An UpdraftPlus backup restore or migration usually fails because the site cannot write backup files, remote storage is disconnected or full, a security/server rule interrupts the restore request, or another plugin exhausts PHP memory. The safest first action is to stop retrying the restore, make sure you still have a separate hosting backup or full UpdraftPlus backup set, then check the UpdraftPlus log for the first real error.
Quick Checks Before Changing Anything
Open Settings → UpdraftPlus Backups and check whether the backup set has all needed parts: database, plugins, themes, uploads, and other files. Do not start a restore if one of those parts is missing unless you intentionally want a partial restore.
If the failure happened during migration, confirm that the destination site has enough disk space for both the compressed backup files and the extracted files. A restore needs temporary working room, not just the final site size.
Check the remote storage account next. Google Drive, Dropbox, S3-compatible storage, or another provider can block new uploads when storage is full or authorization has expired. UpdraftPlus documents failed backup causes such as remote storage problems, large backup files, host limits, and scheduler issues in its own failed backups troubleshooting guide.
If WordPress shows a critical error or recovery mode message, use the recovery email link if you have it. WordPress explains recovery mode in its fatal error recovery documentation. Once inside wp-admin, deactivate the plugin named in the error first, not every plugin at once.
Read The UpdraftPlus Log First
In UpdraftPlus, open the failed backup or restore entry and view its log. Look for the first error, not the last line. Later lines often only report that the job stopped.
Use this decision path:
- Backup directory is not writable: fix file permissions or ask the host to make
wp-content/updraftwritable by the web server user. - Remote storage failed or authentication expired: reconnect the storage account, then run a small manual backup.
- Disk full or quota exceeded: remove old local backup archives only after confirming you have remote or hosting copies.
- Timeout, killed process, or memory exhausted: reduce backup size, exclude very large directories, or ask the host about PHP memory and process limits.
- HTML detected, forbidden, 403, 406, or security response: ask the host whether ModSecurity, WAF, or another security layer is blocking UpdraftPlus restore requests.
- Critical error in another plugin or theme: isolate that plugin/theme before retrying the restore.
When the first logged failure is a PHP memory exhaustion or critical error from another plugin, treat that as a site stability problem before treating it as a bad UpdraftPlus backup. Disable the named plugin or raise the host limit, confirm wp-admin loads normally, then retry only the failed UpdraftPlus action.
WordPress has official guidance for enabling debug logging in wp-config.php when the admin screen does not show enough detail: Debugging in WordPress. Turn logging back off after troubleshooting on a public site.
Safest Fix Order
1. Confirm You Have A Rollback
Before changing plugin settings or restoring files, download the existing UpdraftPlus backup set to your computer if possible. Also check your hosting panel for a server-side backup. Host backups are especially important when the restore failure left the site half-changed.
If a recent host backup is available, make that your first-choice restore path after a failed or partial UpdraftPlus restore. It usually restores the whole account state more cleanly than retrying the same interrupted WordPress-level restore.
Do not delete old UpdraftPlus archives until you know which one is the last good backup.
2. Update UpdraftPlus, Then Retry A Small Backup
If wp-admin is working, update UpdraftPlus from Plugins → Installed Plugins. WordPress’ plugin screen is the normal place to update, deactivate, or remove plugins, as covered in the official managing plugins documentation.
After updating, run a small manual backup with only the database selected. If that works, run another backup for files. This separates database problems from file, disk, or remote-storage problems.
3. Reconnect Remote Storage
If the backup log mentions upload failure, expired access, missing permissions, or full remote storage, go to the UpdraftPlus Settings tab and reconnect the storage provider.
Then run a manual database-only backup and confirm it appears in the remote account. If it only appears locally, the problem is still remote storage, not WordPress restore logic.
4. Reduce Backup Size
Large uploads folders, cache folders, staging copies, video files, and old backup archives can make UpdraftPlus hit host limits. Exclude directories that do not need to be in a WordPress restore, especially cache and backup folders created by other tools.
Keep uploads if the site needs media restored. Excluding uploads can make the restore “succeed” while leaving broken images.
5. Check Host Restrictions
Some hosts restrict backup plugins, limit local retention, or block long-running restore requests. If your host has its own backup system or bans certain backup behavior, use the host backup for the immediate restore and ask support what UpdraftPlus settings are allowed.
A good host support request includes:
- The UpdraftPlus log excerpt around the first error
- The time the restore failed
- Whether the failure was backup, restore, or migration
- Any HTTP code shown in the log
- Whether the backup files are stored locally or remotely
If The Site Is In Recovery Mode
Use the WordPress recovery mode email if available, then deactivate the plugin or theme named in the error. If wp-admin is unavailable, use SFTP or your host file manager and rename the suspected plugin folder under wp-content/plugins/.
For example, rename:
wp-content/plugins/problem-pluginto:
wp-content/plugins/problem-plugin.disabledReload wp-admin. If the site opens, leave that plugin disabled and retry only the UpdraftPlus action that failed.
Do not rename the whole plugins folder unless you cannot identify the failing plugin. That is a broader disruption and can break payment, forms, caching, and security features at the same time.
Optional SSH Method
If you have SSH and WP-CLI access, you can list plugin status before isolating conflicts:
wp plugin listTo deactivate a specific plugin:
wp plugin deactivate plugin-slugWP-CLI documents plugin management in the official wp plugin command reference. Use this only when SSH is already part of your normal site maintenance; wp-admin or the hosting file manager is safer for many site owners.
How To Confirm It Worked
For a backup failure, run a manual database backup first, then a file backup. Confirm the new backup appears under existing backups and, if remote storage is enabled, in the remote account.
For a restore failure, check the restored area directly:
- Visit the homepage and a few important inner pages.
- Open wp-admin and save permalinks from Settings → Permalinks if URLs return 404.
- Check media-heavy pages for missing images.
- Test forms, checkout, login, or membership flows if the site depends on them.
- Review the UpdraftPlus log for a completed restore message and no new fatal error.
For a migration, also check the site URL, uploads, permalinks, and any hard-coded links. A migration can restore files correctly while still leaving old-domain references in content or plugin settings.
Rollback And Escalation
If a restore leaves the site broken, use the hosting backup first when available. It is usually faster and less risky than repeatedly applying the same failed restore through WordPress. If there is no usable host backup, restore from a complete UpdraftPlus backup set only after confirming all required components are present and the first logged failure has been addressed.
Contact UpdraftPlus support when the log points to a plugin restore error, missing backup component, remote fetch problem, or UpdraftPlus-specific message. Contact the host when the log shows memory exhaustion, disk quota, blocked HTTP requests, ModSecurity/WAF behavior, process kills, or backup-plugin restrictions.
Stop retrying after two failed restores with the same error. Repeated attempts can overwrite files, consume disk space, and make the clean rollback point harder to identify.