Great, Thank you!

See pull request https://github.com/pfsense/pfsense/pull/3694 for a fix.

Clearing the cache didn't help, neither does using an incognito window, or a browser on a computer that has never connected to the router.

In the end, I set up Telegraf, InfluxDB and Grafana to give me a nice dashboard.

Or just trust your pfsense CA if you want the pretty green icon..

You can then even use rfc1918 IPs as SAN so you get pretty icon via fqdn or any IPs you might hit your pfsense web gui on..

When is the admin web gui accessed by mass of users.. The only people accessing pfsense web gui should be the admins of pfsense - so why would they not trust the CA of pfsense?  Really takes all of like 1 min to setup..  Using something like lets encrypt that has to be renewed ever 90 days and requires use of registered domain and does not allow for rfc1918 san seems completely pointeless and useless in such a use case..  The only point of using such a cert and ca would be if you need the unknown masses of users that might access the web site and automatically trust the CA.. That should never be the case in the pfsense web gui.. While if you trust your local CA you can use whatever freaking fqdn you want.. see mine is a local.lan and whatever IPs you might want for san, etc.

And actually paying for a cert by a public/trusted cert would just be a waste of money.. time and effort all the way around..

Trusting the pfsense Ca now allows you to create certs that are trusted and the pretty green for all your appliances, servers any iot devices, etc. etc.  See trust my switch url, etc.  2nd pic. esxi host 3rd pic

trustcerts.png
trustcerts.png_thumb
switchtrust.png
switchtrust.png_thumb
otherssltrusted.png
otherssltrusted.png_thumb

I solved my problem. I'll describe the solution here, maybe this can help someone in the future.

First, my setup.
In my pfSense box, I do have a MultiWan setup with two independent links. Since my ISP gateways do not answer ping requests, I have set Google's DNS IPs 8.8.8.8 and 8.8.4.4 to monitor my links.

And the problem:
Apparently, all my ISP links were intermittent for international hosts (Google's DNS is an internation host for me, since I am in Brazil).
Due to this, all my links became unstable. The %loss in Status > Gateways were very high (like 30-40% of loss on both links). This was clearly affecting several pfSense services, like SSH and my users' internet access.

There were also some lines stating this issue in the logs:

/rc.start_packages: Gateways status could not be determined, considering all as up/active. (Group: MultiWAN) ... /rc.filter_configure_sync: Gateways status could not be determined, considering all as up/active. (Group: MultiWAN) ... /rc.openvpn: Gateways status could not be determined, considering all as up/active. (Group: MultiWAN)

Since there's nothing I can do to solve the intermittency of my ISPs link, I decided to change the monitor IP of my Gateways (in System > Routing > Gateways) to an IP that wasn't intermittent (just to cite, I changed them to www.uol.com.br IPs, 200.221.2.45 and 200.147.67.142).

This immediately solved the problem.

@meruem:

Update:

i wouldnt recomend this but because it sounds like you'll lose everything, but I did option #4, (Reset to factory defaults), and then confirmed yes. The terminal stoped stdout and appeared frozen and then all of the sudden my spinning webconfigurator in my browser loaded. now im up and running , I lost nothing, all my config is still there. O_o . I even rebooted and im still good

I would give it a try and let you know whether it works fine for me or not. Well, I now have to install it on a spare machine and would do these experiments as I can't touch my Pfsense in our normal working hours. Glad to hear a response from you on this and thanks a million for your help :)

I made & use this hybrid myself. Feel free to…

pfSense-12-red-css.txt

Just to add here, the limit IIRC is not the number of interfaces but the number of characters for all the tabs. Something around 80+. So, if you can make the interface names shorter, you might get rid of the dropdown.

Seeing similar issues here on an SG-4860.  I run a 4 column dashboard and often just getting back to the dashboard it will paint the first two columns on the left and 4 or 5 seconds later it paints the last 2 columns.  Just moving from widget to application can be slow as well.  There are also some menu-lockouts when certain functions are running.

related to NGINX??

https://forum.pfsense.org/index.php?topic=122951.0
https://github.com/pfsense/pfsense/pull/3553
https://github.com/pfsense/pfsense/pull/3580

Try clearing cache Shift-Reload, etc. Make sure your browser is using the latest bits.

That did it; thanks for the help!

Hi,

New maybe, but an old explanation will do : https://forum.pfsense.org/index.php?topic=126827.msg703782#msg703782  ;)

There is a temp fix here:
https://forum.pfsense.org/index.php?topic=126773.0

Well known bug.

https://redmine.pfsense.org/issues/6748

Just to bump this, I noticed that every nanobsd upgrade on pfSense has been plagued with the "/etc/rc.conf_mount_rw" issue. I thought nanobsd was always set to read-write, but I cant upgrade without setting /etc/rc.conf_mount_rw from the shell.