@gertjan Yep - did exactly that and problem was fixed. Thanks!

@viragomann Thank you the additional server part was not clear to me. Probably read too quickly over it. But thanks for clarification.

@thomasyang I understand. "webGUI" seems fine to me, as your question concerns the web based GUI. If your looking for the perfect "security", make it a none issue. Like : Make the WebGUI only accessible on the LAN interface. Activate LAN type another interface (initially called OPT), and use a firewall rule to forbid any "local" web GUI access. Remove all devices from the LAN port. This way, the question is resolved, as the question became irrelevant. The only web to admin the device is to connect physically a cable into the LAN port : the admin has to have physical access to (into) the device. ..... humm : a SG1000 only has two ports, which is rather minimalistic Next best : Set up a OpenVPN if you need to connect to the webgui remotely.

also what version of pfsense - are you on new dev 2.6 snapshots?

@steveits Thank you.

@ofloo These messages are shown the number of php session "begin" and "end" are not equal. This should normally never happen. Maybe a clue here ?

@johnpoz Thank you! , I'll try

@cduv Tested on 2.5.2 and it still works, though I found 90% to be more aesthetically pleasing. Thank you for this, by the way, The limited screen usage for anything but the dashboard was slowly driving me nuts. Using percentages for widths should be the default anyway, given the wide range of display resolutions available today. It also allows for a more flexible interface, though admittedly it can cause some headaches to get it right.

Clarified. Thanks for the detailed explanation guys. Nice evening

@f-meunier seems more like a browser caching problem maybe? If you at first had accessed it via the lan IP? There should be nothing different be it the browser accesses it via the wan IP or the lan IP. That being said - access from the wan/internet to the gui is normally a bad idea.. Unless you can lock it down to specific source IP or network.. Say from your work IP/Network or something. Bad idea to expose the gui to the public internet.. If you need/want to access pfsense web gui while your remote - via a vpn connection is far better method. I do access some of works pfsense boxes via the wan, locked down to my home IP as the only source. And I have not noticed any issues using firefox. They are not yet on 2.5.2 because of lack of access to facility, and risk in updating when nobody could be on site to correct if something went wrong.. But I do have test 2.5.2 setup here, that I could access via its wan IP vs its lan IP.. If you could give some specific example of what your seeing so I could try and duplicate it. But again - there would be no difference accessing it via the wan or lan IP. If wan rules allowed the access.

@johnpoz Yeah, that's an option of course. I was thinking of this and reread the part "from WAN public IP" twice and toke it as "from WAN interface". Also not sure if he added a rule for allowing TCP 443 to WAN to forward it to a server behind. In this case it would be a good advice to change the web configurators port to any other.

@johnpoz its on live with squid running.

@adrianoebm said in SG1100 - Can´t login webGUI sometimes after 21.05.1 upgrade.: CPU is always at 100% too in the web GUI Did you follow the suggestions in your thread about that?