• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue remote backup in google drive

The issue is known as ID [PPS-13866] and [EXT-4317], but unfortunately it is completely a Google issue. If their systems deem traffic to be illegimitate, the only solution for you will be to experiment with the above mentioned

[ext-google-drive-backup]
RequestTimeout = 300
ConnectionTimeout = 15
MaxResumeAttempts = 15
MaxResumeFailures = 15
PauseBetweenAttempts = 40

entries. It is recommended to play with the Resume values and the pause between attempts. Do longer pauses and increase the resume attempts. There is nothing else that can be done from the user side, because the control over what Google allows and what it does not is alone with Google. If this does not work, you should consider switching the storage provider.
 
@feronimo1 Plesk is not the cause, hence it cannot provide a solution. Plesk cannot unblock something for you that is blocked on Google's side.
İt's just working 17gb, 25gb and 40gb site but not working on 190gb website.

Unable to create the remote backup: Transport error: Extension transport: ext://google-drive-backup/subscription/13/: Google Drive returns an error. Please try repeating the operation later. The error details: <!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 502 (Server Error)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>502.</b> <ins>That’s an error.</ins> <p>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds. <ins>That’s all we know.</ins>
 
The HTML that is logged is a page generated by Google. I suggest referring the case to them. Plesk has no influence on what Google servers do.
 
Back
Top