July 31, 20223 yr Hello unraid community, Recently, I've changed my Internet Service Provider. My last modem/router was in bridge mode with a personal router behind. That was working well. All the port forwarding was in my personal router. My new ISP allow me to use my personal router with PPPoE (MTU 1492) WAN connection. So now my router have a public IP and I didn't made any change in the firewall or the port forwarding router config. All the PCs/Smartphones/VM have internet and work well. Unraid is reachable from internet with the myserver plugin, plex work well too. I can update doker/apps/etc... from unraid. But I can't reach my domain name from duckdns (example.duckdns.org). If I Ping it from WAN, it's not reachable. But a traceroute from WAN reach my correct public IP. I can reach my domain name from a Windows VM in my unraid server. I can reach my domain name from any device in my LAN but not from the WAN. But I can PING or traceroute my domain name from WAN, it's my correct public IP address. So if I'm right: My proxy manager Nginx work, Duckdns work and have my correct IP address. Where's the problem? Do you have any suggestion? Thx for reading me. mydeedee-diagnostics-20220731-0143.zip Edited July 31, 20223 yr by HerrGeneral More analyse
July 31, 20223 yr Author I don't think so. Hairpin is similar to Loopback if I'm right. And it permit to access services via the public IP address or domain name from inside the local network. Another PC on my LAN can't reach Nextcloud (for exemple) with his domain name but it works with his IP address. I can reach my domain name service from the inside of my lan with the VM too. My problem is the impossibility to reach my service via domain name from the oustide of my LAN. I think the Hairpin/Loopback problem is part of the symptom, not the solution. Is that right?
July 31, 20223 yr Author @Kilrah Thx for the reply and I don't think so because the traceroute reach my public IP address and Duckdns have the corret IPv4 (no IPv6) by subdomain. So the DNS is update to the correct IP. @BRiT Thx you too for your suggestion.
August 3, 20223 yr Author Solution My new ISP was blocking the port 80 and 443. That was the explication. Thx for the support. Edited August 3, 20223 yr by HerrGeneral
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.