That feature kinda works, but it’s incredibly fragile. It has caused so many annoyances for me over the last year or so that I’m finally done with the thing. Just go with immich instead, less headache.

This actually sounds quite interesting. Is this controlled with DNS entries at the domain level somehow, or is the subdomain fixed/mandatory?

Yes exactly. I didn’t wanna name-drop them cause they are closed for new dynDNS signups. You can create an account to manage your own domain, but you currently can’t signup for their dynDNS service, unfortunately.

That being said, I would still highly recommend them for managing your own domain, if you’re looking for a place to host literally just the DNS part.

There are dyndns providers that support the DNS challenge that have free tiers. Those are sufficient, and you can even get wildcard certs for your subdomain that way. Perfectly sufficient for a homelab.

The native Android client just can’t do two way sync. Just put a text file or something into any folder (from the web or desktop). Now sync that folder to Android. Now edit it on the web/desktop, and look for the changes on Android (without actively telling it to “sync”). Then change the file on Android, these 2nd changes are never sent back to the server unless you explicitly tell it to “sync” again, manually. That’s what I mean with 2 way sync.

There are quite a few files where you just need that to work to use them properly, like the database of a password manager as a prime example. Mine can talk to Nextcloud natively, so I don’t need the client for that, but I was incredibly close to just switching to syncthing, if I didn’t have active users that use the web office integration of Nextcloud.

Nextcloud can’t do two-way sync on Android. At all. That’s like core functionality for the product IMHO and there’s a feature request open I think. When I found that out, I basically spit out my coffee. It’s fine if you just want to upload photos you take, that kinda works (but my god is it fragile).

Nextcloud is pretty good at quite a few things, including extensibility, but having some omissions in functionality that boggle the mind.

Another name, depending on the exact context, is “hairpin NAT”. Should make googling with the specific router OP has easier.

I think you overestimate how large the percentage of people leaving actually was. Wish it was, but don’t think the number actually leaving made a still visible dent in their traffic graph. surely some toric specific knowledge did leave though.