Akeeba Backup for Joomla!

Tuesday, 04 September 2018 08:33 CDT

guzabi

Follow-up to ticket #30170 – B2 Backblaze backup upload fails

Closing tickets without warning on NOT resolved issues is rude, it's just like slamming a door on my face. I don't appreciate it.

Issue is NOT resolved :

1. You said :

If you have an ApplicationKeyID and ApplicationKey then in Akeeba Backup's configuration you can enter:

1. ApplicationKeyID in the "Account ID" field.

2. ApplicationKey in the "Application Key" field.

I did precisely that. It. Does. Not. Work. Period.

2. As I said in the previous ticket, telling me I didn't set permissions correctly is incorrect. I did multiple tests with various sets of permimssions, to no avail.

3. Just for your information : since August, Backblaze does indeed allow creating Application Keys in the interface. See attached screenshot.

And please, stop being rude. I'm not wasting your time.
You are wasting mine by closing tickets on unresolved issues.

Tuesday, 04 September 2018 09:46 CDT

nicholas

Apologies, the problem is with BackBlaze but not for the reasons I thought. Their API docs are technically correct but they left out a major caveat: the application Key Id is used instead of the account Id only in the authentication API, not anywhere else. Everything else requires either the account ID or the bucket ID.

They also made a footnote of a very important difference. Under the new API (which has the same version number as the old API because somehow that makes sense to them...) the authorization MAY return a bucket ID. But not always. This happens because you can create two kinds of Application Keys: with a bucket or without a bucket. Neither of these works the same as the other one and they are both different than using a master key, something not explained in their API docs. This is ultimately the problem you have.

Here are the three convoluted possibilities for using their API:

If you have a master key you need to provide the account ID, master Key and bucket name. This is already supported in Akeeba Backup.
If you have an application key which is NOT bound to a bucket you must provide the account ID, the application Key ID and the application Key. They did not explain that the account ID is required on top of the application Key ID which was the source of my confusion when I replied to you.
If you have an application key limited to a bucket you must neither provide an account ID nor a bucket name. These should be fetched from BackBlaze during the authorization stage. This is not explained well in their documentation.

These are three very different different flows with three very different interface requirements and very different integrations. I can try to implement this but it's gonna take a while.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 04 September 2018 12:23 CDT

guzabi

Thank you for your answer.

I’ll wait. This is not urgent. I’m using S3 right now and I want to switch to B2 eventually, but I can wait a bit.

Best regards.

Monday, 10 September 2018 05:40 CDT

nicholas

I have amazing and surprising news. It was a BackBlaze API bug after all. I do not have to make any changes to Akeeba Backup.

BackBlaze figured out that the inconsistent way they were handling their API was the source of confusion and frustration among developers. They are officially launching their V2 API on September 13th in BETA phase but it's already enabled. Under the new v2 API you can just use the Application Key Id instead of your Account Id and your Application Key instead of your Master Key in Akeeba Backup's configuration. All API calls now work correctly.

Remember when I told you that the problem was with the b2_list_buckets API call requiring the Account ID even when you supply an authorization token obtained through the use of an Application Key? BackBlaze finally realized that this is completely stupid because -- as I said in this ticket -- it requires three distinct and mutually exclusive code paths for doing something as simple as uploading a file. So they changed their API to accept the Application Key ID instead of the Account ID.

So, problem solved. Just enter your Application Key Id and your Application Key. You MUST, however, enter the correct Bucket Name as well, i.e. the bucket name you enter in Akeeba Backup's configuration must be the same as the bucket you have limited your Application Key to. That's all that is required. I have confirmed this just now. I had cleared up my afternoon to work on this issue and... I have nothing more to do. Oh, well, I won't complain about it!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 10 September 2018 05:41 CDT

nicholas

BTW, looking at their revision log, they only broke the API for a brief period between August 10th and sometime until late last week. If you were trying to do what you wanted to do outside those dates Akeeba Backup would have worked just fine. Too bad they don't announce these changes anywhere...

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Monday, 10 September 2018 13:39 CDT

guzabi

Hi Nicholas.

This is great news. However, there seems to still be a problem…
I did enter my ApplicationKeyId in "Account ID" and ApplicationKey in "Application Key".
I typed in the correct bucket name in "Bucket". And I swear I have been careful. I copy-pasted carefully everything.

I still get this error :

500 :: Backblaze B2 API Error bad_request: string does not start with quote

Failed to process file /home/petitpoisson/public_html/administrator/components/com_akeeba/backup/site-www.petitpoisson.be-20180910.jps

Post-processing interrupted -- no more files will be transferred

Am I doing something wrong?
How can I make this work?

Thank you for your help…

Monday, 10 September 2018 13:40 CDT

guzabi

Here is my log file for my last attempt.

Tuesday, 11 September 2018 23:58 CDT

nicholas

Your log file never made it. Can you please give it another go? If the ZIP file is over 2MB please give me a link to it.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 12 September 2018 00:32 CDT

guzabi

Second try for log file…

Wednesday, 12 September 2018 00:33 CDT

guzabi

Does not seem to work.
Here's a wetransfer link :
https://we.tl/t-GQvrH4UDFs

Thursday, 13 September 2018 03:40 CDT

nicholas

I have tried the following dev release https://www.akeebabackup.com/download/developer-releases/akeebapro/rev4881e6f5.html with the Master Key, an Application Key not limited to any bucket and an Application Key limited to a bucket (no prefix constraint, all privileges granted). It should also be able to deal with application keys with a mix of bucket and / or prefix limiting. It will also crash as gracefully as possible when inadequate permissions are granted for the operation you require (e.g. no write privileges are given and you try to upload a file).

The reason I had not tried to reply to you before is that BackBlaze had announced that their new API was going on-line today. I wanted to make sure the last issue I had seen with the way their bucket list API works was resolved on their side before bothering you.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 13 September 2018 10:15 CDT

guzabi

Hi Nicholas,
Thanks for the feedback.
Do you want me to try the dev release with my credentials for testing ?
Best regards,

Thursday, 13 September 2018 10:56 CDT

nicholas

Yes, please do try it with your own credentials. I prefer to have independent validation :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 13 September 2018 11:05 CDT

guzabi

I downloaded the dev version, installed it over the one in place.
Apparently all settings were preserved ok.

Ran a "Transfer Archive" on a previously done backup, got this :

Then I ran a complete backup, just in case. It failed and tried to resume multiple times with this error :

Backup Halted and Will Resume Automatically
The backup operation has been halted because an error was detected. However, Akeeba Backup will attempt to resume the backup. If you do not want to resume the backup please click the Cancel button below.

The backup will resume in	4 seconds	
 Cancel    Resume

For your information, the last error message was:

<strong>AJAX Loading Error</strong><br/>HTTP Status: 500 ()<br/>Internal status: error<br/>XHR ReadyState: 4<br/>Raw server response:<br/>(HTML containing script tags)

Then the backup failed and sent me to log analyzer with this Alice message :

------ BEGIN OF ALICE RAW OUTPUT -----
Timeout while backing up
There is already an issue with the backup engine saving its state. Please fix it before continuing.

Post-processing engine and archive part size
A post-processing engine is found, but no part size is set; this could lead to timeout issues

------ END OF ALICE RAW OUTPUT -----

and one warning :

Timeout while backing up
There is already an issue with the backup engine saving its state. Please fix it before continuing.

Please try setting min execution time to 1, max execution time to 10 seconds (or if the PHP timeout is less than 10 seconds, use 75% of the PHP timeout), runtime bias 75%

and an error :

Post-processing engine and archive part size
A post-processing engine is found, but no part size is set; this could lead to timeout issues

Set a part size inside backup profile configuration.

All the rest was green (success).

Friday, 14 September 2018 02:52 CDT

nicholas

Oops. I went home earlier yesterday and didn't push the last commit I made to the repository. So when I published the new dev release from home, based on the code I had already pushed on GitHub, and told you to try it out it did not include a critical change required for its correct operation.

OK, here is the correct dev release: https://www.akeebabackup.com/download/developer-releases/akeebapro/revdfadd5cd.html

Yes, it has the same designation and date but the files are updated. Please re-download, install the new file and give it a go. Let me know how it goes.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Friday, 14 September 2018 10:25 CDT

guzabi

Uploading is complete!

Success !!!
Hooray !!!
You are the best !!! :-)

Is it okay to continue using this alpha, or should I reverse to 6.2.1 and wait for next release ?

Friday, 14 September 2018 16:16 CDT

nicholas

Continue using this alpha until I release 6.3.0 (scheduled for mid to late October, barring any as yet undiscovered showstopper issue, a new Joomla! release breaking stuff etc). The alpha you have is just 6.2.1 plus the BackBlaze patch :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Sunday, 14 October 2018 17:17 CDT

System Task

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support