General Questions

My apologies if this question is asked and answered elsewhere.

This morning I changed the webgui protocol from http to https.  Now I am no longer able to access the webgui.  If I try to hit https://monowallIP with a browser I get "unable to connect".  If I try http://monowallIP I get "401 Unauthorized".  I am able to ping the IP address.

I just ordered a null modem cable and can check the serial console for options tomorrow but is there something obvious I have messed up here?  Does the serial console even have an option that would allow me to change the protocol back to http?  Some of the documentation I found leads me to believe this isn't an option in the console.

Monowall is running on a 3 NIC WRAP.  I haven't backed up the configuration in quite awhile and though reseting and starting over is an option it would be a fair amount of work to recreate the nontrivial numbers of dhcp reservations, nat/firewall rules, and local dns entries.

Any ideas?

Hmmm... Do you remember if you inadvertently specified a different port for the webGUI?  I guess you could try to port scan your m0n0wall box from the LAN-side to see which port is running http or https ... use "Nmap m0n0wallIP".  The console doesn't have the option to change between http/https, but you may want to try to reboot the system -- backup your config on the CF card just in case.

If nothing else, if you change your LAN IP at the console, it'll give you the option to revert to HTTP.

In case someone else has a similar problem, I think there may have been an issue with me trying to change the webgui password and protocol at the same time.

I tried to change both with 1 save and ran into the problem described.  nmap showed no port open for https.  I received the null modem cable today and reset the webgui password using the console interface and everything began behaving.

After the password reset https was listening on the standard port and I was able to connect and then set the password to what I wanted.  If a password reset == m0n0wall reset then maybe it was just the reset in general that fixed things.