Troubleshooting Tip: Internal server error due to ...

jankit6 · 10-24-2024

Description This article describes how to fix an issue with CylancePROTECT connector dependencies that failed to install during the initial installation of the connector. Scope FortiSOAR v7.6.0. Solution Sometimes, the dependencies do not get install...

jankit6 · 09-23-2024

Description This article describes how to fix an issue with queue and shift management when they fail to trigger. Scope FortiSOAR 7.5 or later Solution If the queue does not trigger automatically even if the condition is satisfied check the following...

jankit6 · 09-11-2024

Description This article describes how to fix the issue of missing CICD widget if it does not install properly with the CI/CD solution pack. Scope FortiSOAR v7.4 and above Solution When installing the CI/CD solution pack, sometimes, the associate wid...

jankit6 · 09-05-2024

Description This article describes how to fix the issues with FortiSOAR login if it fails due to an error 400 Request Header Or Cookie Too Large error. Scope FortiSOAR v7.5.0. Solution Sometimes, the users experience difficulties in logging into Fort...

jankit6 · 05-24-2024

Description This article describes how to fix the issue when modules are not visible in the playbook while trying to select the module to act on. Scope FortiSOAR. Solution While creating a new playbook, it is necessary to select a module on which it ...

jankit6 · 10-23-2024

@ranjeet Could you please try running the below command and check the status of the connector sudo -u fsr-integrations /opt/cyops-integrations/.env/bin/pip3 install pyJWT

jankit6 · 10-23-2024

@ranjeet It seems the required package version for jwt is not present in the repositories. Please allow me some time to check.

jankit6 · 10-23-2024

Hello @ranjeet Could you please try reinstalling the connector once? If still the same error, check the below logs: /var/log/cyops/install/connectors.log/var/log/cyops/cyops-integrations/connectors.log Please do share the exact version of FortiSOAR a...

jankit6 · 09-30-2024

Hello @beingarif It is not advisable to clone a VM instead, you should deploy a new one. Alternatively, if the host settings permit, you can disable the option to keep the "uuid same" during the cloning process.

jankit6 · 06-25-2024

Should not purge the queue without consulting Fortinet TAC. Check the Playbook execution history and search for Active or awaiting playbooks to find out which playbook is building the queue.

User Statistics

User Activity

Troubleshooting Tip: CylancePROTECT connector dependencies failed to install

Troubleshooting Tip: Troubleshoot an issue with queue management

Troubleshooting Tip: How to fix an issue of missing cicd widget post installation of Continuous delivery

Troubleshooting Tip: How to fix 400 Request Header Or Cookie Too Large error for APIs

Troubleshooting Tip: Module not visible in the list when trying to access via Playbook

Re: Issue with Installing CylancePROTECT Connector Dependencies

Re: Issue with Installing CylancePROTECT Connector Dependencies

Re: Issue with Installing CylancePROTECT Connector Dependencies

Re: FortiSOAR- UUID is same for both primary and secondary Server.

Re: FortiSOAR Queued Workflow

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: 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