Akeeba Backup for Joomla!

Saturday, 10 November 2018 02:01 CST

Valtari

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

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:
Hi,
Soory about my bad english, I'm french.
I've an issue with my backup and his confogurtaion ti send on Ggogle Drive.
Error message :

Erreur d'envoi de l'archive.

Invalid JSON data received: <HTML> <HEAD> <TITLE>Not Implemented</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" TEXT="#000000"> <H1>Not Implemented</H1> <H2>Error 501</H2> </BODY> </HTML>

I read a ticket which say that'is a problem of space, but it's not a problem of space on my Google Drive.
can you hel me.
Thanks in advance.
Best rregards.

Monday, 12 November 2018 01:05 CST

Valtari

UP, please !

Monday, 12 November 2018 04:57 CST

nicholas

Please note that the following reply is not arbitrary. We have worked with another user who has the same issue and have already confirmed that the problem is not on our or Google's side but with the hosting service you are using.

It would appear that you have a transparent proxy server, cache or firewall in front of your server which blocks HTTP PUT requests. The Google Drive API requires that we use PUT requests to perform a multipart upload of files over 5MB. Therefore due to no fault of ours or Google Drive's it is impossible to upload backup archive files over 5MB to Google Drive from your server.

You need to contact your host and ask them to resolve this issue. There is nothing you, us or Google can do about it -- it is a problem with the setup of your server which is controlled by your host.

In the meantime you can either use a different upload service whose API does not require using HTTP PUT (such as Dropbox) or set the Part Size for Split Archives to 5MB. The latter is not a very convenient option. It will cause your backup to be split into multiple files, each one up to 5MB. This means that a 200MB backup results in 40 backup archive files.

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, 12 November 2018 05:50 CST

Valtari

Hi Nicolas,
Thaks a lot for your coimplet reply !
I undestand.
Best regards

Sunday, 18 November 2018 11:46 CST

nicholas

Hello,

I am sending this reply to all users who have filed tickets regarding errors uploading to Google Drive since November 7th. All of you have reported that you suddenly started receiving the error

Invalid JSON data received: <HTML> \n <HEAD> \n <TITLE>Not Implemented</TITLE> \n </HEAD> \n <BODY BGCOLOR="#FFFFFF" TEXT="#000000"> \n <H1>Not Implemented</H1> \n <H2>Error 501</H2> \n </BODY> \n </HTML> \n

and uploading to Google Drive failed.

In most cases I have already told you that this is a hosting error. Some of you did try to contact your hosts but they either refused that this is an error with their infrastructure or deflected and said that the error is on our side. This is partly because my original hunch that this is a firewall or proxy in front of your server was misleading, partly because they didn't bother pursuing this issue further.

One of the affected hosts did take the time to troubleshoot this issue and found out that my second hunch (broken cURL library) was actually the culprit. It appears that a recent update to the cURL library, used by PHP to contact remote servers, has a weird bug which prevents it from correctly identifying the HTTP protocol version the remote server speaks. Instead of using HTTP/1.1 it falls back to HTTP/1.0. However, Google Drive's API servers do NOT speak HTTP/1.1 and return the HTTP 501 Not Implemented error. To make things even weirder, this bug only happens with certain PHP verbs. As I already told you, HTTP GET and POST requests work fine, PUT does not. This is the reason.

Following that lead we have created a developer's release with a workaround to this cURL bug. We are explicitly telling cURL to use HTTP/1.1 when contacting Google's servers. Since we cannot reproduce this issue on any of our development or live servers we would like to ask you to install this developer's release and use it to perform a backup that uploads to Google Drive, then tell us if it resolved the issues you were experiencing. The developer's release is identical to the already published stable plus the fix.

You can download the developer release from:

Akeeba Backup for Joomla!: https://www.akeebabackup.com/download/developer-releases/akeebapro/rev8ff0d814.html
Akeeba Backup for WordPress: https://www.akeebabackup.com/download/developer-releases/backupwp-dev/rev52043ca9.html
Akeeba Solo: https://www.akeebabackup.com/download/developer-releases/solo-standalone-dev/rev52043ca9.html

After installing the developer release you will see that an update is available. Please do not update! This will downgrade you back to the previous stable.

Thank you in advance for your co-operation.

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!

Tuesday, 18 December 2018 17:17 CST

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