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

Can't access Web Sites behind nginx reverse proxy.

Scheduled Pinned Locked Moved General pfSense Questions
7 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.
  • D
    DonWood
    last edited by Dec 12, 2019, 12:06 AM

    I've had 4 web sites up and running for awhile now. I have a cable modem with a linksys router that port forward my http and https traffic to my nginx reverse proxy server. I decided to step up my protection and installed a pfsense router on a VM and I have it up and running. The problem I have is I can't get it to port forward the http and https traffic to the nginx reverse proxy server. I can get to the public side, ping google, and I can ping my internal machines I just can't seem to get to the web sites on my side from the public side. Can anyone point me to a post that has a similar problem. I have googled a lot of articles and tried a lot of setups but nothing has worked so far.

    1 Reply Last reply Reply Quote 0
    • S
      stephenw10 Netgate Administrator
      last edited by Dec 12, 2019, 1:20 AM

      So you replaced the Linksys router with pfSense?

      Can we see screenshots of your port forward setup?

      Steve

      1 Reply Last reply Reply Quote 0
      • D
        DonWood
        last edited by Dec 12, 2019, 1:32 AM

        Steve sure I will have to do it tomorrow and send them to you. its been a long day. If there is anything else I can send let me know.

        1 Reply Last reply Reply Quote 0
        • D
          DonWood
          last edited by Dec 12, 2019, 1:46 AM

          Well who needs sleep

          Nat.JPG rules.JPG

          1 Reply Last reply Reply Quote 0
          • S
            stephenw10 Netgate Administrator
            last edited by Dec 13, 2019, 8:22 PM

            The destination address in the port forwards should be the external IP, usually the WAN IP.

            Steve

            1 Reply Last reply Reply Quote 0
            • D
              DonWood
              last edited by Dec 13, 2019, 11:26 PM

              Hey Steve thanks for the reply but it doesn't make sense.
              If someone wants to access my web page the request comes to my public ip. Hits my router and needs to get to my reverse proxy to be forwarded to my web servers. How is the destination set to the wan ip going to hit my proxy server to direct traffic to the web servers?

              1 Reply Last reply Reply Quote 0
              • S
                stephenw10 Netgate Administrator
                last edited by Dec 14, 2019, 8:33 PM

                Because the NAT IP is set to 192.168.1.4, the proxy.

                The destination IP defined what traffic that port forward will match on coming into the WAN. Unless you have more than one public IP on the WAN it can only be the WAN IP.

                Steve

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