Cannot access internal web server from outside



  • I have just installed and configured 2.0.1-RELEASE (amd64). It's a basic installation with NO packages.

    I created an NAT port forward from my WAN to my internal web server on port 80.

    However, I cannot access the web server from the internet. I can access it from my internal network.

    I am also SURE that my ISP is not blocking port 80 as I just used the same connection to host my web server before I installed the firewall.

    There's nothing showing in the firewall logs either.

    I have included my config as images.

    Can please someone help as I am lost.

    Thanks







  • Go to system/advanced:

    Under "webConfigurator"  set your pfsense box to a different TCP port than 80…  (Then remember it... )



  • And also change protocol to https. ;)

    8443 maybe easy to remember.



  • Hi,
    Thanks guys for the prompt reply.

    However, unfortunately, it did not work.

    I changed the webconfigurator to https on a different port.
    I also deleted all rules and recreated them (see attached pics).

    I don't know what I'm missing.

    If you have any ideas, you are more then welcome to help.
    Thanks



    ![firewall lan.jpg](/public/imported_attachments/1/firewall lan.jpg)
    ![firewall lan.jpg_thumb](/public/imported_attachments/1/firewall lan.jpg_thumb)
    ![firewall wan.jpg](/public/imported_attachments/1/firewall wan.jpg)
    ![firewall wan.jpg_thumb](/public/imported_attachments/1/firewall wan.jpg_thumb)



  • use tcpdump on console to see these port 80 packages arriving.

    If you have a dsl router, configure pfsense ip as a dmz server on modem gui.



  • Port forwards override your web interface port, doesn't matter whether you change that. Go through the steps here:
    http://doc.pfsense.org/index.php/Port_Forward_Troubleshooting



  • Thanks guys for your help.

    I managed to NAT port 80 successfully after changing the admin port to a port other than 80 and used SSL on a different port as well.


Log in to reply