No web gui after updating 24.03

[wisepds]

@planetinse That's exactly my case...al working.. update.. no GUI but all working hehehe

[johnpoz]

@rbron01 said in No web gui after updating 24.03:

I will role it back and make a screenshot of the LAN rules for you.

Ah yeah kind of hard to do a screenshot of the rules without a gui ;) doh!!

Do you have this rule?

[23.09.1-RELEASE][admin@sg4860.home.arpa]/root: cat /tmp/rules.debug | grep anti-
pass in  quick on igb0 proto tcp from any to (igb0) port { 8443 22 } ridentifier 10001 keep state label "anti-lockout rule"
[23.09.1-RELEASE][admin@sg4860.home.arpa]/root: 

This is the rule that should allow you to access the gui, it should list the ports no matter your other rules.

You can look at your rules without a gui by looking in that /tmp/rules.debug file.. I would ask you to upload the file - but you might want to walk through it before you do - because it could have your public IP in it.

[rbron01]

@johnpoz

Hi the strange thing is I have a powerline network when I plug this one from the ISP to my LAN port everything works as expected.

The powerline has WLan power and hangs as a "Dirty Internet" line.

The rule is in place.

[johnpoz]

@rbron01 said in No web gui after updating 24.03:

when I plug this one from the ISP to my LAN port everything works as expected.

What? Oh your sure your interfaces didn't switch? You saying when you put your internet into what you believe is the lan, it works.. That says your wan is your lan and your lan is your wan.

I would validate with say looking at the menu that the correct interfaces are assigned to what they should be assigned too.

You could do that with ifconfig, or just the pfsense menu should show you what interface is assigned to what.. So your previous wan wasn't getting dhcp either from your wan?

This is VM - yeah that can happen where the interface order changes.

[lohphat]

@rbron01

Same thing happened. No WebUI and no DNS.

I had to revert to a backup config made right before the upgrade and reboot. WebUI and DNS came back.

[johnpoz]

@lohphat Are you also running on a VM?

[lohphat]

@johnpoz Negative. SG-3100

[johnpoz]

@lohphat I would do the same sort of testing, is nginx running even can you call it up on pfsense locally via loopback and IP your trying to hit.

Not aware of your config - but some issues being run into with the new interface binding for states vs floating. You could try changing it to floating, and then figure out what your doing that interface binding isn't working.

[4eanlss]

Confirmed that I have the anti-lockout rule:

cat /tmp/rules.debug | grep anti-

pass in quick on mvneta1 proto tcp from any to (mvneta1) port { 443 80 } ridentifier 10001 keep state label "anti-lockout rule"

[4eanlss]

@johnpoz Yes. It resolves to my ISPs LiteBeam 5AC Gen2

[4eanlss]

@stephenw10 said in No web gui after updating 24.03:

https://docs.netgate.com/pfsense/en/latest/releases/24-03.html#general

Even disabling the firewall does not resolve the web gui.
Still get either 301 Moved Permanently for port 80 or no response on port 8443.

Tried restarting the GUI -- nothing.
Considering reloading the config from just before the upgrade.

[4eanlss]

How to change state binding back to float from console via shell?

[4eanlss]

@4eanlss BTW: I also realized what was meant by try the WAN interface address.

1. From shell temporarily disabled PF: pfctl -d
2. launch browser to WAN IP
3. Accept the warning about certificate i.e. https workds
4. However, still receive a blank page.

[4eanlss]

@4eanlss Okay, so, after looking at the boot log I've found that there are a number of core-dumps on pkg-static. Looks like install from fresh image is in order.