FortiWeb can integrate with FortiGSLB using a service called One Click GSLB. This can be found under FortiWeb > Security Fabric > Fabric connector under other Fortinet products.
This cloud status needs to show Green in order to show that it's connected to the GSLB cloud. If showing Red mean the cloud status is down.
Even though the service is set to enable, the cloud reachability is down.Â
To check this further, follow the troubleshooting steps:
Try to ping the Cloud server URL and see if the FQDN can resolve to an IP address:
execute ping 1clickfwb.fortigslb.com
unknown address type; only IPv4 is currently supported
If a similar message is there, it means the FQDN is not able to resolve to an IP. Then proceed to open the CLI and take the debug:
diagnose debug application ocgsd 7
diagnose debug timestamp enable
diagnose debug enable
2026-07-16 18:15:02](update_vs_status : 1399)now_time:1784250902, license_time:20270508 [2026-07-16 18:15:03](update_vs_status : 1425)policy name:Kali, fqdn:g.mygslb.test.me.
[2026-07-16 18:15:03](update_vs_status : 1475)vip name:LinuxServer, ip:10.1.1.1
[2026-07-16 18:15:03](add_vs_status_to_object : 1353)vs status object_str:{ "vdom_name": "root", "name_key": "Kali", "ip": "10.1.1.1", "status": 1, "active_session": 0, "byte_processed": 0 }
[2026-07-16 18:15:03](curl_post : 180)curl_post: POST https://1clickfwb.fortigslb.com/api/v1.0/one-click-glb-fwb/updatestatus failed: Could not resolve hostname <<<<<<
Try to change the DNS server IP on the FortiWeb. If that is an internal IP, then change it to Global DNS and try to ping the cloud server IP again.
Post changing the DNS server IP, and Ping the cloud server FQDN to verify if the FQDN is able to resolve.
FortiWeb # execute ping 1clickfwb.fortigslb.com
PING fortigslb-oneclick-nlb-7654-836794db46510340.elb.us-west-2.amaz (52.43.24.46): 56 data bytes
^C
--- fortigslb-oneclick-nlb-7654-836794db46510340.elb.us-west-2.amaz ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
FQDN resolution could be the main reason for this issue. After that issue the cloud server status will come up.
Note: If the above steps do not resolve the issue, then reach out to Support with the debugs collected as mentioned.
| 
