I have my home server apps configured with NGINX proxy manager and DuckDNS to access remotely, but about three weeks ago DuckDNS URLs stopped working on my home network. I can access 192.168.XXX.XXX:1234 on the home network but myapp.duckdns.org times out.
It DOES work as expected using a VPN or on mobile data.
Any ideas as to what’s going on?
EDIT: I kind-of sort-of got a workaround working using pi-hole “local DNS” feature to point the duckdns URL to NGINX. Didn’t work
EDIT 2: Disabling the router’s firewall completely seems to have fixed it. Still trying to figure out the exact setting that did it. I will update this post if I can.
I had the exact same issue. My troubleshooting took me to my router. Nat Loopback and hair pinning.
Your router might have some options relating to NAT loopback or hairpinning. Apparently this can happen if your router recently had an update or if it was restarted abruptly and didn’t boot properly.
Try restarting your router. It didn’t work for me and my router is too basic for those options so in the end I took down my Nextcloud and remade another container and started from scratch. I had all sorts of things fucked with my instance so it just made sense to toss it out and fix it again.
Hope it works for you!
Thanks for the response but restarting the modem/router didn’t change anything, nor did creating a new container/NGINX config.