…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.

Thanks. I’m seriously considering also a paid domain, so it’s good to hear from your experience. I might go try some other free provider first though.

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.

Great…thanks. I’m going to look them up.

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/

It will fail to resolve randomly, and then your services goes down. And you expend quite a while figuring out whatever might have failed until the typical “when in doubt, it’s DNS” pops up. This also applies when you’re trying to add/renew subdomains.

Just a sample…

https://lemmy.world/post/13565617

It seems to frequently stop responding.

You only need to see how young Tom Scott looks in the video to know this is indeed very old news. They seem to have necroposted this thing from 10 years ago and posted it now without any reference about when the events happened, to make it seem relevant/recent.

Thanks! But…where is the folder specified there? I can only see the temp client body path, but I’m not sure that’s where files will be uploaded.

That would be if it ends in the news if a store uses it. I definitely can’t imagine people stop using their main grocery store off from a rumor like this.

Evolution in Linux does.

This is great news! I have some small project I’ll be taking in a location with cgnat, I’ll be visiting it in November. This will be of great help, thanks so much!

My big question…will this work on blocked locations, as in a router running behind cgnat? No open ports. Does Tailscale solve this?

Thanks!

…but it can’t run both in your phone and in your computer, right? For that you need the desktop app (which is Windows only) or the web app, which linux apps encapsulate right?

What’s this about? I didn’t hear anything about it.

I don’t think I need them over 2000W. Thanks!

The way i understand it, this stops maintenance for Syncthing, but Syncthing-fork in fdroid will continue its development and support as usual. Both show if you do a Syncthing search in fdroid. The fork is more up to date with features.

The way i understand it, this stops maintenance for Syncthing, but Syncthing-fork in fdroid will continue its development and support as usual. Both show if you do a Syncthing search in fdroid. The fork is more up to date with features.

Also a fork that has been ongoing for years, syncthing-fork.

The way i understand it, this stops maintenance for Syncthing, but Syncthing-fork in fdroid will continue its development and support as usual. Both show if you do a Syncthing search in fdroid. The fork is more up to date with features.