Troubleshooting
Why Is Your WordPress Update Failing? Causes and Fixes

Short answer
WordPress updates fail when the server cannot download, unpack or write the new files. Common causes are wrong file permissions, low disk space or memory, a leftover update lock or maintenance file, a blocked connection to WordPress servers, a security rule, or an expired premium licence.
Key takeaways
- Read the exact error message, since it points to the step that failed.
- Wrong permissions or ownership cause Could not create directory errors.
- A leftover lock or maintenance file blocks later updates until removed.
- Download failed often means the server cannot reach WordPress servers.
- Premium plugins need a valid licence to receive updates.
- A manual update over FTP or WP-CLI bypasses most automatic update problems.
Why is your WordPress update failing?
WordPress updates usually fail because of wrong file permissions, low disk space, a timeout or memory limit, a stuck update lock, a blocked connection to WordPress.org, or a plugin or security rule that interrupts the process.
When you click Update, WordPress downloads a zip file, unpacks it into a temporary folder, then copies files into place. A problem at any of those steps stops the update.
The error message tells you which step failed. Typical messages include:
- Update failed: Download failed.
- Could not create directory.
- Another update is currently in progress.
- Installation failed or The package could not be installed.
- Briefly unavailable for scheduled maintenance that never goes away.
- Updating failed. The response is not a valid JSON response in the editor.
Read the exact wording before changing anything. Then use the table below to jump to the right fix.
Which update error points to which cause?
Each update error points to a specific step in the process, so matching the message to its cause saves time.
| Error message | Likely cause | Fix |
|---|---|---|
| Download failed | Server cannot reach WordPress.org, SSL or DNS issue | Check outbound connections, ask host |
| Could not create directory | File permissions or ownership | Correct permissions on wp-content |
| Another update is currently in progress | Leftover update lock | Delete core_updater.lock option or wait 15 minutes |
| Stuck in maintenance mode | Update interrupted | Delete the .maintenance file |
| Not a valid JSON response | REST API blocked | Check permalinks, firewall, security plugin |
| Package could not be installed | Corrupt download, disk full | Free space, retry or update manually |
| Connection information form appears | WordPress cannot write files directly | Fix ownership or set FS_METHOD |
| Timeout or blank screen | Low memory or execution time | Raise PHP limits |
The sections below explain each one in more detail.
Are file permissions stopping the update?
Often, yes: if the web server cannot write to the WordPress folders, updates fail with Could not create directory or WordPress asks for FTP details instead of updating.
WordPress needs write access to wp-content, wp-content/upgrade, wp-content/plugins and wp-content/themes. For core updates, it also needs to write to the main install folders.
Typical safe permissions are 755 for folders and 644 for files. Ownership matters too. Files should belong to the user the web server runs as.
The official file permissions guide explains the details. Our guide to setting correct file permissions in WordPress walks through it with a file manager.
If you see the Could not create directory error specifically, follow our step-by-step guide to fixing installation failed could not create directory.
On shared hosting, ask support to reset ownership. It is a common request and usually takes minutes.
Is your server out of disk space or memory?
A full disk stops WordPress unpacking the update, and a low memory limit or short execution time can kill the process halfway through.
Disk space. Check usage in your hosting panel. Old backups stored inside the site folder are a common space hog. Move them off the server or delete old ones.
Memory. Large plugins and core updates need more memory than a basic page load. Check your limit under Tools > Site Health > Info > Server. Our guide to increasing the PHP memory limit explains the options.
Execution time. If the server stops scripts after 30 seconds, a slow download plus unpack can time out. Ask your host to raise max_execution_time or run the update at a quieter time.
The PHP manual on runtime configuration lists these settings and what they control.
Is a stuck lock or maintenance file blocking updates?
Yes, if a previous update was interrupted: WordPress leaves a lock in the database or a .maintenance file in the root, which blocks or breaks later updates.
Another update is currently in progress. WordPress sets a lock while updating core. If the update crashed, the lock stays. It expires on its own after about 15 minutes.
You can also delete the core_updater.lock row from the options table. Our guide to fixing another update is currently in progress shows both methods.
Stuck in maintenance mode. During updates, WordPress creates a .maintenance file. If the update dies, visitors keep seeing the Briefly unavailable message. Delete that file from the site root over FTP. See our guide to fixing a site stuck in maintenance mode.
After clearing either one, run the update again. Then check that the plugin or core version actually changed.
Can your server not reach WordPress.org?
If you see Download failed or updates never appear at all, your server may be unable to connect to WordPress.org because of a firewall, DNS problem, or outdated SSL certificates.
WordPress fetches updates from api.wordpress.org and downloads.wordpress.org over HTTPS. If outbound connections are blocked, updates cannot download.
Signs of a connection problem:
- Site Health reports that WordPress cannot reach WordPress.org.
- The error mentions cURL, SSL or a timeout. WordPress uses the cURL library for most outgoing requests, so cURL error numbers are worth searching.
- Updates work on another site on a different host.
What to try:
- Open Tools > Site Health and read the Status tab.
- Check whether
WP_HTTP_BLOCK_EXTERNALis set in your config file. The wp-config documentation explains it. - Ask your host to confirm outbound HTTPS is allowed and CA certificates are current.
The free Health Check & Troubleshooting plugin adds extra tests if Site Health is not enough.
Is a plugin, firewall or premium licence blocking the update?
Security plugins, server firewalls and expired licences for premium plugins are common reasons a single plugin update fails while others work.
Security plugins and firewalls. Rules that block file changes or outgoing requests can stop updates. Temporarily pause the firewall, update, then turn it back on. If Wordfence is involved, our guide to fixing Wordfence blocking admin may help.
Premium plugins. Paid plugins update from the vendor's server, not WordPress.org. An expired or missing licence key usually means no updates. Check the licence screen in the plugin's settings.
Plugin conflicts. A broken plugin can crash the update process itself. If updates fail across the board, try with other plugins deactivated. Our guide to fixing a plugin conflict explains how.
Version requirements. A new plugin version may require a newer PHP or WordPress version. WordPress blocks the update and says so. Update PHP or core first.
How do you update WordPress manually when automatic updates fail?
Download the new version from WordPress.org, upload the files over FTP, replacing everything except wp-content and your config file, then visit the admin to finish any database update.
Manual updates bypass most permission and connection problems. The official Updating WordPress documentation covers the full process.
For core:
- Back up files and database.
- Download the latest zip from WordPress.org and unzip it.
- Delete the old
wp-adminandwp-includesfolders on the server. - Upload the new
wp-adminandwp-includesfolders. - Upload the loose files in the root, overwriting old ones. Keep your config file.
- Visit the admin. If asked, click Update WordPress Database.
For a plugin:
- Download the new zip from WordPress.org or the vendor.
- Go to Plugins > Add New > Upload Plugin and upload it.
- Choose Replace current with uploaded when prompted.
You can also update from the command line with WP-CLI. The wp core update command handles core, and similar commands exist for plugins and themes.
What should you check after a failed update?
Confirm the version number changed, look for a leftover maintenance file, check the debug log, and test key pages, because a half-finished update can leave mixed old and new files.
Quick checks:
- Dashboard > Updates shows the expected version.
- No
.maintenancefile remains in the site root. - Front end and admin load normally.
- Debug log is free of new fatal errors.
If the site broke after an update that did complete, the problem is different. See our guide to fixing a site broken after a WordPress update.
You can also roll back the WordPress update while you investigate.
How do you stop WordPress updates failing in future?
Keep permissions and ownership correct, leave enough disk space, keep PHP current, renew premium licences, and back up before each update so failures are easy to undo.
Good habits:
- Update regularly so each jump is small.
- Update one plugin at a time on important sites.
- Test big updates on staging first.
- Clean out old backups and logs from the server.
- Keep a current backup before every update.
Our guide on how to update a WordPress website covers a safe routine from start to finish.
Frequently asked questions
Why does WordPress ask for FTP details when I update?
WordPress asks for connection details when it cannot write files directly, usually because the files are owned by a different user than the web server. Ask your host to fix ownership. As a workaround, the FS_METHOD constant can be set in the config file, but fixing ownership is better.
Is it safe to delete the maintenance file?
Yes. The maintenance file only exists to show visitors a temporary message during updates. Deleting it after a failed update takes the site out of maintenance mode. Then check that the update finished, and rerun it if the version number did not change.
Why do only some plugins fail to update?
Usually because those plugins are premium and update from the vendor's server, needing an active licence. Other causes include a version requirement your site does not meet, or a firewall rule blocking that vendor's server. Check the plugin's licence screen first.
Can a failed update break my site?
It can. A half-finished update may leave a mix of old and new files, which can cause errors. Rerunning the update or replacing the files manually usually fixes it. Keeping a backup from just before the update gives you a quick way back.
How long should a WordPress update take?
Most plugin and core updates finish within a minute. If an update spins for several minutes, it has probably timed out or stalled. Refresh the page, check for a maintenance file, and look at the version number before trying again.
Sources
- Updating WordPress WordPress.org Documentation
- Changing file permissions WordPress Developer Resources
- wp core update WP-CLI Command Reference
- Runtime configuration PHP Manual
- Health Check & Troubleshooting WordPress.org Plugins
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


