Trying to view website brings up Wedconfig not website
-
Are you trying to test inbound traffic from the server itself?
-
Let me guess… You are using a reverse proxy of some sort?
-
-
All I'm trying to do is view the site from the browser on the server. Nothing fancy at all. I may have a fancy misconfiguration, but a whole nother thing.
-
Yeah - But I bet he will get the same problem even if browsing from a vpn on pfsense or perhaps even the LAN.
-
All I'm trying to do is view the site from the browser on the server.
Dude, how on earth do you imagine to meaningfully test port forwarding from localhost on LAN? WTF. So far, you've tested your DNS records. They're broken. Congrats.
-
http://browsershots.org/
-
I'm not trying to test port forwarding via localhost…locahost is just the only thing that works.
I am RDP'd into my server.
From my browser on the server I try to access the website via DNS my.website.com I get webadmin instead
From my browser on the server I try to access the website via IP I get webadmin instead
From my browser on the server via 127.0.0.1 I get the site. -
I am RDP'd into my server.
Why? This is just utterly useless test.
From my browser on the server I try to access the website via DNS my.website.com I get webadmin instead
From my browser on the server I try to access the website via IP I get webadmin instead
From my browser on the server via 127.0.0.1 I get the site.As noted above, the only thing you have tested is that the server is unable to resolve itself in DNS.
-
Are you getting multiple public IPs with NAT?
-
No. just a single public IP and single internal IP (other than the gateway)
I've added the local IP/Name to hosts so I can now access the site and continue to debug…which was my only reason for the question.
Still don't understand why webadmin on 192.168.1.1 was coming up when browsing the DNS name or external IP. I assume it's something to do with the way I have port forwarding set up. This is the first time I've set up a publically accessible webserver. I've always used colocs who handle the firewall setup. It's also the first time using pfsense.
-
Its being caused by NAT. But I have very limited info on your setup.
If you are using NAT Reflection, may be an issue also.
Sounds like you have found a fix though. So, thats good.
I've never had this issue using a single IP - Only multiple NATed public IPs.
-
I've added the local IP/Name to hosts so I can now access the site and continue to debug…which was my only reason for the question.
Your webserver should resolve to the pfSense WAN IP from outside, and to the server's LAN IP from inside. And no, editing hosts file on LAN boxes is certainly not a solution.
-
This:
https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networksSteve
