Update from 2.7.0 to 2.7.2 - No WebGui

shadragon

Good Day,

Updated from 2.7.0 to 2.7.2 and lost the web gui after all was done. Firewall is working fine, I have access to the console and from what I can see the nginx is working correctly. Reset option 11 and 16. Restarted numerous times. Restored a backup config from a few months back (no changes in config since I set it up) and still no web gui. Tried http, https, incognito mode, no joy. Only change made was the update to 2.7.2.

pfSense is running on a ESX VM.

Gertjan

@shadragon

nginx is there. I've the same sockstat list.
Wild guess : are you connected to the LAN ? Or WAN ^^
IIRC : check the doc, there is a console command to switch of the firewall 'pf', this will help if it's a rules issue - or no rules == block by default.

Check also if php-fpm is up.

shadragon

@Gertjan
Cheers.

PLP-FPM is up and restarts fine.

Also tried /etc/rc.restart_webgui to no avail.

No errors in the log or any other issues I can see.

Gertjan

@shadragon

If you are using the https version of the GUI :

curl https://pfsense.your-domain.tld:443

where :

This should show the GUI page (the login page) - html of course ^^.
" " should resolve to your LAN IP.

This line should be added to the /var/log/nginx.log file :

<174>1 2024-02-29T08:00:21.000000+01:00 pfSense.pfsense.your-domain.tld nginx - - - 2a01:cb19:dead:beef:92ec:77ff:fe29:392c - - [29/Feb/2024:08:00:21 +0100] "GET / HTTP/2.0" 200 10947 "-" "curl/8.5.0"

shadragon

@Gertjan
Sorry for the delay. LAN connection to the web gui.

Tried the curl command, but got this error.

The fw is set to only accept LAN connections from one ip so even http would work for me at this point. If I can't sort this I'll reinstall and restore a backup. Even if I have to recreate everything it's an hours work. Still the challenge of figuring this out is appealing. :)

Gertjan

So, the GUI is listening on :

@shadragon said in Update from 2.7.0 to 2.7.2 - No WebGui:

The fw is set to only accept LAN connections from one ip so even http would work for me at this point

Easy to put a pass rule on LAN for testing ...

Just to be sure : get another browser ...

Btw : self signed cert : How to ignore invalid and self signed ssl connection errors with curl