Selfhosted
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!
view the rest of the comments
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.
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