GUI CLI - "Connection lost. Press Enter to start a new session"

[rotem]

after changing the Admin sport to 4433 i get the "Connection lost. Press Enter to start a new session." in the cli

changing back to 443 and it's all good.  

factory reset, no help.

any ideas? 

[AlexC-FTNT]

Just a couple of ideas:

- when you start a new session, do you also change the port to the new 4433 in the browser?

https://fortigateIP:4433

- did you check if port 4433 is not mapped to an internal host (a VIP), or maybe SSLVPN (show full | grep 4433 -f)

[Mohamed_Gaber]

I have the same problem. When I access the Web for the HA IP of FortiGate and then click the CLI icon, I get this message. When I access the management IP for any one of them, it works well. The HA and management IP addresses are in same subnet.

The problem with the HA FortiGate that does not has a management IP on the interface.

[Mohamed_Gaber]

I found the solution.

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Fix-CLI-console-from-FortiGate-GUI/ta-p/22...

[Mohamed_Gaber]

I did check and found the SSL port is already changed. The solution worked. But I don't know the port 443 is used by what..

[HelpMe]

It's a bug they refuse to fix.

[AlexC-FTNT]

Your comment is both wrong and not useful. There is no such bug - only misconfiguration.

[dferrari-all]

I totally agree. Maybe is missconfiguration for this particular case of whom had opened this article, but I have the same problem working with more than 10 fortigates either in firmware 7.0.11 or 7.2.10, and ssh session works very well but it fails sometimes with no configuration changes. Just it fails, and you need to reboot browser or the complete desktop. Forti support team should listen this type of comments in place of just saying missconfiguration. Thanks. 

[AlexC-FTNT]

But in most cases it is a misconfigurations. It also happens when you change your certificate, or user profiles. You need to clear the cache. Or use incognito/private mode - that will work (only to prove the point that action is needed on your side).

[shastacs]

I'm still troubleshooting. I am configuring a 61F for a Branch and just loaded v7.0.12 build9517 (FIPS-CC-70-20). The web CLI worked prior and stopped working after the firmware change. 

I have a basic config and going through the hardening process. I do have a different management port and am using a new In-Private session. 

I am inclined to believe it is a configuration issue or an issue with applying the FIPS firmware. I have other appliances with that firmware operating as intended.
I am still researching and If I need to reset, I'll give that a go.