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

Selfhosted

60831 readers
933 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 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
[–] Dangerhart@lemm.ee 3 points 1 year ago* (last edited 1 year ago)

Are you using your router as DNS and DHCP? With Verizon I had a security setting that was blocking public DNS entries to resolving to local addresses. I can't remember what it's called, but it's to prevent a certain type of attack. For a while I disabled it but switching to pihole as DNS, DHCP and using unbound solves it without the security implications