@girish Thank you very much for the info. I didn’t manage to reply earlier, but I saved the backup configuration again and the morning backup completed successfully. I’ll also try upgrading to 9.0.15.
Also note, I am waiting for 9.0.14 to be stable release before I can update and then download a backup. Currently it's not possible to download a backup in 9.0.13 from Cloudflare R2.
@philkunz said in Backups still not verified or what?:
But that points to how important the e2e read back step is.
absolutely, that is why we are adding the validation in the first place. Having checksums of what we expect is the first step, next then will be the task (can be quite heavy task, so this won't be automatic probably) to read back and recalculate the hashes.
@timka S3 is a pseudo-standard. Tthere is no spec for s3. AWS made a service and then lots of other services made compatible services by reverse engineering. Because of this, there are subtle differences in various implementations. The provider type is just a way for the code to add some provider specific hacks in the code. With that in mind "S3 API Compatible V4" just gets your the generic s3 protocol without any hacks I think it's complicated to document what the hacks are but it's all inside https://git.cloudron.io/platform/box/-/blob/master/src/storage/s3.js?ref_type=heads
Minio is basically dead for community edition.
I rolled back to image: quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z (last version with all management features - don't expose it publicly for security reasons)
Then: Configuration > Region > Restore Defaults
That wiped my region entry and now Cloudron connects properly again. Time to consider successor software now.
yes- was my error/ all resolved. Issue was I had disabaled some of the app backups under app level but then had selected to back these up in global settings but seems the global settings do not overide the app level backup settings/ nor is there anything in global settings to inform backups for sepcific apps have been turned off at app level (maybe this could be added).
@girish Thanks ! I replaced the /home/yellowtent/box/src/storage/gcs.js with the patched version and don't get the "old backup not found" error. the backup is listed in System backups. everything seems to be fine ! Thanks a lot for your help !
@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 .
This has gone back to normal for a few days in a row, indicating the upgrade didn't produce an issue, but probably the hardware infrastructure at Netcup.
@nebulon , per request:
https://forum.cloudron.io/topic/14525/improving-user-experience-with-ssh-keys-for-sshfs-and-volume-mounts
Many, many thanks. And, if I find anything useful, I'll update that thread. Or, this one, and cross-link.
@dylightful If we can have access to your setup, can you write to me at support@cloudron.io ? Would love to debug and figure out why it's failing . Is this reproducible easily - meaning if you take a backup and restore, it fails?
