Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Apache on port 80 NAT

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 2.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • 6
      65 mustang
      last edited by

      Hello,
        I recently added a Firewall -> nat rule to forward all incoming WAN:22 traffic to LAN:192.168.2.5:22 and that worked fine.  I was able to ssh into my LAN system from the WAN public address.

      So i setup a webserver on the same LAN computer i made the ssh NAT rule for.  I have apache running on port 80.
      I added a new NAT rule just like the ssh rule that i added before but this time for port 80.  Although it does not work.

      It did create the correct firewall rule also.  Port 80 is open to the WAN.
      Any ideas?

      1 Reply Last reply Reply Quote 0
      • H
        hoba
        last edited by

        Did you manually create the firewallrule or was it autocreated when adding the nat entry? In case you created it by hand let us see the rule please. Make sure the host behind the client has no own forewall and uses the correct gateway. You also have to test this from the outside  (in case you try this from the inside it won't work without natreflection turned on but this might cause issues with your webgui if it still listens at port 80).

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.