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

    Forwarding to another port?

    Scheduled Pinned Locked Moved NAT
    4 Posts 2 Posters 1.4k 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.
    • J
      joebobfrank
      last edited by

      I have set up a webserver to listen on port 667. I have successfully forwarded a port on the "Firewall > NAT" page on  port 667 because port 80 did not work. Real simple, real easy. Then I made the webserver listen only on port 80. After some research, then tried port redirection and got it to work. By typing in the browser http://my.fake.site.net:667 I was still able to get to the site. I guess the ISP has blocked port 80?

      I now have to add the port number after the URL to get to my site. I would rather just have people type in the URL without the number. Given that, I tried to redirect port 80 to another port (same port the webserver is listening to) it did not work. Why?
      How do I set up my router to allow people to type in only the URL without the number? Do I do that in the router or somewhere else?

      1 Reply Last reply Reply Quote 0
      • C
        craigduff
        last edited by

        What about if you made your website secure? and forwarded 443?

        Some ISP's block port 80 especially home users, because its not secure and notorious for attacks.

        Do any of your port forwards work in your current Pfsense installation? Like RDP 3389? or SSH 22 etc etc

        Kind Regards,
        Craig

        1 Reply Last reply Reply Quote 0
        • J
          joebobfrank
          last edited by

          I'm not forwarding any ports. I just did 80 as a test. Thanks for the idea of using 443.

          @craigduff:

          What about if you made your website secure? and forwarded 443?

          Some ISP's block port 80 especially home users, because its not secure and notorious for attacks.

          Do any of your port forwards work in your current Pfsense installation? Like RDP 3389? or SSH 22 etc etc

          1 Reply Last reply Reply Quote 0
          • C
            craigduff
            last edited by

            ok but if you going to forward 443 you will need to apply a cert to it. Either Self signed or a legit one.

            Kind Regards,
            Craig

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