flork

joined 1 year ago
[–] flork@lemy.lol 2 points 2 days ago

Thanks, but I don't think that's it. I rebooted and also tried adding a new container to NGINX with a DuckDNS url and it won't load on the local network.

[–] flork@lemy.lol 2 points 2 days ago

Well like I said DuckDNS is working

[–] flork@lemy.lol 2 points 2 days ago* (last edited 2 days ago)

Hm, pinging works and shows my (external) IP. But no device I've tested can load the duckdns URL.

~~EDIT: Two of the URLS show the local IP replying when pinged. Not configured any differently so I'm not sure what's going on there.~~ This was a PiHole thing apparently

[–] flork@lemy.lol 3 points 2 days ago (2 children)

Yes and DuckDNS is working flawlessly everywhere except that the network the server is also connected to.

[–] flork@lemy.lol 1 points 2 days ago (2 children)

Arris G36 but I don't believe that's the issue as it was working for years before now and on a different router too.

[–] flork@lemy.lol 3 points 2 days ago

Thanks for the response but restarting the modem/router didn't change anything, nor did creating a new container/NGINX config.

 

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.