Also, the reason for nextcloud update is that it has some slightly tricky optimization to change ownership of files carefully. It also changes the default data directory of newer nextcloud installations.
@LoudLemur looks like the DNS record was pointing to a Cloudron which didn't have any app installed on that (sub)domain. If a Cloudron server as such just gets deleted, then the DNS records are not automatically cleaned up, since there is nothing running anymore to do that.
@girish & @mehdi - thanks for your advice! It gave me the idea to Tailscale. I installed it on the Cloudron server and was able to successfully mount a shared folder from my Synology using cifs. However, even though the data persists between reboots, I don't see the data on the Synology, even when I'm logged in as the root user. I'm not quite the linux expert, but I noticed that when I changed Nextcloud's appdata folder to point to the mount, it created it as a "root" user. On the Synology, I created a Cloudron user that has the necessary permissions and I mounted the shared folder with the Cloudron user, password, and domain. So, I'm thinking this has something to do with user IDs not matching up or something like that.
I'm nervous about moving forward since I can't actually see the data on my Synology. Would you or anyone else have any advice?
By the way, this is how I mounted it:
sudo mount -t cifs -o credentials=/etc/nas-credentials,vers=3.0 //nas/Cloudron /mnt/nas
In fstab, the command is:
//nas/Cloudron cifs -o credentials=/etc/nas-credentials,vers=3.0,_netdev,auto 0 0
the issue could start with a lot of concurrent users and a lot of small changes to file, due to SMB not working at FS lvl but at file level/block of data.
IF hetzner would offer NFS, that could be a solution or better even if there would be support for iscsi.
@jodumont yes. Samba is the only protocol on your list that is really made to be mounted locally. Personally I would try to avoid having to rely on php for access to remote filesystems (regardless of the protocol).
@Bortseb Yeah, best way to get familiar eh! Always worth making up your own mind, I just added in case you were a disappointed once you did get connected and to be aware what I think at least is worth your time on setups, as I know from years of System Admin for a team of about 50, they can often only be as quick or organised as the tools we give them.
Good that it works now. For clarification, an app restart will reset all Cloudron specific settings, in case they were misconfigured or more importantly in case the information has changed on the Cloudron side (like a password, port or secret)
@girish They are unusual I would say, yes. It's a file that is being updated on a daily basis so it has a file history of 30 different versions in NextCloud. They are .db.crypt12 files, which is a database backup of WhatsApp about 120MB in size.
@necrevistonnezr indeed, previous versions of Cloudron would allocate more memory for redis based on the app's memory limit. This limit was not settable by the user. In 5.2, we have made the redis limits visible and configurable by the user. Our 5.2 migration script should ideally could have been smarter and allocated more memory to redis.
@m-si someone may find a way to package it, however, I've found it to be much easier to run a dedicated set of servers for NTHPBE. I offer it to clients for a pretty low fee in either US or DE if you are at all interested.