Akeeba Backup for Joomla!

#30729 – Google drive

Posted in ‘Akeeba Backup for Joomla!’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 28 December 2018 03:47 CST
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:
I am just looking for clarity on the json error problem and google drive in this post #30463 – Invalid JSON data received you state
"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."

So my question is should the server be set to HTTP/1.0 or HTTP/1.1? I have tried both but I still can't send backups to drive
Custom Fields
Joomla! version (in x.y.z format) 3.x
PHP version (in x.y.z format) 7.2
Akeeba Backup version (x.y.z format) all

Friday, 28 December 2018 11:35 CST
I have already applied a workaround to that issue in Akeeba Backup 6.3.1 (and 6.3.2, the latter being the latest version available at this time). All you have to do is update Akeeba Backup to 6.3.2.

If you have an older PHP or Joomla! version I'm afraid you're out of luck. Your host cannot apply any workaround. They'd have to roll back to an earlier cURL version with known security issues. Common sense and security best practices say that this will not happen.

Nicholas K. Dionysopoulos

Lead Developer and Director

Greek: native

English: excellent

French: basic

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

Sunday, 27 January 2019 17:17 CST
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.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Cookies Notification - Action required

This website uses cookies to provide user authentication and improve your user experience. Please indicate whether you consent to our site placing these cookies on your device. You can change your preference later, from the controls which will be made available to you at the bottom of every page of our site.