The permission was not bring properly honored in old versions because of a bug. We fixed the glitch. Invalid configurations "broke" when we fixed said glitch, but they were never valid. It was that or clear the privilege on upgrade, and for a bug like that we went with the secure choice.

I wanted to wait a few days to make sure I did enough testing to feel fairly comfortable.  @doktornotor That thought had crossed my mind but I have always had some sporadic connection issues (to websites where someone would get the the ERR_CONNECTION_TIMED_OUT error).  But to try to eliminate things I removed my Pi-Hole VM, my Kujo security appliance, a few consumer grade non-managed switches with decent quality HP/Dell managed switches, my consumer AP's and replaced them with rock solid Adtran BSAP-1920's.  But I would still get the sporadic connection issues.  Hell I even shut down my Guacamole VM just to be sure. But with this latest problem I wanted to remove pfSense and I realized I still had some VM's from when I was testing various firewalls/UTM software.  I knew for sure that Sophos UTM 9 and OPNsense were functioning.  So I powered down the pfSense VM and fired up both the VMs (testing one at a time) and my connections came back (tested for about and hour).  I then powered down the other VM and powered up pfSense and back to the connection issues.  So for this past two days I've been running on Sophos UTM and everything has been just fine.  Not one single connection time out issue.  I even have my pi-hole and Cujo connected and no issues. So I'm not sure what the hell I did with pfSense (since I don't make many changes) but something I changed/checked seemed to have hosed my config.  At this point when I get back from Portland I'll have time to reinstall pfSense and start all over.  going forward I will make sure I take detailed backups whenever I make a change.

@josemaX: Thanks, worked for me also, only to say (if helps some), these certs are the ones on the Certification Authorities Tab. You were posting against a subject from 2014 - using an ancient pfSense version that doesn't exists anymore …

Done: https://redmine.pfsense.org/issues/7312

Looks like it's a bug - https://forum.pfsense.org/index.php?topic=117036.msg662633#msg662633

System -> General setup [image: lihn.jpg] [image: lihn.jpg] [image: lihn.jpg_thumb]

@awnz: …. My question is: where are notifications cached, so I can clear the backlog and re-enable SMTP notifications? I can't find them :( .... Try /tmp/notices (according to /etc/notices.inc)

Something to try as I found it caused a similar issue for me: check under System > Advanced > Notifications that the server pfSense sends administrative notifications to is correct. In my case, it was pointing to a wrong IP address. php-fpm handles sending admin notifications and they all hung on trying to send them to a nonexistent server, making the webGUI unresponsive.

There has been a feature request for so long that I don't expect it's going to happen, ever.

Thanks. Lots easyer  ;D

bump So no one else has had this issue? Kind Regards.

"with no WAN connectivity (and hence, no web GUI)." Not sure where you got the idea that no wan connectivity means no gui??  Unless your trying to hit the gui via the wan IP?  Which yeah then that would clearly be the case ;) You really should start your own thread - whatever issue this poster had, he never came back and clearly since this thread is from 2014 it would of been with an out dated no longer supported version of pfsense.  Which I would assume your running current 2.3.2p1