A failed plugin update usually comes from a stalled update process, a bad download, file permission trouble, low server storage, or a compatibility problem. The safest first action is to avoid retrying blindly: check whether the site is stuck in maintenance mode, then recover access before updating the plugin again.
Quick checks before changing anything
Open the site in a private browser window and check wp-admin separately. If visitors see a maintenance message but wp-admin still works, WordPress may not have cleared the temporary maintenance state after the update failed.
In wp-admin, go to Dashboard > Updates or Plugins > Installed Plugins and look for the plugin that failed. WordPress handles plugin updates from the dashboard, and its own update documentation recommends keeping WordPress, themes, and plugins current while taking care around update failures and backups: WordPress Updates.
Before replacing files or changing settings, make a fresh backup from your hosting panel if one is available. At minimum, download a copy of the affected plugin folder before deleting or overwriting it.
Safest fix order
1. Clear a stuck maintenance mode
If the front end says the site is briefly unavailable for scheduled maintenance and the message does not clear after a few minutes, connect through your hosting file manager or SFTP.
In the WordPress root folder, look for a file named:
.maintenanceDelete only that .maintenance file. Do not delete wp-config.php, wp-content, or plugin folders while doing this.
Reload the site and wp-admin. If the dashboard returns, try the plugin update again from Plugins > Installed Plugins. If it fails again, stop retrying and move to the next checks.
2. Check storage and hosting limits
A plugin update needs room to download, unpack, and replace files. In your hosting panel, check disk usage first. If storage is near the limit, remove old backups, staging copies, cache files, or unused archives through the hosting tools before retrying.
If the failed update mentions a timeout, unavailable download, or connection error, wait a few minutes and retry once. Repeated download failures can come from the host blocking outbound requests, a temporary WordPress.org/plugin vendor issue, or a commercial plugin license/download problem.
For paid plugins, check the plugin’s own license or account screen before assuming WordPress is broken. Many premium plugin updates fail when the license has expired, the site URL changed, or the vendor download endpoint is blocked.
3. Reinstall the plugin from wp-admin when the site still works
If wp-admin loads and the plugin is not critical to keeping the site online, use the normal dashboard path.
Go to Plugins > Installed Plugins, deactivate the plugin, then update it. If WordPress offers only “Update failed” with no recovery, download a fresh copy of the plugin from the official plugin source, then use Plugins > Add New > Upload Plugin.
When WordPress says the plugin already exists, choose the replacement option only if you have a backup and the plugin package came from the correct source. This replaces plugin files; it should not normally delete plugin settings stored in the database, but poorly built plugins can behave differently.
4. Replace the plugin folder with SFTP if wp-admin is broken
Use this when the failed update caused a fatal error, blank screen, or locked dashboard.
Connect with SFTP or your host’s file manager and open:
wp-content/plugins/Find the affected plugin folder. Rename it by adding -disabled to the end, for example:
plugin-name-disabledThis deactivates the plugin without deleting it. Reload wp-admin. If the dashboard opens, install a fresh copy of the plugin from Plugins > Add New or upload the vendor’s current ZIP.
After confirming the replacement works, remove the old renamed folder. Keep it until you have verified that the site’s key pages, checkout, forms, or editor still work.
5. Fix file ownership or permissions through the host
If updates fail across multiple plugins, or WordPress asks for FTP credentials when it normally should not, the issue is often file ownership or permissions on the server.
Use your hosting panel’s file permission repair tool if it has one. If not, contact the host and ask them to verify that the web server user can write to wp-content, wp-content/plugins, and the temporary upgrade directories without making files world-writable.
Avoid setting plugin folders to 777. That can create a security risk and usually hides the real ownership problem instead of fixing it.
Optional SSH method with WP-CLI
If you have SSH access and WP-CLI is already available, you can list plugins with available updates:
wp plugin list --update=availableTo update one plugin, use its plugin slug:
wp plugin update plugin-slugWP-CLI documents the available options for plugin updates, including updating one plugin, all plugins, or excluding specific plugins: wp plugin update.
Use WP-CLI after you have a backup and know which plugin failed. It is useful for SSH recovery, but it should not be the first path for site owners who can still use wp-admin safely.
How to confirm it worked
Check these in order:
- The public site no longer shows a maintenance message.
- wp-admin loads without a fatal error.
- Plugins > Installed Plugins shows the plugin active and updated.
- The feature powered by that plugin still works, such as forms, checkout, SEO fields, membership access, caching, or page builder content.
- The update notice no longer appears under Dashboard > Updates.
If the plugin controls payments, login, forms, security, caching, or backups, test the exact workflow it affects before deleting rollback files.
Rollback and escalation
If the new plugin version breaks the site, deactivate it from wp-admin. If wp-admin is unavailable, rename the plugin folder through SFTP again.
Restore the previous plugin version only from a trusted backup or the plugin vendor’s official source. Do not download old plugin ZIP files from random mirrors.
Contact your host when updates fail for several plugins, the site cannot write to wp-content, disk usage looks wrong, or deleting .maintenance does not restore the site. Contact the plugin vendor when only one commercial plugin fails, the error mentions a license or download URL, or the plugin update succeeds but its features break afterward.