Cloudron Forum

@tecbox thanks for the update!

There was a bug in Cloudron when backing up directories where the contents keep changing very quickly. This is fixed in https://git.cloudron.io/platform/box/-/commit/42cefd56eb9f89cfb6c7e35d6410dd5b7dbfa45d . Other than the above, the slowness is because of the usage of a cache plugin and this cache plugin's data is being backed up. Since it keeps changing all the time, there is a lot of stuff to clean up and reupload each time. A solution is to configure the cache plugin to use /run/xx path instead of /app/data . This should make things considerably faster.

Haven't been able to find a solution and just dealing with the notification of not using a CDN while using the S3 storage.

@avatar1024 in the previous versions, one could change the backup format between tgz and rsync . We used to track the format of each backup (for restore from old backups to work). in Cloudron 9, you cannot change the backup format of a site once set. instead, you can just create a new backup site if you want another format. The migration code probably detected that you have backups in both formats. So, it would create two sites - one tgz and one rsync. That's what you are seeing .

Hello @JueBam Did you get this resolved or is further assistance required?

Thx for the hint. Will see what Hetzner support has to say.

It worked after I have reset my ssh keys and entered a new one during restoring.

It was not fail2ban - it was IPv6 connection which is failing, as IPv6 disabled (to ensure mail works well). Hetzner's supported provided a very quick and efficient verification / troubleshooting step: ssh -vvv -p 23 user@server - hope that will be of use for anyone else in the future.

We were able to resolve this. The root cause was the missing unbound-anchor ubuntu package. After intstalling this it worked. More info on that issue is at https://forum.cloudron.io/topic/12496/unbound-anchor-not-found-in-ubuntu-24-04?_=1727881329798

FYI the migration to Hetzner Storage Box coming from Contabo Object Storage was worth it and fixed all failures related to backups whether it was in term of stability or duration. I didn't encounter issues yet, despite I'm using encrypted backups and i've plenty of apps including Nextcloud but I don't have as much data on it.

@girish Ok, great! Thank you very much for the information. I really appreciate your time. Thanks again!

@3246 I spotted you just upvoted my post above where I asked. I said in How to setup Hetzner Storage Box using SSHFS: People who are backing up to a Hetzner Storage Box using SSHFS - how did you get it set-up? Thanks! Here is what worked for me: https://forum.cloudron.io/post/96271 Once I worked out how to create the new key pairs it was all relatively straightforward.

So, the mounting is handled by the kernel and Cloudron as such has nothing to do with stability of the mount. Cloudron is really just a user space program. You can find the mount systemd file in one of the mount files in /etc/systemd/system/*.mount . Maybe you can look for hints in dmesg (but often unmount information logs is not there)

nevermind, i found my mistake, i copied my public key in, not the private key -.-

@nebulon Thank you for your response. Yes, it seems the issue is indeed with hardlinks. I have them enabled. I will try to wait for the Cloudron update, or I might consider using Borg for backups to the Storage Box. That should probably resolve the issue. Another option is using rsync with the -H switch, but I haven't tested it yet. Thank you very much for your help.

Yes it´s possible. Watch the video!

@santabroo I did once have all my Calibre Web books stored on a Hetzner Cloud Volume (different from their storage boxes) and have that Mounted as Cloudron Volume. I was rsync-ing my local Calibre Library up to that Hetzner Cloud Volume. I'm not sure if I ever tried upload via the Calibre Web interface too, but if I did I can't remember what happened. I think it very likely would work though if you moved your Calibre Web app Data Directory to a Heztner Cloud Volume but of course this would only be possible if your Cloudron is running on a Hetzner Cloud VPS.

It seems the options --storage-driver=overlay2 makes docker unable to start when the data-root is on a mounted through sftp : adding it through the following error at startup failed to mount overlay: invalid argument storage-driver=overlay2 if I use it with a regular data-root, no errors show up. I guess we should conclude that this makes cloudron not compatible with sftp drive for storing docker images.

Please follow the thread at https://forum.cloudron.io/topic/9333/hetzner-storage-box-cifs . Just trying to keep all this CIFS related stuff in one place.