Unable to Backup Since Updating to 8.0.3

[nebulon]

The error might come from the self-signed certificate on your backup storage, not from your Cloudron.

Which backup storage are you using and does that have a valid cert?

[Shaun Snapp]

BTW, I just reset the certificates in Cloudron and retried a backup and got the same error.

I am using Digital Ocean. I can't find anything about certificates in my settings. And Digital Ocean would not have started asking for this just on the 16th. I am thinking that the 8.0.3 Cloudron update made a change to the backup such that a self signed certificate is necessary for the backup. I made no changes to anything in the backup and never even went into Digital Ocean to change anything.

[Shaun Snapp]

Notice this update note for 8.0.4

"ami: IMDv2 support
apps: do not log app logs to output
backupcleaner: do not remove the backup in progress
backups: make noop upload work again
dashboard: also render checklist items in apps.html
dashboard: remove mailbox import/export feature
ionos: add contract-owned eu-central-3
sftp: restore mode and owner
volumes: /mnt/volumes is reserved"

So it discusses making some things related to backups work again.

8.0.4 will not be stable for a week. So I should probably update to 8.0.4 when it is stable and then retry a backup.

[nebulon]

Well I don't think this is related to the certificates on your Cloudron, but the error indicates that during the backup the connection to the backup storage has issues and that your backup storage has invalid or rather self-signed certificates: Upload error: self-signed certificate

To be clear by saying you use Digital Ocean, does this refer to where the server is or the backup storage?

[Shaun Snapp]

Digital Ocean is where the Cloudron backup backs up to.

[Shaun Snapp]

Interestingly I just received this email from Amazon AWS telling me to upgrade to 8.0.4.

"Thank you for subscribing to Cloudron.

We are writing to inform you that Cloudron UG has added a new version to Cloudron on AWS Marketplace. As an existing customer, your subscription to the product, any running instances and access to previous versions are unaffected. However, Cloudron UG does recommend you to update to the latest version, Cloudron/8.0.4 by visiting https://aws.amazon.com/marketplace/pp/prodview-aep3gt5elubci.

For additional questions or upgrade information, please contact Cloudron UG directly. Visit the seller's profile page on AWS Marketplace."

However, as probably everyone knows, it is not yet stable.

[adnanjan.bcs]

@Shaun-Snapp same here too. how it cloud be solved?

[joseph]

@Shaun-Snapp If you go to Backups -> Configure -> Click Save without making any changes, does it work? I assume you mean you are using Digital Ocean Spaces?

[Shaun Snapp]

@joseph Yes, I can save the configuration in Cloudron Backups without making any changes. Yes I am using Digital Open Spaces. Here is there response to a ticket I opened with them.

"Please note that if your Space Bucket is generally working fine then this on-going issue might not be associated with that."

[Shaun Snapp]

@adnanjan-bcs Did this problem start after you updated to 8.0.3?

[joseph]

@Shaun-Snapp can you check if DNS is working fine on your server? Does host www.cloudron.io work on the server?

[Shaun Snapp]

@joseph I have not had any problems with my DNS. All of my sites are working fine. Except for the inability to make new backups, everything is working as it normally does.

[joseph]

@Shaun-Snapp thanks. I am short of ideas, can you contact us at support@cloudron.io and we can investigate further .

[Shaun Snapp]

I just updated to 8.0.4 and then tried a backup and I receive the same error of a self signed certificate.

[joseph]

Setting the nameservers to 8.8.8.8 and 1.1.1.1 resolved the issue.

[Shaun Snapp]

It did turn out to be a DNC issue which Joseph at Clourdon support fixed and then created a backup.