Yeah I’m really curious where the difficulty lies. Nextcloud was one of the earliest, if not the first, services that I deployed on a server when learning about Linux/Docker from scratch. The evolution of my setup has mostly been through my better understanding of container management practices than through anything Nextcloud specific.

My only Nextcloud specific issue has to do with the implementation of a reverse proxy (NPM) breaking the ability for my Nextcloud and OnlyOffice containers ability to connect - and I’ve not been so fixed about it that I haven’t really sat down trying to figure a fix.

Not directly an issue, however I found NextCloud and OwnCloud to much bloated and not very responsive. I tried all the possible alternatives and they all had some strange drawbacks (proprietary database, chunked into some weired file format…)

Sure I could just use my nextcloud instance without all the possible add-ons, but I just wanted a simple and a reliable cloud service that just syncs my files between my devices without all the bloat.

My final argument would be that it is written in PHP… Programming language of the past ! While I’m probably wrong on this one and I do have no idea of the programming language realm and probably evolved over time, I do prefer something written in a newer more “secure” language.

So that’s why I settled with syncthing. It’s not a cloud service but a syncing service. It’s different but has the same purpose in the end with more configuration options on how/where and when to sync between my devices.

As a final note (cauz I remembered something) 3 years ago I had a really hard time to make NextCloud work properly, via docker, with my reverse proxie (Treafik) I had to allow it manually in a configuration file and still didn’t work great, but was probably my skill issues at that time :).