When troubleshooting the issue of the FortiSOAR GUI not being reachable, the first step should be to check the status of the nginx service, which is responsible for managing web requests.
Using the command systemctl status nginx will provide information on whether the service is running and any potential issues or errors related to it. This approach is more efficient as it directly addresses the service responsible for the web interface, making it possible to diagnose and resolve common issues such as service failure, configuration errors, or connectivity problems.

The celerybeatd service in FortiSOAR is responsible for the playbook scheduler. It handles the periodic execution of scheduled playbooks by managing tasks that need to be executed at specific times or intervals. This service works in conjunction with the Celery worker processes (celeryd) to execute the scheduled tasks.

Connectivity Requirements: For the FortiSOAR license deployment and validation process to succeed, the instance must have outbound connectivity to https://globalupdate.fortinet.net. This URL is specifically used by the FortiSOAR license manager to fetch entitlements, verify the subscription status, and retrieve product information from the Fortinet licensing servers. If this connectivity is blocked (and a FortiManager is not being used as a local FDN proxy), the license deployment will fail.
License Limits: Every FortiSOAR license--whether Perpetual, Subscription, or Trial--strictly enforces a maximum number of active users (concurrent or named) and often a limit on the number of automation actions per day.
Perpetual Trial Licenses (often called "Free Trial") are restricted to a specific user count (typically
2 or 3) and a daily action limit (e.g., 200 or 1000 actions). Therefore, options C and D are incorrect as they suggest "no limit on user count." URL Clarification: While update.fortiguard.net is a common Fortinet endpoint for security signatures (IPS/AV), FortiSOAR's specific licensing and entitlement communication is directed to the globalupdate.fortinet.net service.

When joining a FortiSOAR cluster as a standby node, the correct status value should be passive.
Using active would imply that the node is trying to join as an active node, which could cause conflicts in the cluster setup. In FortiSOAR, standby nodes must be set as passive to ensure they are recognized correctly and to avoid conflicts with the primary node or other active nodes within the cluster. Therefore, setting the status to passive will resolve the issue and allow the node to join the cluster as intended.