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
In what sense is DuckDNS unreliable?
It seems to frequently stop responding.
I was wondering the same, I've not had any issues personally
Glad it works for you guys. Here it fails to respond at least once a week or so, and it can last one hour or more sometimes. It's unpredictable. And makes the server look buggy.
A sample for measure...there's a lot of these on reddit:
https://www.reddit.com/r/selfhosted/comments/1cyru6p/duckdns_dns_servers_down/
Does your IP address really change that often?
Does it matter?
No, it does not change, but why is this something of concern? The problem is duckdns DOES NOT REPLY providing DNS replies, not to my own servers, but to people outside looking for my servers by typing their address. Duck fails to provide a response to those queries, and users get timeouts. I can frequently replicate this with either dig or nslookup, from different machines, either inside my network or at random connections.
I managed today to run certbot to register 2 new subdomains that yesterday consistently failed with a long timeout during THE WHOLE DAY. Today the same certbot command on the same server ran straight at the first attempt.
So...yeah. Unreliable.
Oh I thought you meant it just doesn't reply to DDNS updates. If it doesn't even reply to DNS queries, yeah that's a big issue. What did their support have to say about it?
...what support? They barely reply any queries people post in their google groups. If you go there you'll see most people will try to reach them either due to servers down (the main issue at hand) or login issues which never get fixed (the longest standing issue, better create a different new subdomain) from what I've seen. I've also tried repeatedly to reach them regarding changing the token access, but with no luck. It's a free service so I can't complain, but the only support you actually will get is from other users, and for some scenarios that's not quite enough.
EDIT: Oh wow right after posting this I just saw they actually replied regarding the SSO/tokens issue most people have (SSO failed due to the reddit snafu, you end up with just the token and no chance to do any further changes to your account again). This has been an ongoing issue for over two years, I just saw they finally replied (I think for the first time) a couple of weeks ago.
Oh if they don't even have support, yeah I would have moved away a long time ago.
DNS cert renewal randomly stopped working for me.