Nextcloud, hands down.

I use Borg to backup the default volume directory and my compose files. If you’re interested I can share my backup script.

While that’s an easy solution it makes it impossible or rather difficult to restore single containers and/or files.

I’m using a cheap VPS that connects over Tailscale to my home server. The VPS runs Nginx Proxy Manager, has a firewall and the provider offers DDOS protection and that’s it.

Take a look at Nginx Proxy Manager and how to set it up. But you’ll need a domain for that. And preferably use a firewall of some sort on your server and only allow said ports.

Or just install the browser add-on.

Hetzner Storagebox

It’s pretty straight forward:
https://wiki.archlinux.org/title/NFS

Maybe you can create an NFS share on your remote system and mount it on your local system, then create a Borg repo there as usual.

Borg backup all the way.

Not sure how lightweight it needs to be, but I use Ghost and it’s pretty simple and basic.

An initial library scan with 19k assets: 1m40s down to 9 seconds.

Insane!

Jellyfin is pretty nice for music too. I use it with Finamp, an Android client.

After changing the MTU to 1200 I have no timeouts anymore, but a lot of read ECONNRESET errors. -.-

I just changed the Docker’s MTU to 1200 and will observe the change.

So the MTU of Tailscale is actually 1280, but is the connection even going through the VPN or rather through my VPS, when Uptime-Kuma is trying to connect to my local domain?

Thanks, since I access my home network and server through the public IPv4 of a VPS via Tailscale this could actually be the issue. I’ll look into it, when I find the time.

Not sure how this helps, but here you go.

Yeah, I suspect it’s simply an issue on the side of DuckDNS. :/

Yeah, it works fine through my browser. Sometimes the websites load a little longer. I feel like it’s an issue with DuckDNS as it’s seemingly random when it works and when not.

IPv6 doesn’t work:

docker exec -it Uptime-Kuma curl -6 proxmox.datenprolet.duckdns.org
curl: (6) Could not resolve host: proxmox.datenprolet.duckdns.org

Besides that the issue has disappeares since last night. I automatically restart all containers at night and moved from uptime-kuma:1 to uptime-kuma:latest. That shouldn’t make a difference, but maybe it did?

And it’s not a typo in my config, but in my post. But good catch. ;)