How to fix UpdraftPlus backup not working
If your WordPress backups are failing, the problem is usually not UpdraftPlus itself but a server limit, remote storage issue, or a conflict in the backup workflow.
This guide shows how to fix UpdraftPlus backup not working by tracing the failure from configuration to server-side causes.
UpdraftPlus is one of the most widely used WordPress backup plugins, but even a reliable backup plugin can fail when file permissions, PHP memory, cron jobs, or cloud authorization break down.
Check the backup log first
The backup log is the fastest way to identify where the process stopped.
In UpdraftPlus, each backup attempt records status messages that can point to timeout errors, upload failures, zip creation problems, or database access issues.
- Open WordPress Dashboard > Settings > UpdraftPlus Backups.
- Go to the Existing Backups tab and inspect the log for the latest run.
- Look for phrases such as failed to upload, cannot write to, timed out, or authentication failed.
If the log shows the exact step where the backup stops, you can focus on that part of the workflow instead of troubleshooting blindly.
Confirm remote storage is connected correctly
Many backup failures happen because the destination service is no longer authenticated.
Google Drive, Dropbox, Amazon S3, Microsoft OneDrive, and other remote storage providers often expire tokens, require reauthorization, or block access after security changes.
What to verify
- The remote storage account is still connected in UpdraftPlus settings.
- The correct folder or bucket exists and has write permissions.
- The third-party service has not blocked access due to account security changes or API limits.
- There is enough free storage space in the destination account.
If the backup completes locally but fails during upload, the storage integration is the likely cause.
Disconnecting and reconnecting the remote destination often restores normal backups.
Test file and folder permissions
WordPress backups need permission to create archives, write temporary files, and store backup chunks.
If the web server cannot write to the backup directory, UpdraftPlus may stop during file packaging or upload preparation.
Common permission-related causes include incorrect ownership after a site migration, restrictive chmod settings, or hosting platforms that lock down the wp-content directory.
- Check that wp-content/updraft exists and is writable.
- Verify that the server user owns the WordPress files.
- Avoid overly permissive settings that create security risks, such as world-writable directories.
If you recently moved hosts or restored the site manually, permissions and ownership are especially important.
Increase PHP memory and execution limits
Backups can fail when PHP runs out of memory or hits the maximum execution time before the archive finishes.
Large media libraries, plugin folders, and database tables increase the load on the server.
UpdraftPlus may stop with timeout behavior even when the site appears normal in the browser.
This is common on shared hosting, lower-tier VPS plans, and servers with conservative PHP settings.
Settings that often matter
- memory_limit
- max_execution_time
- max_input_time
- upload_max_filesize
- post_max_size
If your hosting provider allows it, raise these limits through php.ini, .user.ini, or the hosting control panel.
If not, ask support to increase them for your WordPress site.
Reduce backup size when large files cause failures
Backups often fail because they are simply too large for the server or storage target to process in one pass.
Large video files, cache directories, log files, and backups of backups can make the archive unstable or slow.
UpdraftPlus lets you exclude specific folders and file types.
This is useful when the site contains data that does not belong in routine backups.
Common exclusions
- Cache folders such as wp-content/cache
- Temporary or session files
- Old archive files stored inside the site
- Very large media files that are archived elsewhere
Review the backup contents carefully.
Excluding unnecessary directories can shorten backup time and reduce the chance of a timeout.
Check WordPress cron and server scheduling
UpdraftPlus often relies on WordPress cron to start or continue backup jobs.
If wp-cron is disabled, blocked by caching, or interrupted by low traffic, scheduled backups may not run reliably.
Problems with cron can also happen when a site uses a real server cron job but the schedule is misconfigured.
In those cases, backups may appear enabled but never start.
- Confirm that wp-cron.php is reachable.
- Check whether a caching plugin is preventing scheduled tasks from triggering.
- If you use a real cron job, verify that it calls WordPress at the correct interval.
For mission-critical backups, a server-side cron schedule is usually more dependable than traffic-based WordPress cron.
Look for plugin and theme conflicts
Security plugins, optimization tools, and aggressive caching solutions can interfere with file writes, remote requests, or scheduled tasks.
A theme conflict is less common, but it can still affect admin-side AJAX calls and dashboard behavior.
Typical conflict sources include:
- Security plugins that block outgoing connections
- Optimization plugins that compress or delay scripts
- Backup plugins running at the same time
- Hosting firewalls that restrict loopback requests
To isolate the issue, temporarily disable nonessential plugins and test another backup.
If the backup succeeds, reactivate plugins one by one to identify the conflict.
Verify server connectivity and firewall settings
UpdraftPlus needs outbound access to communicate with cloud services and, in some setups, to contact its own update or validation endpoints.
Firewalls, ModSecurity rules, and host-level security layers can block these requests.
Symptoms include authorization failures, connection timeouts, and uploads that never finish.
If the log suggests networking trouble, ask your host whether outbound HTTPS connections are restricted.
Also check whether your site is behind a proxy, WAF, or CDN rule that interferes with WordPress admin requests.
These systems can be helpful, but they occasionally break backup traffic if configured too aggressively.
Update UpdraftPlus, WordPress, and PHP
Compatibility issues can cause backup jobs to fail after a WordPress core update or a PHP version change.
Older versions of backup plugins may not handle new PHP behavior, library changes, or stricter server settings.
- Update UpdraftPlus to the latest stable version.
- Update WordPress core.
- Check whether your PHP version is supported by both WordPress and UpdraftPlus.
If the problem started immediately after an update, review recent changelogs and test whether a rollback is necessary in a staging environment before changing production settings.
Use a manual test backup to isolate the failure
A manual backup gives you a controlled way to reproduce the problem.
Scheduled backups can fail for different reasons than on-demand backups, so testing manually helps separate scheduling issues from archive or upload problems.
When you run a manual backup, watch for whether the process fails during database export, file archive creation, local storage, or remote upload.
That detail is often enough to pinpoint the root cause.
Interpret the result
- Fails immediately: likely a configuration, permission, or connection issue
- Fails during archiving: likely memory, timeout, or file-size pressure
- Fails during upload: likely remote storage or firewall problem
Restore a clean backup configuration
If UpdraftPlus settings have changed multiple times, export or note the current configuration, then reset only the backup destination and scheduling options that are most likely to be broken.
Reconfiguring from a clean state can remove stale tokens, invalid paths, or corrupted job metadata.
After resetting, test with a small manual backup before returning to full-site backups.
This step is especially helpful after migrations, domain changes, or hosting transitions.
When to contact your host or switch backup strategy
If you have checked logs, permissions, storage, PHP limits, cron, and conflicts, the remaining issue may be at the hosting layer.
Some providers place strict limits on long-running PHP tasks, background processes, outbound connections, or temporary file creation.
Ask your host to review:
- PHP memory and execution limits
- Disk space and inode usage
- Firewall rules and outbound SSL access
- Error logs for backup-related failures
If the hosting environment cannot support reliable full-site backups, consider splitting backups into smaller sets, moving the site to stronger hosting, or using a second backup method for redundancy.
Quick checklist for fixing UpdraftPlus backup failures
- Read the backup log for the exact failure point
- Reconnect cloud storage accounts
- Verify directory permissions and ownership
- Increase PHP memory and execution limits
- Exclude unnecessary large files and cache folders
- Check cron scheduling and loopback access
- Disable conflicting plugins temporarily
- Update WordPress, PHP, and UpdraftPlus
- Run a manual backup to reproduce the problem