Troubleshooting Tip: Internal server error due to ...

jankit6 · 04-18-2025

Description This article describes how to fix the package version conflict issue that occurs during the FortiSOAR upgrade. Scope FortiSOAR v7.3 deployed on an Azure host system. Solution FortiSOAR upgrade from v7.3.0 to v7.4 fails with below error du...

jankit6 · 03-14-2025

Description This article describes how to fix an issue where the Python library failed to install during FortiSOAR's initial configuration Scope FortiSOAR. Solution After installing FortiSOAR, the initial config wizard launches to configure it once t...

jankit6 · 03-14-2025

Description This article describes how to fix the issue that occurs during content export while using the Export Wizard option. Scope FortiSOAR. Solution While exporting the contents like connectors, playbook, and other modules, it fails with the bel...

jankit6 · 03-14-2025

Description This article describes how to resolve an issue that occurs after upgrading the FortiGate connector to version 5.4.0. Scope FortiSOAR and FortiGate Connector version 5.4.0 Solution Issue 1: After upgrading the FortiGate connector to the 5....

jankit6 · 03-14-2025

Description This article describes how to configure Jinja to map the source ID, or any other field containing a long number, to a text file in FortiSOAR. Scope FortiSOAR. Solution The value of the field in FortiSOAR changes to scientific notation ins...

jankit6 · 04-16-2025

You can review the execution history for the alert to identify the reason for the playbook failure, which should help pinpoint the root cause.If the playbook has failed, you can also try retriggering it.

jankit6 · 04-16-2025

Hello @Osama-Ahmed The indicator extraction for the alert seems stuck or is still in progress. You can check the Extration playbook status by opening an alert and selecting the playbook execution history for the respective alert. Regarding the second...

jankit6 · 04-02-2025

@Osama-Ahmed The error indicates an issue with DNS resolution:Failed to establish a new connection: [Errno -2] Name or service not known')) Could you please try the below from FortiSOAR CLI and verify: # curl -v https://api.xforce.ibmcloud.com# telne...

jankit6 · 03-25-2025

Hello @bidisha-spryiq This is the default behavior by design, where the AND condition does not apply to the tags field.

jankit6 · 02-25-2025

Thanks @Ranjith All the services are running? # csadm services --status Try restarting it once # csadm services --restart if still an issue, please open a support ticket and share the logs.

User Statistics

User Activity

Troubleshooting Tip: How to fix package version conflict issue occurs during FortiSOAR upgrade from v7.3.0 to v7.4.0

Troubleshooting Tip: Installation of Python libraries failed during Initial VM configuation

Troubleshooting Tip: Steps to identity and fix the issue occurs during content Export using Export wizard

Troubleshooting Tip: Health check and Block IP action fail after upgrading FortiGate connector to 5.4.0 version

Technical Tip: How to map source ID containing long numbers to a text record field in FortiSOAR

Re: Alert Data

Re: Alert Data

Re: IBM xforce connector

Re: API Query to Fetch Module Data

Re: Error: Unable to load API credentials from cache or DAS

Troubleshooting Tip: Internal server error due to ...

Troubleshooting Tip: Proxy Connectivity Issues in...

Troubleshooting Tip: Approval step shows Deprecate...

Troubleshooting Tip: Troubleshoot the issue with S...

Troubleshooting Tip: How to fix HMAC Authenticatio...

Re: Fix for playbooks que overflow

Re: Issue with Installing CylancePROTECT Connector...

Re: Update Record step is failling with Internal S...

Re: Authorization code for office365

Re: Connector Fortinet FortiGuard Threat Intellige...

FortiSOAR

KCS

User Statistics

User Activity

You are leaving our website