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.

  • CmdrShepard42@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 hours ago

    I don’t know if this will be of any help, and I dont fully understand the intricacies, but I run into similar issues with my HomeAssistant setup when the certificates expire (every couple of months?). The issue is that HA doesn’t pull the new certificate without a reboot, so I typically just restart it every once in a while to ensure that it has the newest certificate.

    • Jediwan@lemy.lolOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      14 hours 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.