Compliance isn't an issue here. For it to be a problem it has to be proven to actually be a problem, which hasn't happened. Whatever scan is flagging it is giving bogus results, it's a false positive. If you want to alter the source to shut the scanner up, that's up to you.

Side note extra learning “Edit In Place Editing the configuration in-place is also possible in a variety of ways. The general procedure is: Edit /conf/config.xml Run rm /tmp/config.cache to clear the configuration cache Reboot, or use the GUI to save/reload whichever part of the firewall utilizes the edited settings” Ref: https://docs.netgate.com/pfsense/en/latest/config/xml-configuration-file.html

While the proposed solutions here involve directly editing the /conf/config.xml file with scripts, it is important to note that modifying the /conf/config.xml file directly is a delicate operation and should be approached with caution. If you choose to install such scripts, be sure to create a backup of the /conf/config.xml file before making any changes. I had a similar task to install tailscale certificates on the pfSense firewall and created some scripts to import that certificates on pfSense, using acme-command.sh of the acme package. Github Repository I might extend that repository with the great ideas and examples of that thread on demand.

@rickandaj Now is something for a feature request?? Maybe yeah wan/lan are special.. But others called just optX where you can change the name on them, etc. but they are always still referenced as optX

Fixed it. It was my PC that needed reboot. All is fine again.

@jimp Hummm. "vin" is wine here (French). Corrected the post .... thanks.

Hi, The update did not solve the problem. I still got a crash report today. PHP Errors: [27-Dec-2023 14:42:09 Europe/Amsterdam] PHP Fatal error: Uncaught TypeError: pfSense_interface_rename(): Argument #1 ($ifname) must be of type string, array given in /etc/inc/interfaces.inc:4593 Stack trace: #0 /etc/inc/interfaces.inc(4593): pfSense_interface_rename(Array, 'wan_stf') #1 /etc/rc.newwanip(154): interface_6rd_configure('wan', Array) #2 {main} thrown in /etc/inc/interfaces.inc on line 4593 [27-Dec-2023 14:42:28 Europe/Amsterdam] PHP Fatal error: Uncaught TypeError: pfSense_interface_rename(): Argument #1 ($ifname) must be of type string, array given in /etc/inc/interfaces.inc:4593 Stack trace: #0 /etc/inc/interfaces.inc(4593): pfSense_interface_rename(Array, 'wan_stf') #1 /etc/rc.newwanip(154): interface_6rd_configure('wan', Array) #2 {main} thrown in /etc/inc/interfaces.inc on line 4593 The code I have at this line is: [image: 1703684761480-c8a70086-46d8-4b83-9eae-c5e98fcdce7d-image.png] Please suggest me how I can possibly resolve this issue.

@makaone20 said in Can not access webui from local LAN: is this a setting in pfsense? Not unless you created one - or using something like IPS or pfblocker and are blocking it. Out of the box pfsense blocks nothing outbound, and blocks all things unsolicited inbound into your wan.

@johnpoz Thank you, I blocked popups in my browser. Problem solved.

Old thread, but should this be helpful I encountered this issue as well and resolved it by updating the router's DNS servers (i.e. to 8.8.8.8)

@TheAncientGamer on eero, bridge mode is what makes the mesh act like an AP. I skimmed the above but not sure I followed. If you want to separate the networks you can connect your main eero to a third interface with a unique subnet. It needs its own rules; LAN defaults to allow all with the two default rules but all other interfaces default to deny all.

@jimp Thank you. I believe I'm solved here.

@wolfsden3 said in Web GUI blank page: Doing an: nginx -t shows [23.09-RELEASE][root@pfSense.bhf.tld]/root: nginx -t nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful and that's not the nginx.conf that's being used by pfSense/nginx. The actual config file is here : /var/etc/nginx-webConfigurator.conf So : [23.09-RELEASE][root@pfSense.bhf.tld]/root: nginx -c /var/etc/nginx-webConfigurator.conf -t nginx: the configuration file /var/etc/nginx-webConfigurator.conf syntax is ok nginx: configuration file /var/etc/nginx-webConfigurator.conf test is successful The folder /usr/local/etc/nginx/ contains some config files that are placed there when you install pfSense, and never 'touched' again. I'm not sure that they are even needed. The system, pfSense, never modifies the content of this folder, so if the content, any file, was changed, start doubting about the health of the file system == disk all together. Use "Diagnostics > S.M.A.R.T. Status Information & Tests" a bit more often from now on.