Can't access Web Sites behind nginx reverse proxy.
-
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.
-
So you replaced the Linksys router with pfSense?
Can we see screenshots of your port forward setup?
Steve
-
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.
-
Well who needs sleep
-
The destination address in the port forwards should be the external IP, usually the WAN IP.
Steve
-
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? -
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
