I'll happily renew it to download the latest version, but if the product's going to keep doing this then I'm not sure I want to pay for an update.Recently, I’ve migrated my personal backup from Backblaze Backup to B2 (an online S3-style file storage, also by Backblaze). I can't see anything obvious in the release notes I can find, but it's very possible I've missed something. I *can* get backup's to work if I edit Cloudberry Backup's network settings and tell it to ignore SSL certificates, but obviously this isn't ideal because I'd like it to be verifying the backup destination with SSL.ĭoes anyone happen to know if this is a known issue, and has it been fixed in a more recent version? I hadn't realised until now that my licence expired in August. I've experimentally tried a couple of full system restarts, just in case there's a service somewhere that needed to refresh its view of the cert file, but that hasn't worked either.
With some experimentation, I think it's appending the new certificate to that file every time I click the Trust Certificate button, but for whichever reason the rest of the app doesn't seem to recognise it as trusted. Furthermore, if I browse to my /opt/local/Online Backup/00000000-0000-0000-0000-000000000000/config/certs directory and view the contents of the trustedCerts.pem file, I can see multiple copies of the same cert. If I open Cloudberry Backup's network settings, it tells me that the new certificate which expires a year from now is trusted. Even if I attempt to create a *new* backup storage configuration with a new app ID from Backblaze, Cloudberry displays the same behaviour. It displays repeatedly every time I click the Trust Certificate button. I checked the certificate and clicked the Trust Certificate button, but a few seconds later the same dialog displays again.
When I went to edit the backup storage settings, the Cloudberry app (with a pop-up dialog) gave me an option to trust the new certificate, which expires almost a year from now. The Backblaze B2 cert had expired, which would happen every year. Specifically, a week ago my scheduled backups started reporting errors, which turned out to be from an invalid certificate.
I'm using Cloudberry Backup Personal Edition 3.1.4.20 for Linux, running on Debian, but I've been running into problems with the new upstream Backblaze B2 certificate not being trusted after the old one expired, even after I tell Cloudberry to trust it.
0 kommentar(er)
