Hmm, strange indeed!

Do you have an OpenVPN server running on the firewall? Does it show the clients connecting to it? What are they supposed to be connecting to?

What do you see logged when the webgui cert changes?

Steve

Removing the coax caused pfsense to lose connection, but maintain the DCHP address it had. I was logged in to the gui and could still use it as long as I stayed away from the dashboard. The dashboard did load very slowly but did load after a few minutes.

Logging out and then logging back in, where the default starting point is the gui, did not ever load and eventually returned this:

Screen Shot 2020-07-12 at 4.51.54 PM.png

I read this is due to widgets, ie the version checking for updates and needing DNS but not having it and eventually timing out. The 8987 bug shows resolved, but did say that the issue is not resolvable at the time.

Once I reconnected the coax, everything became stable again and no reboots on the modem or pfsense were needed. That is not what happened to me yesterday, I had to reboot both the modem and pfsense. Is this something I need to live with, not being able to check the status of my WAN via pfSense when my isp goes down?

Is there a command line equivalent of this gateway status shown in the dashboard?

Screen Shot 2020-07-12 at 5.05.53 PM.png

Thanks,
Jerold

@NollipfSense I am using a cable modem, so I guess I'll just wait and see if the issue returns. Hopefully not!

Okey-dokey.

Though here it reads:
"Wenn nicht aktiviert, wird Port 80 automatisch auf den HTTPS Port weitergeleitet. Aktivieren, um die automatische Weiterleitung zu deaktivieren." which sounds to me, the native German speaker, the other way round.

Thanks to all who answered, I think I understand the behaviour.
And yet, I can't really see the point of this behaviour, to me at least it is unexpected. Not?

Thanks again,

Uwe