2.3.3 WebGUI HTTPS broke after upgrade
-
Good day, can some one help me trouble shoot why HTTPS no longer works.
After the upgrade i was was not able to access the web gui any more, i ssh in and change /conf/config.xml from https to http and the web was accessible again.
I attempted to switch it back to https in the GUI and became in accessible again.
I factory reset and reloaded my config.. still didn't work.
I did a fresh install and loaded my config still didn't work.currently it only works if i have HTTP enabled.
when HTTPS is enabled port 443 is accessible but its almost like nothing is hosting properly.
I checked the lock out rules and they are all working fine..
Any suggestions as what i can try to get https back working?edit also to add to this, i checked the firewall logs when i attempted to access when HTTPS was enabled and i see the firewall rule PASS the 443 tcp traffic.
-
Look around: System / Advanced / Admin Access, System / Certificate Manager
maybe generate a new Certificate for WebGUI -
Look around: System / Advanced / Admin Access, System / Certificate Manager
maybe generate a new Certificate for WebGUIHey RonpfS, I tried and existing one and a new one still no luck still getting ERR_CONNECTION_CLOSED in the browser.
when i look at the logs i do see errors after hitting submit
i do see a bit of errors and then
bind() to 0.0.0.0:443 failed (48: Address already in use)
I Think what is happening is the captive portal plugin is also set to use https with NGINX and the configs are interfering with nginx trying to bind on 0.0.0.0:443
As soon as i tell PFsense to listen to be https on a off standard port it works.. any ideas? or is this now a bug?
-
when i look at the logs i do see errors after hitting submit
i do see a bit of errors and then
bind() to 0.0.0.0:443 failed (48: Address already in use)What about showing these errors ?!
I Think what is happening is the captive portal plugin is also set to use https with NGINX and the configs are interfering with nginx trying to bind on 0.0.0.0:443
nginx is used for the GUI : for http and https.
nginx is used for the captive portal(s) (ports 800x (and up)).
Works for me.As soon as i tell PFsense to listen to be https on a off standard port it works.. any ideas? or is this now a bug?
And why taking it of the standard (443) port ?
=> but : when I change my default https access, using port 443 to 450 (and save), I can access the GUI on port '450' afterwards.Btw : I'm running the GUI on LAN, dand DO NOT permit access from any other NIC (neither WAN, neither my Captive portal running on OPT1)
-
" bind() to 0.0.0.0:443 failed (48: Address already in use)"
What is using it?
2.3.3-RELEASE][root@pfsense.local.lan]/root: sockstat | grep :443
root nginx 78975 6 tcp4 *:443 :
root nginx 78975 7 tcp6 *:443 :
root nginx 78929 6 tcp4 *:443 :
root nginx 78929 7 tcp6 *:443 :
root nginx 78911 6 tcp4 *:443 :
root nginx 78911 7 tcp6 *:443 :
root openvpn 23945 5 tcp4 24.13.snipped:443 :
