WordPress .maintenance File Stuck Fix

Delete the .maintenance File (Safely)

This is the most common immediate fix. Connect to your site via FTP/SFTP (e.g., FileZilla) or your hosting provider's cPanel File Manager. Navigate to your WordPress root directory (often public_html/, www/, or your domain's folder). Locate the .maintenance file and delete it. Ensure hidden files are visible in your file manager settings.

# Via SSH, from your WordPress root directory:
rm .maintenance

✓ Time estimate: 1-2 minutes. Low risk.

Clear All Caching Layers

If deleting the .maintenance file didn't work, aggressive caching is likely serving an old page. Clear every caching layer you have: plugin caches (e.g., WP Super Cache, W3 Total Cache, LiteSpeed Cache), server-side caches (via your hosting panel), and CDN caches (e.g., Cloudflare, Sucuri). If you can't access your WordPress admin, you may need to clear plugin caches via FTP by deleting cache folders in wp-content/cache/.

# Example cache folder paths to delete via FTP/SFTP:
/wp-content/cache/
/wp-content/plugins/w3-total-cache/cache/
/wp-content/litespeed/cache/

✓ Time estimate: 5-10 minutes. Moderate risk if critical cache files are deleted incorrectly.

Check and Clear Stuck Database Transients

A failed update can leave behind database transients that tell WordPress an update is still active. Access your database via phpMyAdmin (available in cPanel) or a similar SQL client. Select your WordPress database and navigate to the wp_options table (your table prefix might be different, e.g., wp_abc_options). Look for rows with option_name like _site_transient_update_core, _site_transient_theme_transient_timeout, or _site_transient_plugin_transient_timeout. Delete these specific rows.

DELETE FROM `your_prefix_options` WHERE `option_name` LIKE '%_site_transient_update_%';
DELETE FROM `your_prefix_options` WHERE `option_name` LIKE '%_site_transient_theme_transient_timeout%';
DELETE FROM `your_prefix_options` WHERE `option_name` LIKE '%_site_transient_plugin_transient_timeout%';

✓ Time estimate: 5-15 minutes. High risk if incorrect rows are deleted. Backup your database first!

Verify File and Directory Permissions

Incorrect permissions can prevent WordPress from completing file operations, including deleting the .maintenance file. Connect via FTP/SFTP. Set directories (e.g., your WordPress root, wp-admin, wp-content, wp-includes) to 755. Set files (e.g., index.php, wp-config.php, all files within wp-admin, wp-content, wp-includes) to 644. Be cautious with wp-config.php; some hosts recommend 440 or 400 for extra security.

# Via SSH, from your WordPress root directory:
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
chmod 640 wp-config.php # Or 440, 400 depending on host recommendation

✓ Time estimate: 10-20 minutes. Moderate risk if permissions are set too broadly (e.g., 777).

Increase PHP Limits and Check Error Logs

If PHP timed out during an update, increasing its limits might prevent future occurrences and help diagnose the current one. Edit your wp-config.php file (in your root directory) or php.ini (if you have access) to increase memory and execution time. Also, check your server's PHP error logs (often in cPanel or accessible via SSH) for any fatal errors that occurred around the time the site went into maintenance mode.

// Add this to wp-config.php, just above the 'That's all, stop editing!' line
define('WP_MEMORY_LIMIT', '256M');

// In php.ini (if accessible):
max_execution_time = 300
memory_limit = 256M

✓ Time estimate: 5-15 minutes. Low risk if values are reasonable; too high can impact server performance.

Isolate Plugin/Theme Conflicts

If the issue persists or the .maintenance file keeps reappearing, a faulty plugin or theme might be causing the update process to fail repeatedly. Via FTP/SFTP, rename your wp-content/plugins folder to wp-content/plugins_old. This deactivates all plugins. Check if your site recovers. If it does, rename the folder back, then reactivate plugins one by one to find the culprit. Do the same for your active theme in wp-content/themes/ by switching to a default theme like Twenty Twenty-Four.

# Via SSH, from your wp-content directory:
mv plugins plugins_old
mv themes themes_old

✓ Time estimate: 30-60 minutes. Moderate risk of breaking functionality during testing.