Selfhosted

43626 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

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 2 years ago

MODERATORS

[email protected]

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

submitted 1 day ago* (last edited 1 day ago) by [email protected] to c/[email protected]

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

[–] [email protected] 2 points 1 day ago* (last edited 1 day ago)

I've got the same problem since a month or two with another dyndns provider. That's not specific to the dydns provider. It is the router. Yet I have no idea how to fix it, and I am too lazy currently.

I'm on graphene, btw.