| Description | This article helps to identify and fix the issue that occurs with the FortiGuard Threat intelligence connector. |
| Scope | FortiGuard Threat intelligence connector - All versions of FortiSOAR prior to 7.4.1. |
| Solution |
Error: _traceback__ must be a traceback or None Connector:: fortinet-fortiguard-threat-intelligenceV3.1.1
Resolution step:
#curl -v https://filestore.fortinet.com #curl -v https://productapi.fortinet.com #Disable SSL inspection in Firewall/Proxy.
2. Ingestion fails with 502 errors.
Error: 502 Server Error: Bad Gateway for url: https://localhost:9595/integration/execute/?format=json
Resolution Step:
#Update the timeout value: Vi /etc/uwsgi.d/integrations_wsgi.ini harakiri = 900 (This is in seconds. Change it to 3600 to make it 1 hour) #Restart uwsgi service: systemctl uwsgi restart
3. FortiGuard connector health check down while running on Agent:
Error: FileNotFoundError: [Errno 2] No such file or directory: '/opt/cyops-auth/certs/fdn_client_keystore.p12'
Resolution Steps:
#Login to Agent CLI #sudo -u fortisoar mkdir -p /opt/cyops-auth/certs #Download the file "fdn_client_keystore.p12" from the master system present at the same above location #Copy the file on the agent and change the permission #Chown fortisoar:fortisoar /opt/cyops-auth/certs/ fdn_client_keystore.p1 #Restart the cyops-integrations-agent service: systemctl restart cyops-integrations-agent
4. Ingestion fails due to unexpected character.
Error: Unexpected \"}\" character.\nCONTEXT: unnamed portal parameter $17693
The patch is applied in FortiSOAR 7.4.2 version. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2026 Fortinet, Inc. All Rights Reserved.