Support

Akeeba Backup for WordPress

#29421 – Ajax 403 error received on Backup, and when attempting to update to v3.0.1

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Wednesday, 21 March 2018 20:06 CDT
webcoast
Hi, my site is having trouble completing a backup. I don't know what percentage it gets to because it doesn't show us anymore, but it is always during the "Backing up files" phase. It is an Ajax Loading Error 403, XHR ReadyState 4.

The last time that a backup was successful was a couple of weeks ago when I was last working on the site.

The site is running Litespeed cache, it was implemented recently but I'm not sure whether it was done before the last backup was made, or after.

I copy the backup files, in 100meg chunks to AmazonS3 on completion. The backup should be around 420meg, but it is not being completed so not being stored in the backup directory locally (or on S3).

There is adequate disk space.

I re-ran the configuration wizard but it didn't make any difference, Ajax 403 is still received. I've tried about 4 times now.

PHP maximum execution time on the host is 90seconds, PHP memory limit is 256.

I also can't apply the update of Akeeba Backup to version 3.0.1 because of Ajax 403 error.

See attached screenshots and log file.
Regards
Nicola

Custom Fields

WordPress version (in x.y.z format) 4.9.4
PHP version (in x.y.z format) 7.1.15
Akeeba Backup version (x.y.z format) 3.0.1b
 
Wednesday, 21 March 2018 20:44 CDT
webcoast
Hi, I can't seem to upload the log file at all. I can't attach it, it's only 4meg and has no special characters (filename is Akeeba-Backup-Debug-Log-coronasolar.txt) . I can't include it inline, as your ticket window just freezes on submit (see attached screenshot). I can't email it to [email protected] What other options do I have?

Nicola
 
Wednesday, 21 March 2018 20:46 CDT
webcoast
This is the error received when I try to upload the error log (see attached).
 
Thursday, 22 March 2018 04:12 CDT
tampe125
Hello,

first of all, you should zip the backup file to shrink its size. Since it's a text file, the resulting compressed file would be very small.
That said, I think I know what's going on.
The 403 error means that the server reject your connection: this is usually caused by some security rules applied from your hosting to your server. They see that the same page is requested over and over from the same IP address and then they block the connection.
You can try to slow down the backup process; inside Akeeba Backup configuration page, please set the following values:

Minimum execution time: 5 seconds
Maximum execution time: 3 seconds
Runtime bias: 50%

Yes, minimum is greater than maximum, that's not a typo. In this way your backup will be slower, but it should complete.
If it's still failing, you should get in touch with your host.


Davide Tampellini

Developer and Support Staff



Italian: native

English: good



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Thursday, 22 March 2018 04:41 CDT
webcoast
Thanks Davide, that worked, and I was able to run the Akeeba update as well, without issue.
You can close this ticket.
Regards
Nicola
 
Thursday, 22 March 2018 04:44 CDT
tampe125
You're welcome!


Davide Tampellini

Developer and Support Staff



Italian: native

English: good



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!