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?

@steveits Thank you!

It's a known issue and fixed on 2.6.0/21.09 snapshots

Hello Steve,
Thanks, it’s working now. Seems, missed several backups in between! that’s fine to us as it resumed to normal.

@kom Thank you - I appreciate the help.

Seems to be somewhat browser related also.
The logo disappears ONLY if:

pfSense-beta theme is selected, and

Chrome browser is used, and

Only on an SG-1100

@gertjan

I manually deleted the cert by clicking on the trash can icon.

I did not know about pfSsh.php so I create a new cert in certificates and assigned that in DNS.

I think the bottom line is I had picked a, now deleted cert in the DNS drop down, which cause the DNS service not to be able to start even though DNS SSL was unchecked. It must, since the cert was specified, check if it exists and since it no longer existed it would not start.

I restored backup file, problem solved.
thanks