Akeeba Backup for Joomla!

Wednesday, 14 November 2018 13:47 CST

dviolante

Description of my issue:

Hello, im having the same issue as the user from ticket #30463 – Invalid JSON data received...

Im getting the 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> error message.

In your answer you said that the user must have to contact hosting support to fix the issue.

My question is, what exactly do i have to ask to my hosting support that they have to fix?

Could you please tell me what exact words / technicalities i have to ask for.

Thanks

Thursday, 15 November 2018 00:20 CST

nicholas

Before you contact your host, I have another idea. Have you tried reauthenticating to Google Drive? If you have and you can still reproduce the issue the problem is that for whatever reason the server is stripping or corrupting the HTTP Authentication header from HTTP PUT requests sent to a remote server (Google Drive API server) using PHP's cURL module. So what the host needs to do is check a. if their libcurl is somehow broken after the last PHP update and b. if they have a firewall or proxy which strips out HTTP headers from HTTP PUT requests sent to a remote server using PHP's cURL module.

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!

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!

Sunday, 18 November 2018 12:38 CST

dviolante

Hello Nicholas, thanks for the update.

I have installed package v.rev8FF0D814 in my site, ran akeeba backup process and it finished successfully without issues, the file is uploaded to google drive.

Please tell me what to do now. Do i keep this package v.rev8FF0D814 installed?

Thanks

Monday, 19 November 2018 01:13 CST

nicholas

Yes, please keep the developer release installed until we release Akeeba Backup for Joomla! 6.3.1 and Akeeba Backup for WordPress 3.3.1.

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!

Wednesday, 19 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