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.

  • tychosmoose@lemm.eeEnglish
    2·
    1 day ago

    Could also be a stale DNS cache entry on one device or the router. If you ping your duckdns fqdn from the device that can’t connect while on your home network, does it resolve to the correct public IP?

    I still think a firewall/nat issue is more likely tho.

    • Jediwan@lemy.lolOPEnglish
      2·
      1 day 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