Selfhosted

61512 readers

582 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.
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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

DuckDNS URL no longer working on home network? (lemy.lol)

submitted 1 year ago* (last edited 1 year ago) by flork@lemy.lol to c/selfhosted@lemmy.world

14 comments fedilink hide all child comments

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

[–] tychosmoose@lemm.ee 2 points 1 year ago (1 children)

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.

[–] flork@lemy.lol 2 points 1 year ago* (last edited 1 year 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