Fixing 502 Server Errors in JetBackup & Gdrive Backups Print

  • 0

Fixing 502 Server Errors in JetBackup & Gdrive Backups

In case your cPanel accounts are not getting backed up correctly using Google Drive as the destination through JetBackup, you may face the following problem. You may receive 502 errors from Google, which would include a message stating that the connection was blocked. The error message could look like this:

<title>Error 502 (Server Error)!!1</title>
Error 502 (Server Error) The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds. We're sorry...</h1><p>... but your computer or network may be sending automated queries. To protect our users, we can't process your request right now.

Please note that if you are backing up multiple servers to Google Drive destinations, the backups MUST be staggered to prevent throttling/rate-limiting errors like these.

To resolve this issue, please provide a screenshot of the Google "App" Console along with your assigned scopes. You can find this information in the Google Cloud console under "APIs and Services > OAuth Consent Screen": You can view the Scopes by clicking "Edit App".

Additionally, please make sure that the "Google Drive API" is enabled for the "App." If the Google Drive API is not explicitly enabled, it can cause unusual problems with the backup. You can check this here: If the button shows as "Enable," click Enable and proceed through the prompts to ensure the Drive API is enabled.

You can find documentation on setting up a Google Drive destination [ Click here... ]

If you have followed all the instructions provided by JetBackup, and the problem persists, you need to go to the terminal and run the following command to download the hook for JetBackup. The hook will sleep every request for 2 minutes, which should solve the problem.

wget -O /root/
chmod +x /root/

Now add the hook at JetBackup from WHM > Plugins > JetBackup > Hooks. Click on "Create new hook" and name everything as follows:

Save the changes and then go to the "Backup Jobs" section and start the backup. To check if it is working, go to the "Logs" section. This should resolve the issue.

Was this answer helpful?

« Back

Send Message