Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
rotem
New Contributor

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

 

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? 

 

16 REPLIES 16
shastacs

Yup config issue. Bonehead move and forgot to enable FIPS mode. Works now. Ha ha. 

sahps
New Contributor II

Absolutely a bug. I'm new to Fortigate, and am setting up a 100F. 3 times now I get this error when clicking the CLI button, to fix it every time, without making any further changes, is to close my incognito no-extensions-installed browser window and start again. Sorry but that is a bug. Browsers follow the instructions given to them and the Fortigate GUI puts itself into this mess. Frustrated, as I have wasted time on this and the only response from Fortigate is to claim its not a bug.

Claiming this isn't a bug is both wrong and not useful.

AlexC-FTNT

There are 2 bugs for this

- 412184 was fixed in FortiOS 5.6

- 1155662 in FortiOS 7.2 (and multi-vdoms) has been fixed in FortiOS 7.4.8 with no fix in 7.2, since it passed the End of Engineering Support date.

So make sure your FortiGate is running the recommended version (or newer)
Technical Tip: Recommended Release for FortiOS


- Toss a 'Like' to your fixxer, oh Valley of Plenty! and chose the solution, too00oo -
sahps
New Contributor II

I'm running 7.4.9 build 2829 (Mature). Updating needed to be the first thing as it wouldn't register with cloud to get its licenses with the shipped firmware. CLI thing happened again just now.

Yesterday when I had this issue, I was connected via the MGMT port and setting up all the other interfaces and VLANs. Couldn't GUI CLI after that so I closed and re-opened the browser.


Today I did a test fail-over to the HA unit by unplugging the power on the current primary. Test went smoothly, plugged back in, did the same thing with the other unit, also fine. Plugged all back in. Then I couldn't CLI, so I closed and re-opened the browser again to fix.

 

So then I thought I'd be helpful and raise a case to see if this could get looked at, and I can't reproduce it. No idea :(

AlexC-FTNT

But what you describe is completly normal. The RSA keys are not the same for the units, so restarting the browser (clearing the cache/cookies) to access the other unit after failover is quite normal and expected (or CTRL+F5 will achieve the same outcome). 


- Toss a 'Like' to your fixxer, oh Valley of Plenty! and chose the solution, too00oo -
sahps
New Contributor II

Sure, that makes technical sense. Doesn't make it less annoying. Closing and re-opening my browser repeatedly isn't fun so I have stopped using the CLI button and SSH in instead.

 

Something for the suggestion pile for Fortigate to improve upon.

 

Have a great weekend.

HelpMe
New Contributor II

Use Chrome

Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors