What to do when you are "Unable to connect" to FortiGate from Local-Client device?

Modified on Fri, 07 Jul 2023 at 10:41 AM

Summary: The user tries to connect to the FortiGate GUI using the Firefox browser (HTTPS default protocol) on the local-client device. The page will not open within the "Local-Client" device and an error message in Firefox will appear: "Unable to connect"; e.g : https://10.X.X.X/login?redir=%2F

If you get this error there are strong chances that either device 10.X.X.X is shut down or the HTTPS protocol is disabled.

  • First workaround: try using HTTP instead of HTTPS; e.g > http://10.X.X.X/login?redir=%2F

  • Second workaround: if the first workaround did not work, ensure device 10.X.X.X is not shut-down. In this case, you need to power it on or reboot from your console (Revert > Power On).

  • Third workaround: you might have disabled 'HTTPS' by mistake on the Fortigate (ISFW / Local-Fortigate). In this case, you must connect to the device and ensure HTTPS is enabled on all ports.

On the Fortigate Device > Network > Interfaces; ensure all active ports have 'HTTPS' enabled:

Having done that, you can try again, and the chances are all is working as expected:

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article