Webconfigurator doesn't save webgui tcp port if blank and others
-
I was experimenting with captive portal and I needed to change the web configurator in system/advanced/webconfigurator to https and non standard port in tcp port say 555.
When I tried to revert to http from https and blank the tcp port field so it would use the defaults for http it did not save the blank value but rather kept the old one.
As a result, after saving the changes I was not able to access the webconfigurator using http to port 80 as expected.
The webconfigurator could be accessed with http://xxx:555 though.
Not saving a blank value on the tcp port would prevent telling the firewall to use the defaults ports for http/https which is a convenient feature.
Can this be fixed?By the way I found a similar problem in captive portal under a zone configuration, where once "Use custom captive portal page" is checked, if unchecked it does not save the unchecked value but keeps it checked.
-
@jjstecchino said in Webconfigurator doesn't save webgui tcp port if blank and others:
As a result, after saving the changes I was not able to access the webconfigurator using http to port 80 as expected.
Yeah ....
I had togrep '<port>' /cf/conf/config.xmlI know the first one is the one used by the web server used by the GUI.
to figure out that "leaving blank" actually means : "don't change" (?) and not 'go back to 80 if http is chosen, and 443 if https is chosen.@jjstecchino said in Webconfigurator doesn't save webgui tcp port if blank and others:
By the way I found a similar problem in captive portal under a zone configuration, where once "Use custom captive portal page" is checked, if unchecked it does not save the unchecked value but keeps it checked.
Correct, it says checked until you click these two buttons :
as soon as the second button is clicked, "Use custom captive portal page" will become not selected.
-
Thanks for the report, redmine here: https://redmine.pfsense.org/issues/14820
