What this problem is
Updating a plugin fails, stalls, or returns an error such as extraction failed, destination folder exists, or update failed.
Why it happens
- File permissions prevent writing to
wp-content/plugins - Disk space/inode limits
- WAF or security plugin blocks the update request
- Plugin folder ownership mismatch after migration
Prerequisites
- Hosting panel access
- FTP/File Manager access (recommended)
Diagnosis
- Check disk space and inode usage.
- Confirm folder permissions for
wp-content/plugins. - Review error logs for blocked requests or unzip failures.
Detailed steps
Step 1) Try updating one plugin at a time
Bulk updates can time out. Update individually.
Step 2) Temporarily disable caching/security layers
Disable caching plugin and WAF rules if you can, then retry.
Step 3) Fix permissions
Ensure wp-content/plugins is writable by the web server user.
Step 4) Use a manual plugin update (if needed)
Upload the new plugin version via FTP by replacing the plugin folder (covered in a dedicated article for manual updates).
Expected results
- Plugin updates complete successfully
- Site remains functional and no partial plugin folders remain
What to do if it fails
- Check the exact error message and match it to permissions vs disk vs WAF
- Ask hosting support to correct ownership or disable a blocking rule temporarily
Best practices
- Back up before updating plugins
- Keep plugins updated but avoid updating many at once on production
- Use staging for major plugin updates