Akeeba Backup for Joomla!

#31104 Restoration Fails

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 on Monday, 15 April 2019 17:17 CDT

Friday, 15 March 2019 16:23 CDT

warchop

Backups are running fine, but I'm unable to restore from a backup, when I do, I receive the below issue. I don't have a download log for this, and I really don't even know where to start. I've been searching and googling for 6 hours, and nothing seems to work. I really have no idea where this error is coming from.

Description of my issue:

The extraction has failed
Extraction of the backup archive has failed.
The last error message was:

AJAX Loading Error
HTTP Status: 503 ()
Internal status: error
XHR ReadyState: 4
Raw server response:
(HTML containing script tags)

Saturday, 16 March 2019 17:15 CDT

nicholas

Your server returned an HTTP error code 503 Service Unavailable. This means that you have ran out of free space, ran out of bandwidth or your host imposes limits on the number of requests per second you can execute on your site.

In the first two cases there's nothing I can do to help you. You'd need to buy more space or bandwidth from your host.

In the latter case I can try to do something to help you. Before clicking the Start button in Kickstart scroll all the way down and set "Minimum execution time" to 5 and "Maximum execution time" to 1. Yes, the max is less than the min. This slows down the extraction 5 times which should overcome this kind of requests per second limitation of 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!

Monday, 15 April 2019 17:17 CDT

System Task

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

Support