Fortinet white logo
Fortinet white logo

Known Issues and Workarounds

Known Issues and Workarounds

  • 1126843: When a filter is applied on the listing page and a record is opened in a new tab, users may encounter a '414 Request-URI Too Large' error if the URL generated with the filters exceeds the default length limits.
    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.
  • 1220684: Upgrading from release 7.6.1 to a later release (for example, 7.6.4, 7.6.5) causes the Utilities Connector 'Create an attachment from file action' to fail with the following error:
    CS-INTEGRATION-5: Error occurred while executing the connector action. ERROR :: 400 Client Error: Bad Request for url: https://localhost/api/3/files :: {'type': 'TypeError', 'message': \"Internal Server Error. Check log 'prod.log' for more details\"} :: Url: https://localhost/api/3/files Call for URL: https://localhost:9595/integration/execute/ failed with status code 400 \n
    The issue occurs because the Restricted File MIME Types setting under Settings > Application Configuration has no values configured. As a result, file uploads fail.
    Workaround:
    After upgrading from release 7.6.1:
    1. Navigate to Settings > Application Configuration.
    2. Update Restricted File MIME Types to include the default values:
      image/svg
      image/svg+xml
    3. If any custom MIME types were configured before upgrading from release 7.6.1, re-add those values as well.
    4. Save the updated settings.
      For details, see the Enabling MIME type validations for file uploads topic in the "Administration Guide."
      NOTE: After upgrading from release 7.6.1, the TAXII server configuration is also automatically disabled. If the TAXII server is required, manually re-enable it. For more information, see the Threat Intel Management Solution Pack documentation.

Known Issues and Workarounds

Known Issues and Workarounds

  • 1126843: When a filter is applied on the listing page and a record is opened in a new tab, users may encounter a '414 Request-URI Too Large' error if the URL generated with the filters exceeds the default length limits.
    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.
  • 1220684: Upgrading from release 7.6.1 to a later release (for example, 7.6.4, 7.6.5) causes the Utilities Connector 'Create an attachment from file action' to fail with the following error:
    CS-INTEGRATION-5: Error occurred while executing the connector action. ERROR :: 400 Client Error: Bad Request for url: https://localhost/api/3/files :: {'type': 'TypeError', 'message': \"Internal Server Error. Check log 'prod.log' for more details\"} :: Url: https://localhost/api/3/files Call for URL: https://localhost:9595/integration/execute/ failed with status code 400 \n
    The issue occurs because the Restricted File MIME Types setting under Settings > Application Configuration has no values configured. As a result, file uploads fail.
    Workaround:
    After upgrading from release 7.6.1:
    1. Navigate to Settings > Application Configuration.
    2. Update Restricted File MIME Types to include the default values:
      image/svg
      image/svg+xml
    3. If any custom MIME types were configured before upgrading from release 7.6.1, re-add those values as well.
    4. Save the updated settings.
      For details, see the Enabling MIME type validations for file uploads topic in the "Administration Guide."
      NOTE: After upgrading from release 7.6.1, the TAXII server configuration is also automatically disabled. If the TAXII server is required, manually re-enable it. For more information, see the Threat Intel Management Solution Pack documentation.