Support

Akeeba Backup for Joomla!

#42239 AJAX Loading Error HTTP Status: 500 Internal status: error XHR ReadyState: 4 Raw server response: null

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
5.3.3
PHP version
8.4.11
Akeeba Backup version
10.0.5

Latest post by crimleit on Monday, 01 September 2025 03:29 CDT

crimleit

Hi Nicholas

I repeatedly have backup errors on some of my websites. During the backup I can see 2 or 3 times this message:

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 5 seconds
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/>null

Each time the backup resumes after a few seconds. At the end, there is an error message and the backup status shows a red icon indicating "Failed".

I hope you will find the reason for this.

Thank you and kind regards
Chris 

crimleit

I just tried a backup that excludes the folder «images». This was successful, so the reason for the error must be somewhere in the «images» folder. For the time being, I configured the regular backup so that the «images» folder will not be backuped. 

nicholas
Akeeba Staff
Manager

The actual problem is that you are trying to upload 2GiB part files over WebDAV. Please remember that I have documented why this is a problem:

Before you begin, you should know the limitations. As most remote storage technologies, WebDAV does not allow appending to files, so the archive has to be transferred in a single step. PHP has a time limit restriction we can't overlook. The time required to upload a file to WebDAV equals the size of the file divided by the available bandwidth. We want to time to upload a file to be less than PHP's time limit restriction so as to avoid timing out. Since the available bandwidth is finite and constant, the only thing we can reduce in order to avoid timeouts is the file size. To this end, you have to produce split archives, by setting the part size for archive splitting in ZIP's or JPA's engine configuration pane. The suggested values are between 10Mb and 20Mb. Most servers have a bandwidth cap of 20Mbits, which equals to roughly 2Mb/sec (1 byte is 8 bits, plus there's some traffic overhead, lost packets, etc). With a time limit of 10 seconds, we can upload at most 2 Mb/sec * 10 sec = 20Mb without timing out. If you get timeouts during post-processing lower the part size.

If you read this documentation paragraph you will see that it explains what happens, why it happens, and what to do (lower the part size for archive splitting under the archiver engine options).

As to why it only happens when you include you images directory, I think that by now the answer to that question should be easy to deduce: because that's where the vast majority of your data lies in. When you take a backup excluding the images directory you have a much, much smaller backup which uploads over WebDAV without your server timing out. That's good. This is a known safe backup archive size for your configuration. Change your part size for archive splitting to the size of your backup minus the images directory and take a new full 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!

crimleit

Thank you very much for this convincing explanation. It has helped me a lot. I previously used Microsoft Onedrive as a post-processing engine and did not have this problem. I was not aware that WebDAV has different file size requirements in this regard.

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!