Support

I see you received the public mailing of B2 last week :) However, you missed a few important details in it.

BackBlaze B2 added an optional S3 compatibility API in B2 that runs in parallel with the B2 API but does not replace the B2 API. The B2 API continues to function properly. This was communicated to us developers a month in advance, when the S3 compatibility API went live. We did test it but we see no reason to replace our existing B2 API implementation with the S3 compatibility API.

Something else is happening with your backup but without the backup log file I can't tell you what. I do have a suspicion – there was a wrong implementation note in the B2 API about when an upload retry (with a request for a new upload URL) should occur. This is something that we fixed last week but we don't have a public release with that change yet.

Is it possible to ZIP and attach your log file so I can verify this is the case with your backup? Don't worry, attachments are private even in public tickets i.e. only you and our support staff will be able to see them.

Thank you in advance!

It looks like a more mundane issue than I expected. B2 reports that your key is invalid. You have revoked it, mistyped it or it's a key for a different bucket. Try creating a new key and put it in Akeeba Backup's configuration.

Please note that before replying to you I ran two test backups which upload to B2. One with a key I had created last year and one with a new key. The backup uploads to B2 just fine. This means that both Akeeba Backup and the B2 API are working properly and the issue lies with the key you are using or the permissions on your bucket.

You're welcome! Have a great day :)