Home » wp-admin » Briefly Unavailable for Scheduled Maintenance: WordPress Fix

Briefly Unavailable for Scheduled Maintenance: WordPress Fix

You clicked “Update”, the screen hung, and now every page of the site, front end and wp-admin, shows one line: Briefly unavailable for scheduled maintenance. Check back in a minute. Minutes pass and it does not go away.

This happens on any WordPress site after a core, plugin or theme update that did not finish. The fix takes less than a minute: delete one hidden file. After that you still need to check what the broken update left behind.


When WordPress starts an update it writes a file called .maintenance into the folder that holds wp-config.php. When the update ends, it deletes it. If the PHP process dies halfway (timeout, memory limit, closed tab on a slow host), the file stays and the site keeps showing the maintenance message.

Over SSH, go to the WordPress root and look for it:

cd /path/to/wordpress
ls -la .maintenance

If the file is listed, remove it:

rm .maintenance

With WP-CLI you can do the same thing without touching the file by hand:

wp maintenance-mode status
wp maintenance-mode deactivate

deactivate should end with Success: Deactivated Maintenance mode. Reload the site in a private window and it should load again.

No SSH? Open the site root in your FTP client or the hosting file manager and delete .maintenance there. The dot at the start makes it a hidden file, so if you do not see it, turn on “show hidden files” (in FileZilla: Server menu, Force showing hidden files).

💡 The file is in the WordPress root, next to wp-config.php and wp-load.php. It is not in wp-content or wp-admin.


The file itself is tiny. Core writes one line into it, the Unix time the update started:

<?php $upgrading = 1795000000; ?>

On every request, wp_is_maintenance_mode() loads that file and compares the timestamp with the current time. This is the check in core (from wp-includes/load.php):

if ( ! file_exists( ABSPATH . '.maintenance' ) || wp_installing() ) {
	return false;
}

require ABSPATH . '.maintenance';

// If the $upgrading timestamp is older than 10 minutes, consider maintenance over.
if ( ( time() - $upgrading ) >= 10 * MINUTE_IN_SECONDS ) {
	return false;
}

So a leftover file from a crashed update should stop blocking the site on its own after 10 minutes. If you still see the message after that, one of these is going on:

  • The file does not contain a fixed timestamp. Some maintenance scripts and plugins write $upgrading = time();, which is always “now”, so the 10-minute check never passes. Open the file and look.
  • Something keeps starting new updates. Auto-updates via WP-Cron or a management dashboard (MainWP, ManageWP, a host tool) retry a failing update, and each attempt writes a fresh .maintenance.
  • You are looking at a cached copy. A CDN or page cache stored the 503 page. Purge it after deleting the file.

If the file comes back after you delete it, check the scheduled update jobs with wp cron event list and pause auto-updates in your dashboard until you find which update keeps failing.


Deleting .maintenance brings the site back, but the update that created it is still half done. A plugin folder may contain a mix of old and new files, or be gone completely. I always check this right away.

Start with core. This compares every core file with the official checksums for your version:

wp core version
wp core verify-checksums

If it reports files that do not match or are missing, run the core update again (or reinstall core, see below). Then do the same for plugins from WordPress.org:

wp plugin list --fields=name,status,version,update
wp plugin verify-checksums --all

A plugin that fails the checksum check, or a plugin that has disappeared from the list, is the one that broke. Reinstall it over the top of itself:

wp plugin install plugin-slug --force

Replace plugin-slug with the folder name of the plugin. Premium plugins are not on WordPress.org, so verify-checksums cannot check them. Upload a fresh copy from the vendor instead.

See also  Backuply SQL Injection (CVE-2026-93953): Update & Check Your Site

If core itself is broken, my post on how to reinstall WordPress core using WP-CLI covers that without touching wp-content or wp-config.php. Take a backup of the files and the database before you reinstall anything.

Also look in wp-content/upgrade/. WordPress unpacks downloads there during an update, and leftovers from the crash can be deleted once the site works. If the next update attempt says “Another update is currently in progress“, that is a second lock, stored in the database, and it has its own fix.


An update does not leave .maintenance behind without a reason. If you do not fix the cause, the next update gets stuck the same way. The usual causes:

  • PHP max_execution_time is too low for a big plugin like WooCommerce or Elementor, and the process is killed in the middle of copying files.
  • PHP runs out of memory while unpacking the zip.
  • WordPress cannot write to some files because of wrong ownership, so the copy fails halfway. See WordPress asks for FTP credentials for how to check and fix the owner.
  • The disk is full, so the new files cannot be written.
  • You updated 20 plugins in one bulk action on a slow host.

Turn on debug logging before the next update so you get the real error instead of a guess:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
briefly unavailable for scheduled maintenance wp config 1 - Briefly Unavailable for Scheduled Maintenance: WordPress Fix
Where it goes in wp-config.php: above the “That’s all, stop editing!” line

Add these lines above /* That's all, stop editing! */ in wp-config.php, then read wp-content/debug.log after the update. Remove them again when you are done.

On sites I care about, I run updates from WP-CLI (wp plugin update --all) instead of the dashboard. The CLI is not bound by the web server timeout, and if something fails you see the error on screen.

In OpenPanel, the WordPress Manager has a maintenance mode switch and lets you edit maintenance.php from the panel (OpenPanel WordPress docs), and the File Manager works on the site files under /var/www/html/. In cPanel you do the same in File Manager with hidden files (dotfiles) shown in its settings, or with WP-CLI over SSH.


If you want visitors to see something nicer during a real update, WordPress supports a drop-in for this. When wp-content/maintenance.php exists, core loads it instead of the default message. Otherwise it sends a 503 with Retry-After: 600 and the “Briefly unavailable” text.

A minimal drop-in should keep the 503 status, so search engines know the outage is temporary:

<?php
http_response_code( 503 );
header( 'Retry-After: 600' );
header( 'Content-Type: text/html; charset=utf-8' );
?>
<!DOCTYPE html>
<html>
<head><title>Back soon</title></head>
<body>
<h1>We are updating the site</h1>
<p>This takes a minute or two. Please refresh shortly.</p>
</body>
</html>

The drop-in only changes what the page looks like. It does not fix a stuck .maintenance file, so the steps above still apply.

As of 2026-11-22 this logic lives in wp_is_maintenance_mode() and wp_maintenance() in core, and the official common WordPress errors page gives the same fix: delete .maintenance from the site root.

TL;DR: “Briefly unavailable for scheduled maintenance” means an update crashed and left the hidden .maintenance file in the WordPress root. Delete it (or run wp maintenance-mode deactivate), purge the cache, then run wp core verify-checksums and wp plugin verify-checksums --all to find and reinstall whatever the update left half done.

Was this post helpful?

Leave a Comment

I enjoy constructive responses and professional comments to my posts, and invite anyone to comment or link to my site.

Recommended