A WordPress automatic update failed notice in your dashboard is one of those problems that site owners often dismiss as a temporary glitch — assuming the next scheduled attempt will succeed — and then forget about until something more serious happens because the site has been running outdated software for weeks. I take WordPress automatic update failed notifications seriously, and you should too, because the automatic update system is your first line of defence against security vulnerabilities. When it breaks, you are not just dealing with a minor inconvenience; you are dealing with a site that cannot patch itself. This guide covers every reason the WordPress automatic update failed message appears and every fix that gets automatic updates working reliably again. For the bigger picture, our WordPress Errors Complete Guide pulls everything together.
Before anything else: A WordPress automatic update failed message in the dashboard does not always mean an update was missed. Sometimes it means the update succeeded but the success notification failed to write. Visit Dashboard → Updates and check whether the version numbers are current before beginning any troubleshooting.
Why WordPress Automatic Updates Fail
The WordPress automatic update process involves several sequential steps: checking for available updates, downloading the update package from WordPress.org servers, extracting and replacing the relevant files, running any database upgrade routines, and then writing the success status. A WordPress automatic update failed error can occur at any of these steps, which is why the causes range from server-side network issues to file system permission problems to timeout limits.
The most common single cause of the WordPress automatic update failed error on shared hosting is a timeout. WordPress minor and major updates download and extract a significant amount of data, and on servers with a low PHP execution time limit or a slow connection to WordPress.org, the process exceeds the timeout before completing. The server stops the process mid-update, and WordPress reports a WordPress automatic update failed status while the site is left in a partially updated state — sometimes with the maintenance mode file still in place.
File system permission problems are the second most common cause. The WordPress update process needs to create, overwrite, and delete files in the WordPress root and in wp-admin and wp-includes. If the web server user does not have write access to these directories, the WordPress automatic update failed error appears because WordPress cannot complete the file replacement portion of the update. This is particularly common after a hosting migration where the file ownership transferred incorrectly. The third cause is a server firewall or network configuration that blocks outbound connections to api.wordpress.org and downloads.wordpress.org — the endpoints WordPress uses to check for and download updates.
Complete the Update Manually When WordPress Automatic Update Failed
When the WordPress automatic update failed notice appears, the fastest path back to a current, secure installation is completing the update manually. This bypasses whatever caused the automatic process to fail and gets the site updated immediately rather than waiting for the automated system to be fixed first.
- Visit wordpress.org/download and download the latest version of WordPress as a zip file
- Extract the zip on your local computer — you will see a folder named “wordpress” containing all WordPress files
- Connect to your server via FTP or SFTP
- Upload the
wp-adminandwp-includesfolders from the extracted download to your server’s WordPress root, choosing to overwrite existing files when prompted — this replaces core files with the updated versions - Do not overwrite
wp-content,wp-config.php, or.htaccess— these contain your site’s data and configuration - After the upload completes, visit yoursite.com/wp-admin/upgrade.php — this runs any database upgrade routines the new version requires
- Confirm the current WordPress version in Dashboard → About to verify the manual update succeeded where the WordPress automatic update failed
Manual updates are a reliable alternative to the automatic process and should always be used when automatic updates consistently fail. The process takes about ten minutes and achieves the same result as a successful automatic update. Returning to fix the automatic update system is still worth doing, but getting the site onto the current version first is the priority whenever the WordPress automatic update failed notice appears.
Clear the Maintenance Mode File That Blocks WordPress Automatic Updates
When a WordPress automatic update failed partway through execution, WordPress may have left a .maintenance file in the WordPress root directory. This file signals that an update is in progress — WordPress creates it at the start of every update and removes it on successful completion. When the WordPress automatic update failed message appears after a timeout or an interrupted update, this file is often left behind, and its presence prevents any subsequent automatic update attempt from starting. Visitors to the site see a “Briefly unavailable for scheduled maintenance” message instead of the live site.
Removing this file is typically one of the first things to check after any WordPress automatic update failed event. Connect via FTP or your hosting file manager, navigate to the WordPress root directory, and look for a file named .maintenance. Your FTP client must be set to show hidden files to see it — in FileZilla, go to Server → Force showing hidden files. If the file is present, delete it. The site immediately returns to normal, and the next scheduled automatic update attempt can proceed without the previous failed state blocking it.
After removing .maintenance, check whether the partially attempted update actually completed despite the WordPress automatic update failed message. The automatic update process sometimes writes files successfully but fails to update the version number in the database, producing the failure notice despite a functionally updated site. Running the manual database upgrade at yoursite.com/wp-admin/upgrade.php and then checking the version in Dashboard → About confirms the actual state of the installation.
Fix the File Permissions Causing WordPress Automatic Update Failed
File system permissions that prevent the web server from writing to the WordPress core directories are a structural cause of the WordPress automatic update failed error that will recur on every update attempt until the permissions are corrected. Unlike a one-time timeout or a network blip, a permissions problem consistently blocks every WordPress automatic update failed attempt until addressed directly.
The WordPress automatic updater needs write access to the WordPress root directory (public_html/ or wherever WordPress is installed), wp-admin/, and wp-includes/. If the web server runs as a different user than the file owner — which happens on some hosting configurations — the updater cannot write to these directories even if the permissions look correct from the owner’s perspective. On shared hosting that uses suPHP or PHP-FPM (where PHP runs as the site owner rather than the web server user), this is rarely an issue. On configurations where the web server user is separate, it is common.
To diagnose whether permissions are causing the WordPress automatic update failed error, check the WordPress debug log or the server error log for entries timestamped around the time of the failed update. A permissions-related failure will show PHP errors referencing could not write file or permission denied at paths within the WordPress directory. If confirmed, contact your hosting provider and ask them to verify that the PHP process has write access to the WordPress installation directory. On VPS or dedicated servers with SSH access, you can verify ownership with ls -la and correct it with chown -R username:group /path/to/wordpress as the appropriate system user.
Enable WordPress Automatic Updates in wp-config.php
Some WordPress installations have automatic updates disabled entirely in wp-config.php — either by a developer who set it up that way, by a plugin that manages updates on a schedule, or by a migration that brought over a configuration from a development environment where automatic updates were intentionally turned off. If this is the case, the WordPress automatic update failed message (or the absence of any automatic update activity at all) is explained by the update system being disabled, not broken.
Check wp-config.php for these lines that control automatic updates:
define( 'WP_AUTO_UPDATE_CORE', false ); // Disables all automatic core updates define( 'AUTOMATIC_UPDATER_DISABLED', true ); // Disables the entire automatic updater define( 'WP_AUTO_UPDATE_CORE', 'minor' ); // Enables only minor (security) updates define( 'WP_AUTO_UPDATE_CORE', true ); // Enables all automatic core updates
If AUTOMATIC_UPDATER_DISABLED is set to true, that alone explains every WordPress automatic update failed or missing update event. Setting it to false or removing the line re-enables the updater. For the most useful configuration — automatic minor updates for security patches, manual control over major version updates — set WP_AUTO_UPDATE_CORE to 'minor'. This ensures security releases are applied automatically without waiting for manual intervention, which is the most common cause of WordPress sites being compromised through outdated software after a WordPress automatic update failed event that was never investigated.
When the Hosting Environment Is the Root Cause
Some WordPress automatic update failed situations are not fixable within WordPress itself because the problem is in the server infrastructure. A firewall that blocks outbound connections to wordpress.org, a server that sits behind a proxy that modifies or drops HTTPS responses, or a PHP configuration that prevents file system write operations from the web server process are all hosting-level issues that require the host’s involvement.
The test for a network-level cause of the WordPress automatic update failed error is straightforward: from the WordPress admin, go to Tools → Site Health → Info → Server. Scroll down to the WordPress.org connectivity check. A failed connectivity check confirms the server cannot reach WordPress.org update servers, which is the direct cause of the WordPress automatic update failed error in this scenario. Present this information to your hosting provider’s support team — a specific connectivity test result is far more actionable for them than a general “updates aren’t working” report. Most providers can resolve outbound connection restrictions quickly once the specific domain and port are identified.
Our guide on how to safely update WordPress covers the full manual update process with additional detail on database upgrade steps and rollback procedures for when an update produces unexpected problems. Our guide on how to backup a WordPress site properly is essential reading before any update process — a backup taken immediately before a major update is your safety net if the WordPress automatic update failed error occurs mid-process and leaves the site in an unstable state. The WordPress developer documentation on wp-config.php covers the full set of automatic update configuration constants and their accepted values. You might also run into How to Fix WordPress Upload Failed to Write File to Disk Error.
