Support

Akeeba Backup for Joomla!

#42310 Can't Backup to Amazon Web Services of BackBlze

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
4.4.11
PHP version
8.2.29
Akeeba Backup version
10.0.6

Latest post by nicholas on Saturday, 04 October 2025 03:32 CDT

timpennington

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 10MiB, please upload it on your server and post a link to it.

Background: I normally back up my site to BackBlaze and everything seemed to be going well until this Spring when i noticed the automatic backups stopped in January 2025; I contact you all and it seemed the issue was with my hoist, Hostgator and this was your response: 

"Looking at your log, it seems that you're uploading 20Mb in about 1 second. Honestly that seems a bit too much, if you include that archives are not in your BackBlaze account, I suspect that there's some cache on the server for outgoing connections. So we think we uploaded a file, but in reality we're getting a cached OK response from your server, not the cloud provider. ou should get in touch with your hosting and report the problem, please be prepared because this is something not very easy to convey to first level support. Otherwise, you can try to use another post-processing service, maybe those are in the list of domains that shouldn't be cached. Davide Tampellini, Developer and Support Staff"

I needed some expert help with this (and other issues with my site) and I brought in a consultant to help me; we contacted Hostgator and they "reset" the server but it still do not take a Backblaze backup. Otherwise, Hostgator knew nothing about how to fix this issue.

I then recently switched to Amazon Web Services (AWS) to try to set up automatic backups. When we set it up and did a backup, it went to AWS no problem. When we set up the automatic backups, it did not take. It did not back up as scheduled. 

Our most recent backup (not automatic) we initiated to AWS we received the following message after it said "Backup Successful" : 

Failed to process file /home/tpennington/public_html/administrator/components/com_akeebabackup/backup/site-finishingandcoating.com-20250926-132005edt-max6ayspvlheqGB_.j01

Error received from the post-processing engine:

Akeeba\S3\Connector::putObject(): [500] RequestTimeout:Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. Debug info: SimpleXMLElement Object ( [Code] => RequestTimeout [Message] => Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. [Requestld] => 7A9PYA0VJJE6GBBG [Hostld] => G7GOP+e769xsBG5aNPef/42ZTiuX/08uv5cGdAk+garMbOVy5jyERUtJxoz9GLEiFaz8NDsPQ9M=)|

Post-processing interrupted - no more files will be transferred

Can you help us decipher this error code above (also attached) and also tell us what we can do to work with HostGator to get these automatic overnight backups resolved.

 

Thank you very much.

nicholas
Akeeba Staff
Manager

I have a very important question here. In your issue title you typed "Amazon Web Services of BackBlaze". Such a thing cannot exist because Amazon and BackBlaze are two different companies. The way I parse this turn of phrase is that you are trying to use the BackBlaze S3-compatible API.

In your issue content, however, it looks like you are trying to use Amazon S3 proper as offered by Amazon Web Services (a completely different company to BackBlaze), not the BackBlaze S3-compatible API.

I really need to know if you meant to type "of" or "or" in the title as it would completely change the context of the error message and my reply to you.

Can you please clarify?

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!

timpennington

My apoloigies for the confusion.

 

I had been backing up to BackBlaze. Then ran into the problem of it not backing up automatically.

 

I then switched to try to back up to AWS and set the parameters up to backup to AWS (abandoning BackBlaze because I thought it wouldn't work). It backed up manually to AWS, but since then has not been able to back up to AWS automatically.

 

In summary, I abandoned trying to back up to BackBlaze.

 

I hope that helps to clarify.

 

Thanks

nicholas
Akeeba Staff
Manager

Yes, that helps (me) a lot. Unfortunately, this means that your host's firewall does not allow you to access external services over HTTPS at all.

Do tell them that the message you get ("Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed.") comes from Amazon S3. It's Amazon S3 telling you that it cannot receive any data from you.

Even though the original HTTP handshake went through and the headers were sent, your host's firewall has blocked the content body of the PUT request. Amazon S3 is waiting… and waiting… and waiting… until it says, in so many words, "sorry, mate, you are not sending me anything, go away". Fair enough.

Looking at your previous ticket, uploading to BackBlaze B2 was actually suffering from the same issue. The difference is that B2 doesn't send any descriptive error message, or even a different status code back to let us know this kind of issue has happened. It just closes the connection and sends a success message. It's a quirk of B2's architecture which makes it devilishly difficult for us to diagnose issues, since both this and the more common issue Davide described look the same from the point of view of your web server.

So, what's next? Go shout at your host, and tell them they are blocking PUT requests. The initial HTTP handshake works, but they block the message body from being sent. This is a problem of their making, therefore their problem to solve.

If they can't figure it out, my advice is to move to a different host. I will give you a clue on that. Ask ChatGPT, or whichever AI assistant you use, to tell you which group owns your current host, which other hosts that group owns, and what is the general reputation of those hosts in web developer circles.

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!

timpennington

Thank you!

 

I will shout at HostGator, and might look for another host.

 

Much appreciated.

 

tp

nicholas
Akeeba Staff
Manager

You're welcome!

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!

timpennington

I wanted to update with a solution.

 

In actuality, this was my own error on the HostGator server. In the "Backup Configuration" setting on my server, there is a place to add your BackBlaze settings in "Additional Destinations" that match your bucket info for Akeeba backups.

 

I found this setting and saw that my BackBlaze settings were incorrect.

 

I set up a new bucket with BackBlaze, and added the settings on Hostgator and now it has backed upo fine for the past 3 days.

 

Thanks for you help; obviously this was my error, and I just forgot this setting on my server. I hope it might help others if they have the same problem.

nicholas
Akeeba Staff
Manager

Thank you for the update!

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!