WordPress Stuck in "Briefly Unavailable for Scheduled Maintenance"? Fix It in 30 Seconds

You clicked "Update" on a few plugins, something interrupted the process, and now every page on your site says "Briefly unavailable for scheduled maintenance. Check back in a minute." And it's been a lot longer than a minute. The fix takes about 30 seconds. Making sure nothing was half-updated takes a little longer.

Why WordPress gets stuck

When WordPress updates core, plugins or themes, it creates a file called .maintenance in the site's root folder. While that file exists, every visitor gets the maintenance message. When the update finishes, WordPress deletes the file.

If the update is interrupted (you closed the tab, the server hit a timeout or memory limit, or the connection dropped), the file never gets deleted. WordPress does ignore a .maintenance file once it's more than 10 minutes old, but some setups and caches keep serving the message regardless, which is why some sites stay stuck.

The fix: delete the .maintenance file

Via SFTP or your host's file manager

1. Connect to the site and open the root folder, the one containing wp-config.php and the wp-content folder.
2. Find .maintenance. Files starting with a dot are hidden by default: in cPanel's File Manager click Settings → Show Hidden Files; in FileZilla use Server → Force showing hidden files.
3. Delete it.
4. Reload your site. If you still see the message, clear your page cache and any Cloudflare cache.

Via WP-CLI

wp maintenance-mode status
wp maintenance-mode deactivate

Or over plain SSH:

cd /path/to/wordpress
rm .maintenance

Now check for half-finished updates

The update that was interrupted may have left a plugin or core partly replaced. That can cause errors right away, or only later when someone uses the broken feature.

Plugins and themes

1. Go to Dashboard → Updates. Any plugin that still shows an available update didn't finish. Update it again, one at a time.
2. If a plugin has disappeared from the Plugins list, its folder was removed before the new version was copied in. Reinstall it from Plugins → Add New. Its settings live in the database, so they'll still be there.
3. Look in wp-content/upgrade/ and wp-content/upgrade-temp-backup/. Leftover folders there are normal after a failed update and can be deleted once everything works.

WordPress core

If a core update was interrupted, verify the core files:

wp core verify-checksums

If anything is reported as missing or modified, reinstall core without touching your content:

wp core download --skip-content --force

No SSH? Go to Dashboard → Updates and click Re-install version X.X.

"Another update is currently in progress"

If WordPress refuses to start a new update with this message, a lock from the failed update is still set. It expires on its own after about 15 minutes. To clear it immediately:

wp option delete core_updater.lock

Or in phpMyAdmin, delete the core_updater.lock row from the wp_options table.

The site shows an error after deleting .maintenance

If the maintenance message is replaced by "There has been a critical error on this website" or a white screen, the interrupted update left a plugin broken. Follow my guide to fixing the WordPress critical error. The debug log will name the exact plugin.

How to stop it from happening again

• Update one plugin at a time, especially large ones like WooCommerce or page builders. Bulk updates on cheap hosting are the most common cause of timeouts.
• Don't close the tab until WordPress says the update is complete.
• Raise PHP limits if your host allows it: max_execution_time of at least 120 seconds and a memory_limit of 256M make timeouts much less likely.
• Test updates on staging first for any site that makes money. A broken update on staging costs nothing.