Support

I updated Akeeba Backup to version 4.4.0 on one of my Joomla sites this morning, and ran Akeeba Backup afterward. The backup completed successfully, but post-processing (upload to Amazon S3) failed, whereas it has worked fine in the past.

Suspecting the update as the culprit, I logged in to another site and ran a backup before updating Akeeba Backup. That backup completed successfully and was successfully uploaded to Amazon S3. I then updated Akeeba Backup to version 4.4.0, and ran another backup immediately afterward. That backup completed but failed to upload to Amazon S3 (reference line 53648 in the attached log).

Please let me know what additional information I can provide.

Thank you,
Joey Sirmons

Joey,

This is Nicholas' reply to the first report which came in about 20 minutes ago:

Please go to Configuration, find the Post-processing engine row and click on the Configure button next to it. Make sure the "Amazon S3 Region" is set correctly to the same region your bucket is located in. Verify that the "Signature method" is set to "v4 (preferred for Amazon S3)". Click on Save & Close even if you made no changes. Try taking a new backup.



If the backup fails go to Configuration, find the Post-processing engine row and click on the Configure button next to it. Try setting the "Signature method" to "v2 (legacy mode, third party providers)" and click on Save & Close. Try taking a new backup.



If the backup still fails go to Configuration, find the Post-processing engine row and click on the Configure button next to it. Find the "Disable multipart uploads" and check the box next to it. Click on Save & Close. Try taking a new backup.



Please let me know which one of these solutions worked for you. Normally the first one should be sufficient.



If none of these worked please remember to ZIP and attach your backup log file.

Hi Nicholas,

All our S3 buckets are in region "US Standard."

Bucket names are all lowercase and include one or two hyphens, usually in the format clientname-backups (e.g., "masource-backups").

"Use SSL" is enabled in the "Upload to Amazon S3" post-processing engine for both sites.

Of the two websites I refer to above, the first is rather large, with the backup totaling 2.78Gb, broken into two parts: 2.0GiB and 801.8 MiB. The second website is much smaller, with only one backup part totaling 107MiB.

I have another website with Akeeba Backup installed running version 4.3.1. I am currently able to backup to S3 just fine (without the 4.4.0 update). I suspect the upload to S3 would fail after the update to Akeeba Backup 4.4.0, as with my second website mentioned above. I'm willing to try that and provide you any output (screen shots, log files ... whatever you need) to help troubleshoot. Let me know what steps you need me to take, and what information I can provide.

Thanks,
-- Joey

Joey,

This version has been canceled. Thank you for your bug report. Please downgrade to Akeeba Backup 4.3.

I confess I have never rolled back an update to a Joomla extension before. Is there a simple way to do that? Or is there a mechanism built in to Akeeba Backup to roll it back?

Thanks,
-- Joey

You can just download the 4.3.1 version and install it over the 4.4.0 that you have installed. That worked for my site with no problems.