Issue Plesk Google Drive Backup Error

[Ahmet CAVUSOGLU]

Server operating system version

Ubuntu 24 LTS

Plesk version and microupdate number

18.0.75

Hi,

I'm experiencing a problem. One of my servers, located on different IP addresses with similar settings, is unable to back up to Google Drive and cannot list the backups. However, there appears to be no problem with the Google Account connection.

I also tried the settings described in this article on panel.ini, hoping it might fix the problem, but it persists. (Backup via Plesk Google Drive fails: your computer or network may be sending automated queries - Support Cases from Plesk Knowledge Base)

The error message on the screen is as follows:

ERROR:      ()      Unable to create the remote backup: Transport error: Extension transport: ext://google-drive-backup/server/: cURL error 6: Could not resolve host: www.googleapis.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://www.googleapis.com/drive/v3/files?q=%27root%27%20in%20parents%20and%20trashed%3Dfalse&spaces=drive&fields=nextPageToken%2C%20files%28id%2C%20name%2C%20size%2C%20mimeType%2C%20md5Checksum%29&supportsTeamDrives=true

WARNING:      ()      Unable to delete the incomplete remote backup. Error: Failed to exec pmm-ras: Exit code: 129: Transport error: Extension transport: ext://google-drive-backup/server: cURL error 6: Could not resolve host: www.googleapis.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for

Thank you in advance for your support.

 

[Kaspar]

The cURL error 6: Could not resolve host error indicates that there is an issue resolving the www.googleapis.com host on your server. This is likely because of an issue with the resolve.conf configuration. Try to compare network configurations between your servers to why one server behaves differently from your other server.

 

[Ahmet CAVUSOGLU]

Hi @Kaspar

It seems you've identified the problem. I haven't compared the resolution.conf file, but I didn't see a difference. The problem is related to disk filling up. Our server is using 58% of its available disk capacity, but it's still insufficient. Even though we set up a multi-volume backup with a volume size of 2048MB, the disk fills up, causing the backup process to stop.

Why might it not have worked despite setting it up as a multi-volume backup? Do you have any guesses?