Support

Akeeba Backup for WordPress

#23009 Invalid AJAX data: (HTML containing script tags)

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.

Environment Information

WordPress version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by dlb on Thursday, 23 July 2015 11:09 CDT

ktjscm
I get this error when post processing to S3

Invalid AJAX data: (HTML containing script tags)

ktjscm

ktjscm
Log File

dlb
It looks like you are using the S3 (Legacy) post processing type. That method requires that the archive be broken down into small parts, the "chunk" function did not work well in that version of the Amazon API. The newer version works much better.

The first thing to try is to switch to the newer S3 method and see if the upload works with that. If it does, great, we're done. If not, we need to look at the settings some more to beat it into submission.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


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


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

ktjscm
Yes, Ive done that. I moved from Legacy to the new version and get the same error.

-ms

dlb
Please double check your user and password for S3. We're not getting an authentication error, but it is failing immediately. Are there any characters besides letters and numbers in your bucket name?

Can you give me an updated log please?


Dale L. Brackin
Support Specialist


us.gifEnglish: native


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


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

ktjscm
Here is the most recent log file. Credentials are correct, I use it on multiple sites but please also note on some of my other sites I run backup using legacy mode because v4 never works. The only reason I implemented v4 is because there is a note saying legacy mode will be removed so I figured we have to make this work.

-ms

ktjscm
Here is the attachment. It errored on me during the last message

dlb
In your S3 setup, the field "Disable multipart uploads" should not be checked.

When Amazon retires the old API, then we will have to retire the legacy code as well. They are calling the shots on that, not us.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


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


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

ktjscm
I need a Thumbs Up emoticon - THAT WORKED!!! Thank you.

-ms

dlb
I saw the problem, but misinterpreted the message. :-(

What that does is break your archive up into small chunks and uploads the individual chunks, then reassembles them into the archive again. The chunking is invisible to you, unlike the split archive function. The problem was that it was trying to upload your whole archive in one part and it was too big. When I saw "Legacy" in the log, I thought S3 Legacy mode, not unchunked.

I"m glad it is working now!


Dale L. Brackin
Support Specialist


us.gifEnglish: native


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


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

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!