Web traffic is being redirected to webGUI



  • I have forwarded port 80 from the WAN interface to my webserver but http requests are still being redirected to the pfsense web configurator.  I have configured the web configurator to listen on a custom port for https traffic, I have checked "Disable webConfigurator redirect rule" in System > Advanced and the only NAT entries that would redirect http traffic direct it to my webserver on the LAN side.  I am also positive I'm connecting from the WAN side.  It might be useful to know that when I connect to http://<wan ip="">, I am served a certificate before redirecting to https://<wan ip="">:<custom port="">.

    I would expect that if I specify a particular port and protocol for webGUI, and disable auto redirect, that requests coming in on any other port and protocol be ignored (time out).  Additionally, i would expect traffic coming in the wan port be subject to the NAT entries and firewall rules and be redirected to the host on my LAN before reaching pfsense's webserver.  Am I wrong about this?

    Any input is appreciated.</custom></wan></wan>



  • Sounds reasonable. Have you tried clearing the states or restart the firewall?
    What does your firewall rule and NAT rules look like?



  • Gah!

    What we have here is an instance of browsers behaving badly.  I didn't realize what the problems was at the start because both IE and Firefox demonstrated the same behavior.  Once I tried Chrome however, everything worked as expected.  I think that because I had previously connected to the webGUI on http port 80 with both my browsers before, it kept pulling the cached page on my subsequent attempts and this is what was causing the redirect to https custom port.  Once I cleared the history and cache, everything is working as expected.

    Hopefully someone else can benefit from this information.



  • @pffan:

    Gah!

    What we have here is an instance of browsers behaving badly.  I didn't realize what the problems was at the start because both IE and Firefox demonstrated the same behavior.  Once I tried Chrome however, everything worked as expected.  I think that because I had previously connected to the webGUI on http port 80 with both my browsers before, it kept pulling the cached page on my subsequent attempts and this is what was causing the redirect to https custom port.  Once I cleared the history and cache, everything is working as expected.

    Hopefully someone else can benefit from this information.

    I did, I run into same problem, thanks.


Log in to reply