Me too. After a disastrous episode with DropBox while travelling in foreign countries nearly a decade ago, I instituted my own File Server that's accessible via the Internet. All of my data is 'safe at home' with daily backups.
Me too. After a disastrous episode with DropBox while travelling in foreign countries nearly a decade ago, I instituted my own File Server that's accessible via the Internet. All of my data is 'safe at home' with daily backups.
I now keep my primary 'work' and 'private' collections (10-30g each) and a large shared set (350g) synced across desktop & laptop, and also 3 off-site archive servers, using Syncthing. This includes a literal satellite connection for one site.
Its less of a hassle to use something like nginx reverse proxy docker container in front of your web services, as it comes preconfigured with some best practices regarding TLS. (TLS1.2+ only by default) https://hub.docker.com/r/jwilder/nginx-proxy
If you use docker, be sure to google around how to manage firewall with containers (must use DOCKER-USER chain instead of INPUT)
Ofcourse, you will get a bit involved in setup step if you choose to tie nginx proxy, letsenccrypt and nextcloud containers. But search engine is your friend.
What was that? They cut your access because you logged from a different IP?
Except that it worked in reverse. My laptop was 'emptier' than the home server, so the home server's files were deleted to match the laptop. Hundreds of megabytes of files were destroyed before I managed to stop it.
On top of that, I only had a 2 gig per month quota for internet access while travelling, and all the DropBox activity soon exhausted that in days.
On later trips my own home server coped very well, with less overall unwanted activity.