Support

Akeeba Backup for Joomla!

#25227 Ajax Errors

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 Wednesday, 29 June 2016 17:20 CDT

Nick_Q
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:

Looking to restore a site built on one of my test sites to its new domain, I am getting Ajax loading errors when attempting to run kickstart pro 4.2...

Not had this before and having attempted this using my Amazon S3 backup depository, and a local version with FTP (binary upload) I get the same result... Restarting the load gives me the same result.

Can you assist - What am I missing?

tampe125
Akeeba Staff
Hello Nick,

what's the actual error?
Can you please upload here a screenshot of the error?
I suspect that your hosting is blocking requests that contain too much data.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Nick_Q
Hi Davide,

Here is a screen shot of the error...

tampe125
Akeeba Staff
That's what I was thinking.
The remote host is blocking your request. You should contact them and ask if they can remove the block.
Otherwise the only option is to locally extract the whole site and then upload everything using FTP.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Nick_Q
HI Davide,

Many thanks for your response...

Thanks for your support on this. Its odd as I have not had this with HEART before and have 50 + sites with them most using your (akeeba!) backup off to my Amazon S3 account.

Restoration and/or site transfer have not previously been an issue. The only difference here is that I am replacing an old HTML site with a new Joomla installation from another test bed domain also hosted by HEART.

Just for the record I have now written to them asking for an investigation and confirming that:

-----------------------------------------------------------------------------------
OK so what I have done today is to attempt this again in two ways both of which fail at the extraction on the backup .jpa file.

Firstly I took an up to date backup manually and this is automatically stored on my S3 account which would be the normal process.
This version of Kickstart allows for importing a backup .jpa file from Amazon which I duly did and on attempting the initial extraction the restoration failed giving the error that I forwarded previously.
I then downloaded the .jpa file from Amazon and uploaded to the public_html folder using binary FTP and attempted to complete the extraction using the now resident .jpa file --> same result.
It is as if the server refuses to accept this amount of data being loaded in this way... odd?!

NB. I will now go and delete the fragments of files that have been extracted so that you have the same "clean Sheet that I started with. I will leave the latest .jpa file present which I can confirm was certified good by akeeba backup when taken.

Appreciate any light you can throw on this as its holding up a site migration which is beginning to be embarrassing - its my site!

You will also see and index.html file and an image file which is currently acting as a place-holder which I will also leave present.

Please let me know if you need any further information.
--------------------------------

I will keep you in the loop as this may assist others with tripping over this issue.

tampe125
Akeeba Staff
Ok, please keep me updated

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Nick_Q
HI Davide,

Quick update for you... still struggling with this...

changes employed to date include taking the backup with akeeba version 5.1.0.b1 and adding a local PHP.ini file with:

max_execution_time = 5000
max_input_time = 5000
max_input_vars = 5000
memory_limit = 128M
upload_max_filesize = 50M
post_max_size = 200M


Still getting that AJAX error as originally reported with the extraction bombing out after 5 - 10 seconds...
All backups taken reported as good at the time of completion.

tampe125
Akeeba Staff
Sadly that's nothing to do with our software, it's your server blocking the requests.
You can try to slow down it a little. In Kickstart main page, there should be a setting regarding the maximum and minimum execution time.
Please try those setting:
Minimum execution time: 7 seconds
Maximum execution time: 3 seconds

Yes, minimum is greater than maximum, that's not a typo. The restoration will be very slow, but that should do the trick.
If it still fails, your last resort is to manually extract everything locally and then upload it using FTP.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

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 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!