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

Port forwarding HTTP traffic on port 8080

Scheduled Pinned Locked Moved NAT
4 Posts 3 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.
  • J
    jan.gestre
    last edited by Mar 31, 2008, 7:50 AM

    Hi Guys,

    I need to port forward port 8080 in one of PC's on LAN however the rule seems to be not working. I have already port forwarded port 80 of the same machine successfully and I don't know why it doesn't work on port 8080. I followed the same procedure described here http://doc.pfsense.org/index.php/How_can_I_forward_ports_with_pfSense%3F

    Any idea what's wrong?

    TIA

    1 Reply Last reply Reply Quote 0
    • P
      Perry
      last edited by Mar 31, 2008, 8:07 AM

      Do you have a firewall on that pc. did you make test from another lan pc? is there a router in front of your pfSense box?

      /Perry
      doc.pfsense.org

      1 Reply Last reply Reply Quote 0
      • J
        jan.gestre
        last edited by Mar 31, 2008, 8:27 AM

        @Perry:

        Do you have a firewall on that pc. did you make test from another lan pc? is there a router in front of your pfSense box?

        I've disabled the firewall on that PC (WinXP) and I'm doing the test from outside the network. pfSense is the main router, no other router behind or in front.

        1 Reply Last reply Reply Quote 0
        • H
          hoba
          last edited by Mar 31, 2008, 11:17 AM

          Delete that portforward for 8080 and the firewallrule it created for it. Then readd the portforward making sure the firewallrule autocreate tickbox is still enabled. If that doesn't help either review your firewall rules at WAN. The order is important and in case you have some custom block rules there and the firewallrule is created below that one it won't match. If that still doesn't help edit the firewallrule and check the log option. Then retest and check your firewallogs at status>systemlogs, firewall.

          1 Reply Last reply Reply Quote 0
          3 out of 4
          • First post
            3/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received