Support

Akeeba Backup for Joomla!

#18022 Falure uploading to S3

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Monday, 04 November 2013 03:10 CST

user6956
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes the S3 pages in the manual
Joomla! version: 2.5.14
PHP version: 5.4.9-4ubuntu2.3
MySQL version: 5.4.9-4ubuntu2.3
Host: Digital Ocean VPS
Akeeba Backup version: 3.8.2

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue: Just trying to upload the backup file to S3. I looked at the log and it doesn't seem to have any errors thrown, so here I am!

nicholas
Akeeba Staff
Manager
I think you missed an important bit of our documentation :) https://www.akeebabackup.com/documentation/akeeba-backup-documentation/step-by-step-guides.html#how-to-cloud-backup-basic-config

As you can read, you might need to set a small part size for split archives (around 10Mb should work). Moreover, you may want to consult this page for more troubleshooting information: https://www.akeebabackup.com/documentation/troubleshooter/abamazons3.html

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!

user6956
I had initially tried part sizes as small as 20. Now I went all the way down to 1, and still get the same error. I turned on logging over on the S3 side of things, it seems to login properly. I would post the log files, but it looks like it has some info I don't feel comfortable posting in public. I have followed the other recommendations and I still get the error.

nicholas
Akeeba Staff
Manager
Have you tried turning off the multipart uploading as I've written in the troubleshooter page?

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!

user6956
Yep, multipart uploaded was unchecked. At 1mb. Still fails

nicholas
Akeeba Staff
Manager
I see that you have a single part archive with a size of 345220928 bytes (329.23 Mb). It's not a split backup. I think you are changing the wrong parameter, so please let me give you the very detailed instructions. I apologise in advance if they look way too detailed and novice-oriented; I want to make sure that there is no miscommunication of the configuration option you need to modify.

Please go to the back-end of your site and click on Components, Akeeba Backup. From the drop down menu at the top of the page make sure that "Default backup profile" (#1) is selected. If not, please select it from the list and wait for the page to reload.

Now click on Configuration. Find the row labeled "Archiver engine". Next to the drop-down there is a button labeled "Configure...". Click on it. A pane opens right below. Find the row labeled "Part size for split archives". From the drop-down box select the value "10.00". Now click the "Save & Close" button at the very top (toolbar area) of the page. Then please retry your backup.

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!

user6956
I can show you my backup that has 329 parts to it, I can assure you that I have it currently set at 1mb. I didn't upload the latest log, Here it is

nicholas
Akeeba Staff
Manager
Please contact your host. There seems to be a server-level firewall which prevents the connection to Amazon S3. Unfortunately this is beyond our control and you'll have to seek assistance from your host.

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!

user6956
I spoke with support at Digital Ocean and they said they don't block anything. Also I don't think they are either because i have logging on in S3 and I do see it attempting to handshake. So something else has to be the issue?

nicholas
Akeeba Staff
Manager
I am wondering why the transfer doesn't go through. We are simply using PHP's cURL library to handle the HTTP(S) transfers to Amazon S3. According to what you are saying your host can send packets to S3 but not receive packets from S3. Frankly, I've never seen that before, but I have a hunch. Go to the Akeeba Backup Configuration page, click the Configure button next to the Post-processing Engine row and uncheck the "Use SSL" checkbox in case your server has an older, slightly broken version of libcurl or libssl. I can't think of any other reason for this one-way packet transfer.

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!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!