@phil.davis: I checked on 2.3.4-RELEASE and 2.4-BETA. In 2.3.4-RELEASE it always shows all the top menu items, even if they are empty. In 2.4-BETA empty ones do not show. So what you want is coming. Hi phil.davis, OH, I've seen the differences of 2 versions, thanks support for me.

Go to System->User Manager, edit the user that you are logged in as. See if the Custom Settings box is checked. If so, then that user has their own set of custom webGUI settings, which includes the theme. That user has a different theme selected from the default theme (which is selected in System->General Setup)

This quirk still exists in PFSense 2.3.4.

As said above, it has nothing to do with pfSense. The request is coming from your PC.

@NOYB: Is there a save button at the bottom of the page?  If so, after making changes, click it. Thanks NOYB.  Just upgraded all my 2.2 boxes and still not familiar with the 2.3.x interface.  I was having the same issue and missed the 'Save' button lighting up.

I can confirm the patch works. Thanks again! Cheers, Keith

PR https://github.com/pfsense/pfsense/pull/3707 adds the ability to customize the widget title, for widgets that currently have any customizable options. (For widgets that do not have anything customizable, the user is not likely to want/need to change the widget tile. And widgets like this do not have any of the code to show the "wrench tool" and open the settings panel. I was basically too lazy to add that to those widgets.)

Ah yeah, much better. Thanks..

So I just had to save a change on the General tab and it reset to 4 columns now. How can I override it till this gets updated in a snapshot?

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 [image: trustcerts.png] [image: trustcerts.png_thumb] [image: switchtrust.png] [image: switchtrust.png_thumb] [image: otherssltrusted.png] [image: 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