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

System -> General setup

lihn.jpg
lihn.jpg_thumb

After setting up a new rsyslog-server (CentOS 7) this week, i see the same behaviour. It must be something completely different from standard because i set up rsyslog to truncate the domain name. That works for all messages, except those submitted by nginx on pfSense.

It clutters up the log results and i think there should be a fix for this.

We have six pfSense 2.3.2 boxes, of which five are full installs and one is a nano image with VGA.

The same problem is reported here: https://forum.pfsense.org/index.php?topic=112880.0

@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

I did sort of almost spit out my drink when I noticed you using a code base thats no longer supported.

I can confirm on 2.4 TLS 1.2 is used.

So update the pfsense to a newer code base and your problem is solved.

"Using https and an IP, that's just NOT possible - not logic - it's counter productive …"

Huh???  An IP is no different than FQDN, you can for sure put IP as SAN in your cert so you do not get any warning..

Notice my pretty green icon, and hitting it via IP.. Notice the SAN have 2 different IPs in them and another fqdn for another interface - so I can hit it with that name or that IP and still trust the cert..

SANinCert.png
SANinCert.png_thumb

Hardware event. This is not a software error. CPU 0 4 northbridge   Northbridge Watchdog error       bit57 = processor context corrupt       bit61 = error uncorrected   bus error 'generic participation, request timed out             generic error mem transaction             generic access, level generic' STATUS b200000000070f0f MCGSTATUS 4 MCGCAP 105 APICID 0 SOCKETID 0 CPUID Vendor AMD Family 15 Model 47

Nothing there sounds good, it also doesn't point to any one specific thing.

Given that seems to be a >10yr old CPU, it's probably time to consider a replacement box.

AMD 0F 2F K8 (rev.E)   Athlon 64  Sempron

Flixed in the latest snapshot. Thanks Luiz.

Glad to assist in finding bugs, it still sets the LAN IP though, just a little annoyance pop-up. :)