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.

Still having the problem, now I have some logs See attached file. Tried the workaround in https://redmine.pfsense.org/issues/6862 - did not work  

" bind() to 0.0.0.0:443 failed (48: Address already in use)" What is using it? 2.3.3-RELEASE][root@pfsense.local.lan]/root: sockstat | grep :443 root    nginx      78975 6  tcp4  *:443                : root    nginx      78975 7  tcp6  *:443                : root    nginx      78929 6  tcp4  *:443                : root    nginx      78929 7  tcp6  *:443                : root    nginx      78911 6  tcp4  *:443                : root    nginx      78911 7  tcp6  *:443                : root    openvpn    23945 5  tcp4  24.13.snipped:443      :

@pluff: I did kind of cover that off along with the reboots How exactly do reboots cover browser web page refresh?

@doktornotor: How about upgrading your pfSense to 2.3.3 and using the ACME package? Thanks for the suggestion.  As I just mentioned, I was able to get it working.  But as my current certbot workflow is somewhat clunky, I should see if 2.3.3 w/ACME can file off some of those rough edges.  A project for next weekend…

Will be hard to guess the OTP password on the proxy gateway… then you will have to guess the gui password as well. I need to access from work where I have not mobile data (nuclear plant, the walls are so thick). And I cannot use VPN on my workstation, only proxy access to internet.