No web gui after updating 24.03
-
The IP addresses are still correct?
Can you ping out from the console?
You might be hitting the firewall state binding change:
https://docs.netgate.com/pfsense/en/latest/releases/24-03.html#generalHow are you trying to connect to the webgui?
-
@stephenw10 said in No web gui after updating 24.03:
https://docs.netgate.com/pfsense/en/latest/releases/24-03.html#general
Yes.. i try to connect to web GUI, but nothing.. no ping, no ssh, no webgui...
I try to connect to webgui with IP (Firefox, Brave, chrome...) but nothing..Yes, i can pint out from console on proxmox.
After test a few ideas... that vpn-pfsense are working.. if i connect with a wireguard vpn and try to enter the pfsnse MV says "Connection REFUSED" in other words.. firewall inside that MV is working..
but.. why i can't see the webgui? This pfsense have been working more than 1 year without problems...
0 errors or problems while loading pfsense+
-
@stephenw10 said in No web gui after updating 24.03:
You might be hitting the firewall state binding change:
https://docs.netgate.com/pfsense/en/latest/releases/24-03.html#generalHow are you trying to connect to the webgui?
That ^.
If you have some sort of route asymmetry it may be blocking the traffic.
If you disable the firewall as a test can you connect?
https://docs.netgate.com/pfsense/en/latest/troubleshooting/locked-out.html#disable-the-firewall -
@stephenw10
WORKING...
I put a all traffic passing from wireguard connection and i can login into pfnsense, and go to advanced--firewall & nat and floating states...How to configure the more secure Interface Bound States?
-
The fact it blocked your connection with Interface Bound States set implies the traffic was taking an unexpected route somehow.
You first need to work out what was happening there and resolve it.
Or you can set the binding policy to floating on only the rules required to reach the webgui.
I would connect to it and then check the state table to see where the connection is actually opening states. I'm still not clear how you were trying to access it before that was broken.
-
I don't quite understand what's going on since on my other two virtual machines I haven't touched anything and the “Interface Bound States” configuration has worked without doing anything.
What should I do to activate Interface Bound States without the firewall preventing me from accessing the web?
Now I have it on “Floating States” and everything works as usual but I read that it is less secure.
What are the steps to activate Interface Bound States without the firewall blocking me?
I can enter the VM via WAN or LAN.
The Pfsense VM it's inside a lan where the router is another Pfsense that's the reason why i can enter by WAN and LAN
-
@stephenw10
After a few hours testing.. now i can say that i understand where de failure was. If your pass rule is in "Floating rule" when update the firewall will block you because by default update change the metod to Interface Bound States. You must introduce pass rule inside interface tab... that's easy :)All working now.
Thanks Stephenw10 -
@wisepds said in No web gui after updating 24.03:
If your pass rule is in "Floating rule" when update the firewall will block you because by default update change the metod to Interface Bound States
Huh, that might be worth a comment in the release notes...?
-
Hmm, because your floating rule was applied to multiple interfaces? Or was outbound or some other advanced firewall option?
-
@wisepds said in No web gui after updating 24.03:
You must introduce pass rule inside interface tab.
Okay. Same issue here. My configuration was very basic from the beginning purchase of netgate 3100 with no custom rules. How to introduce pass rule without the GUI?
-
@4eanlss there are a handful of suggestions on https://docs.netgate.com/pfsense/en/latest/troubleshooting/locked-out.html#remotely-circumvent-firewall-lockout-with-rules.
However the default pfSense config is no floating rules and an allow all rule on LAN.
-
Yes still unclear exactly what the floating rule configuration was that failed here. I was unable to replicate it locally. I'd love to know what it was because, I agree, we should document it.
-
@stephenw10 I don't know why.. on floating roules only was "PFblocker" floating rules... i only know that with floating rules all work as intend and when we changed to interface bound States GUI stop working.. i must disable firewall and create this rule to work:
My last rule was * * * * * * * and don't work to access.. when that rule was deleted and create a specifically rule to pass.. all work..
That MV is inside a lan.. in other words.. i access that MV by WAN connexion.
-
Hmm, so just the existence of those floating rules prevented access?
The floating rules created by pfBlocker could well block access from the WAN. It coukld just be the pfBlocker lists pulled in something that blocked your local source IP.
-
@SteveITS Thank you for the information. Greatly appreciated. At this point I will not be able to get the GUI from the WAN IP as my ISP works in a way that I would ultimately be hitting their equipment.
-
@4eanlss said in No web gui after updating 24.03:
I will not be able to get the GUI from the WAN IP as my ISP works in a way that I would ultimately be hitting their equipment
Huh? That would be any and all traffic from pfsense to the internet - that is how isps work, yes your traffic be hitting their equipment. So not sure what your meaning with such a statement.
-
@johnpoz I was referring to the troubleshooting option to "Add an allow all WAN rule from the shell"; however, if I attempt to load my public IP address (https) I instead get a web page for a login of my ISP devices. Maybe I misunderstand what the troubleshooting was indicating to attempt. Regardless, I've compared all my configuration backups xmls and have not found a anit-lockout rule in any from the beginning; so, not sure if a ever had a valid configuration other than I was able to use the GUI interface 4 years until the upgrade.
-
@stephenw10 Since my router is functioning normally in all other regards I'm not that concern at this time. I will become familiar with the console interface and attempt to identify the differences in my configuration before/after the upgrade and post results here.
My configuration only runs two additional services: pfBlockerNG and UPS.
My procedure was:- Shutdown the system from the GUI menu.
- After confirming the system was shutdown, pulled power.
- Pulled the USB from UPS and replace batteries. Note: intent was to do UPS maintenance as well and did not want a forced shutdown by UPS during upgrade.
- Restarted firewall, confirmed all services were working sans UPS (USB still unplugged).
- Made configuration backup.
- Performed an upgrade from GUI.
- After device restarted and after 10-15 minutes of no response from GUI -- realization that GUI access was blocked; however, firewall was allowing inbound/outbound traffic as expected.
-
@wisepds same issue for me webgui not responding after upgrade, but everything is up and running.
Edit: yes for me it was the interface bound state change, after set it to floating - it works again.
-
@planetinse said in No web gui after updating 24.03:
Edit: yes for me it was the interface bound state change, after set it to floating - it works again.
So you have asymmetric routing going on, maybe fix it.
