WordPress Stuck in Maintenance Mode? The One-File Fix (2026)

The fix: delete one file — .maintenance — in your WordPress root. It's hidden, so enable "show hidden files" first. Takes 2 minutes via FTP or file manager. The follow-up nobody mentions: the update that created it was interrupted mid-way — re-run it one item at a time or your site stays half-updated.

Why It Happens

When WordPress updates core, a theme, or a plugin, it drops a .maintenance file in the site root — same folder as wp-config.php. That file displays the "Briefly unavailable" message. When the update completes, WordPress deletes it. When the update is interrupted — closed tab, timeout, memory crash, plugin conflict — the file stays and the site stays locked. Note: WordPress auto-ignores .maintenance files older than ~10 minutes; if it's still showing past that, the update itself failed, not just the cleanup.

The Fix: Delete .maintenance

Via FTP (FileZilla etc.):

1. Connect with your FTP credentials
2. Enable hidden files — in FileZilla: Server → Force showing hidden files
3. Navigate to site root (where wp-config.php lives, usually public_html)
4. Find .maintenance → delete it
5. Reload the site — it returns immediately

Via hosting File Manager:

1. Open cPanel → File Manager (or your host's equivalent)
2. Click Settings → check "Show Hidden Files (dotfiles)"
3. Navigate to the site root, delete .maintenance

Via SSH/WP-CLI: rm /path/to/site/.maintenance or wp maintenance-mode deactivate.

The Step Everyone Skips: Finish the Update

Deleting .maintenance unlocks the site, but the interrupted update left a half-applied plugin/theme/core. After unlocking:

1. Log into wp-admin → Dashboard → Updates
2. See which update was interrupted
3. Re-run it one item at a time, keep the browser open

Skipping this leaves a partially-updated install — which surfaces later as the critical error or white screen.

If It Keeps Reappearing

Delete .maintenance, it comes back = the update is failing repeatedly. Culprits: PHP max_execution_time too low, insufficient memory, or a corrupted plugin that can't update. Check the server error log, increase limits in wp-config.php:

define( 'WP_MEMORY_LIMIT', '256M' );

Or ask your host to raise max_execution_time — shared hosts with tight timeouts cause most repeat cases.

Prevention

• Update one item at a time — "Update All" is how timeouts happen
• Don't close the tab mid-update — wait for completion
• Adequate PHP limits — low memory/execution time kills updates
• Hosting that doesn't choke updates — tight shared timeouts are the root cause; Bluehost managed WP handles updates on WP Cloud with proper limits

Related: critical error fix, maintenance guide, 500 internal server error.