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:
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.

I will answer it myself - as long as the interfaces are attached to something....a switch , etc...it doe not time out. Thanks Netgate....maybe you guys will fix that in new versions?

Paul

@johnpoz said in webConfigurator: Using my own CA is not working...:

I would think so but you can always restart from the console menu, option 11

I forgot about that...., thanks for your help!.... 👍

@viragomann Hey thanks for the comment. You are right, if I use the VPN interface IP I can connect! I did not understand this correctly in your second post.
That solves my problem 🙏

@Ramosel said in Package updates not showing until I ran Package Manager:

Patch Manager

System Patches? That was released this morning.
https://forum.netgate.com/topic/184175/system-patches-package-version-2-2-8

dunno about others :)