Google Drive

The Google Drive provider uses OAuth. Easypanel creates the provider entry, redirects the browser to Google, and stores the resulting authorization after the browser returns.

Connect Google Drive

Open Settings → Server → Storage Providers.
Select Add Provider → Google Drive.
Enter a descriptive Name and save.
Select the intended Google account and complete authorization.
After returning to Easypanel, confirm that the provider shows as connected.
Select it in a backup configuration and perform a manual run.
Locate and verify the uploaded file in Google Drive.

The provider is not offered in backup forms until OAuth completes.

Destination paths

The destination path is relative to the Google Drive root available to the connection:

production/orders-postgres

Use a unique path for each database or volume configuration. This prevents database retention and volume synchronization from affecting unrelated files.

Check available Google storage before scheduling large or frequent backups.

Connection lifecycle

Easypanel refreshes Google Drive authorization in the background. A revoked grant, failed refresh, removed account, or policy change can still make later backup actions fail.

The provider's actions menu includes:

Edit to change its Easypanel name;
Disconnect to revoke authorization but retain the provider entry;
Connect to authorize a disconnected provider again;
Remove to revoke authorization and delete the provider configuration.

Disconnected providers are excluded from backup and restore selectors.

Disconnecting or removing Google Drive does not delete previously uploaded files. Backup configurations that still reference the provider will stop working until they are changed or the provider is reconnected.

Troubleshooting

Authorization does not complete

Start again from the provider's Connect action.
Use the intended Google account.
Make sure the browser can return to the same reachable Easypanel address that initiated OAuth.
Check whether a Google Workspace administrator blocks the authorization.

A working provider starts failing

Reconnect it to replace the stored authorization.
Confirm that the Google account remains active and has available storage.
Review the backup action log and exact destination path.
Confirm that the account can still read and modify the uploaded files.

A backup cannot be found

Search the connected account for the generated backup filename and inspect the configured destination path. Confirm that OAuth was completed with the account you are currently viewing.

See Storage Providers for shared path, permission, and deletion guidance.