this post was submitted on 08 Mar 2025
25 points (90.3% liked)

Selfhosted

43809 readers
573 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 2 days ago (1 children)

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!

[–] [email protected] 3 points 1 day ago

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