Everything you need to know about backing up, restoring, and migrating your WordPress site with BackupRidge.
Use this section for stuck jobs, timeout errors, and storage connectivity issues.
Configure server cron and use the BackupRidge system cron trigger URL when WP-Cron is unreliable.
A scheduled watchdog task detects backups that should have resumed but did not (for example when loopback fails or WP-Cron is disabled). It can re-queue a resumption attempt or mark the job failed so the dashboard does not stay on “Running” indefinitely. Watchdog actions are written to the per-job log under BackupRidge → Logs.
Apply noabort LiteSpeed rules for wp-cron.php and admin-ajax.php to prevent aborted resumptions.
If Connect with Google succeeds but Test connection reports Connection succeeded but file upload test failed, OAuth is working but the Drive API call failed.
Most often the Google Drive API is not enabled on the same Google Cloud project as your OAuth client. Enable it under APIs & Services → Library → Google Drive API, wait a few minutes, then test again.
Full setup steps: Cloud Storage → Google Drive.
If OAuth shows No scope requested can be granted, your Dropbox app Permissions were not enabled and Submitted before Connect. Enable files.content.write, files.content.read, files.metadata.read, and files.metadata.write, click Submit, then Connect again.
If Connect with Dropbox succeeds but Test connection reports upload failed, the token likely lacks write scopes — fix permissions, Submit, and Connect again.
Full setup steps: Cloud Storage → Dropbox.
URL may not contain a query string when adding a redirect URI — register https://yoursite.com/wp-admin/admin.php only, not admin.php?page=....
unauthorized_client: not enabled for consumers or Consumer vs /common/ — your Azure app's supported account types must match the sign-in account. Personal OneDrive apps should use Personal Microsoft accounts only with BackupRidge's default consumers endpoint.
Full setup steps: Cloud Storage → OneDrive.
If Connect with Google, Connect with Dropbox, or Connect with Microsoft shows Quick connect is not configured, your site has no hosted OAuth app for that provider. Switch to Use your own app (Client ID and secret) and follow the provider setup in Cloud Storage (Google Drive, Dropbox, or OneDrive section).
If Test connection fails at the first step, check Access Key ID, Secret Access Key, bucket name, and Region (must match the bucket's AWS region). Leave Custom endpoint empty for AWS.
If upload works but you see Upload succeeded but file listing returned no objects, the IAM user likely has s3:PutObject but not s3:ListBucket on your backup prefix — add list permission in IAM.
Full setup steps: Cloud Storage → Amazon S3.
If Test connection fails immediately, check Access Key ID, Secret Access Key, bucket name, and R2 endpoint URL. Copy the URL from R2 Overview → Account details → S3 API (not a public bucket URL). It looks like https://<account_id>.r2.cloudflarestorage.com. Use the Cloudflare R2 provider in BackupRidge, not Amazon S3.
BackupRidge sets the signing region to auto for R2 automatically (there is no Region field in the form). Do not use the Amazon S3 provider with AWS region codes.
If you see 403 or Access Denied, the API token may be read-only or scoped to a different bucket — recreate the token with Object Read & Write on your backup bucket.
Full setup steps: Cloud Storage → Cloudflare R2.
If you see Connection succeeded but file upload test failed, authorization worked but the upload step failed. Use the Bucket ID from B2 Bucket Settings (not the bucket name), and an application key with read and write access to that bucket.
Full setup steps: Cloud Storage → Backblaze B2.
If FTP is disabled in Remote Storage or you see PHP ftp extension is not installed, the WordPress PHP runtime does not have the ftp module. Enable it via your host panel, php.ini, or a custom Docker image — not only PHP CLI.
If Test connection fails after the extension is loaded, check host, port, credentials, firewall, and try toggling Passive mode or Use SSL/TLS for FTPS.
Full setup steps: Cloud Storage → FTP and FTP/SFTP PHP requirements.
If SFTP is disabled or you see PHP ssh2 extension is not installed, install the PECL ssh2 extension for the same PHP SAPI that serves WordPress.
If connect works but upload fails, the remote path is often not writable — on chrooted SFTP servers use a subdirectory such as /upload/backups/ instead of the chroot root.
Full setup steps: Cloud Storage → SFTP and FTP/SFTP PHP requirements.