1
General Discussion / Help with Port Forwarding, Please?
« on: November 15, 2020, 06:47:38 pm »
Hi, guys. I've been at this for hours and just can't figure it out. What's worse is that I don't know if it's an opnSense issue or other. I hope you can help.
My setup:
Basically, when I try to connect to 192.xxx.xxx.11 via the xolocrafts.duckdns.org host name, I get this:
I set up the NAT Forwarding this way:
I assume that I can NAT Forward from WAN to LAN, but if this is incorrect, then it's part of the problem. I have tried to temporarily stop the Web Proxy, but I get a similar error: "Hmm. We’re having trouble finding that site. We can’t connect to the server at xolocrafts.duckdns.org."
Note that I used external Port 1080... that was just to see if there was any difference in results, since I initially used Port 80.
It seems that the Dynamic DNS setting is correct, since it IS routing it to the correct public IP address. From there, I don't know what is happening.
I haven't even set up SSL for this (my next step), but can't even get it working without it. Now..., if I simply type "http://192.xxx.xxx.11 in my browser, while connected to the LAN interface, everything works fine.
Do you see what I'm doing wrong?
Thanks for your help!
My setup:
- opnSense running on a computer with a 4-port NIC
- TrueNAS box connected to the LAN interface w/ IP address 192.xxx.xxx.10, assigned by opnSense
- Nextcloud plugin installed in TrueNAS w/ IP address 192.xxx.xxx.11, also assigned by opnSense
- opnSense Dynamic DNS is set up to use DuckDNS, routing xolocrafts.duckdns.org to my public IP address
Basically, when I try to connect to 192.xxx.xxx.11 via the xolocrafts.duckdns.org host name, I get this:
I set up the NAT Forwarding this way:
I assume that I can NAT Forward from WAN to LAN, but if this is incorrect, then it's part of the problem. I have tried to temporarily stop the Web Proxy, but I get a similar error: "Hmm. We’re having trouble finding that site. We can’t connect to the server at xolocrafts.duckdns.org."
Note that I used external Port 1080... that was just to see if there was any difference in results, since I initially used Port 80.
It seems that the Dynamic DNS setting is correct, since it IS routing it to the correct public IP address. From there, I don't know what is happening.
I haven't even set up SSL for this (my next step), but can't even get it working without it. Now..., if I simply type "http://192.xxx.xxx.11 in my browser, while connected to the LAN interface, everything works fine.
Do you see what I'm doing wrong?
Thanks for your help!