Yeah with a docker container running 24/7 and a phone app it’s much better. they also have a setting where deleted files on phone are simply moved to archive on the server.

Having setup both, ive found syncthing to be much simpler. I would probably not go through the headache of setting up https and databases for next cloud again…

How can you ever learn the risks of exposing ports if all answers are “if you don’t know you shouldn’t do it”?

The post explicitly recommends ONLY exposing the wireguard port, not 80/443/22 which one should usually not do anyways. Very different things!

Yeah it’s good to have a system separate from the main server. It’s always so frustrating having to debug wireguard issues cause there’s some problem with docker

Ssh behind a wire guard VPN server is technically more secure if you don’t have a key-only login, but a pain if the container goes down or if you need to access the server without access to wireguards VPN client on your device.

Use syncthing to sync and monitor your backups.

Syncthing backup server for your important files.

Cloudflare, namecheap, GoDaddy, domain.com, they all offer dns I think. Some of them are supported by Dyndns; you can find a list of supported providers.

So they profit from high-profile commercial users to subsidize the free tier (proxy, tunnels) and cheap DNS. What’s wrong with that? It’s not like we absolutely need those (proxy is nice but you can use vps, tunnels are also offered by ngrok).

Cloudflare

So it makes you IP less discoverable. However, if someone finds your IP randomly (through brute force), would you still be vulnerable? Or is it possible to only port forward to a static CF address so only CF can connect to you outside of your home network?

How is getting a domain protecting you IP? Wouldn’t your IP still be accessible even after you link it to a domain?