Fortinet white logo
Fortinet white logo

Known Issues and Workarounds

Known Issues and Workarounds

  • 1126843: When applying a filter on the "Assigned to" field in the 'Alerts' listing page and opening a record in a new tab, users may encounter a "414 Request-URI Too Large" error.
    Workaround:
    To resolve this issue, increase the buffer size for client headers in your Nginx configuration file.
    Update the large_client_header_buffers setting from 4 8k; to 4 50k; in the /etc/nginx/nginx.conf file. After making the change, restart the 'nginx' service as the 'root' user to apply the changes by running the following command:
    # systemctl restart nginx
    If you are using HAProxy as a load balancer, follow these steps:
  1. SSH to your HAProxy VM and log in as root user.
  2. Edit /etc/haproxy/haproxy.cfg file.
  3. In the 'global' section, add the following parameter:
    tune.bufsize 32768
  4. Restart HAProxy to apply the changes by running the following command:
    # systemctl restart nginx
  • 1132542: After upgrading a FortiSOAR deployment configured with Multi-Tenancy (MSSP) and High Availability (HA) in an Active-Active cluster, the WebSocket connection on the secondary node remains disconnected.
    Workaround:
    Restart the cyops-tomcat service on the secondary node:
    #systemctl restart cyops-tomcat
    This restores the WebSocket connection on the secondary node and ensures that all nodes are properly connected.

Known Issues and Workarounds

Known Issues and Workarounds

  • 1126843: When applying a filter on the "Assigned to" field in the 'Alerts' listing page and opening a record in a new tab, users may encounter a "414 Request-URI Too Large" error.
    Workaround:
    To resolve this issue, increase the buffer size for client headers in your Nginx configuration file.
    Update the large_client_header_buffers setting from 4 8k; to 4 50k; in the /etc/nginx/nginx.conf file. After making the change, restart the 'nginx' service as the 'root' user to apply the changes by running the following command:
    # systemctl restart nginx
    If you are using HAProxy as a load balancer, follow these steps:
  1. SSH to your HAProxy VM and log in as root user.
  2. Edit /etc/haproxy/haproxy.cfg file.
  3. In the 'global' section, add the following parameter:
    tune.bufsize 32768
  4. Restart HAProxy to apply the changes by running the following command:
    # systemctl restart nginx
  • 1132542: After upgrading a FortiSOAR deployment configured with Multi-Tenancy (MSSP) and High Availability (HA) in an Active-Active cluster, the WebSocket connection on the secondary node remains disconnected.
    Workaround:
    Restart the cyops-tomcat service on the secondary node:
    #systemctl restart cyops-tomcat
    This restores the WebSocket connection on the secondary node and ensures that all nodes are properly connected.