Lorixen.
EN

WordPress Stuck in Maintenance Mode After an Update

Short answer: WordPress creates a hidden file called .maintenance in the site's root folder at the start of every core, plugin or theme update and deletes it at the end. If the update is interrupted, the file stays behind and every visitor sees "Briefly unavailable for scheduled maintenance. Check back in a minute." Open your host's file manager or connect by SFTP, show hidden files, delete .maintenance from the folder that holds wp-config.php, and reload the site. Then find out which update stopped halfway and run it again, one item at a time.

Why the message does not go away

During an update, WordPress downloads a package, unpacks it and swaps the new files in. While that happens, the .maintenance file tells WordPress to show the short notice instead of a half-updated site. The file holds a timestamp, and in normal operation the last step of the update removes it.

Common reasons that last step never runs:

  • You closed the browser tab or lost connection while a batch of updates was running.
  • The server hit a PHP time limit or memory limit partway through.
  • Several plugins were updated at once and one of them failed to unpack.
  • The host ran out of disk space, so the new files could not be written.
  • File permissions prevented WordPress from replacing a folder.

WordPress itself ignores a .maintenance file older than about ten minutes in some situations, but you cannot rely on that, especially with caching in front of the site. Deleting the file by hand is the dependable fix.

Deleting .maintenance with the hosting file manager

This route needs nothing more than your hosting login.

  1. Log in to the hosting control panel (cPanel, Plesk, or the host's own dashboard) and open File Manager.
  2. Go to the WordPress root. It is usually public_html, httpdocs or www, or a subfolder if WordPress lives at /blog. You are in the right place when you see wp-config.php, wp-admin and wp-content.
  3. Turn on hidden files. In cPanel this is under Settings in the top right, then "Show Hidden Files (dotfiles)". Files that start with a dot are hidden by default.
  4. Find .maintenance, select it and choose Delete.
  5. Reload your site in a private browser window. If a caching plugin or CDN is active, purge its cache as well.

Deleting it over SFTP

If you prefer a desktop client such as FileZilla, Cyberduck or WinSCP:

  1. Connect with the SFTP details from your hosting panel. Use SFTP rather than plain FTP where the host offers it.
  2. Enable hidden files. In FileZilla this is Server > Force showing hidden files.
  3. Open the WordPress root folder, right-click .maintenance and delete it.

On a server with SSH access, the same thing takes one command run from the WordPress root: rm .maintenance.

Working out which update failed

The site is back, but something is now probably half-updated. Check before you carry on:

  1. Log in to wp-admin and open Dashboard > Updates. Anything still listed as needing an update is a likely suspect.
  2. Open Plugins > Installed Plugins. A plugin that was mid-update may show as deactivated, may be missing entirely, or may show an error about a missing main file.
  3. Look in wp-content/upgrade via the file manager. Leftover folders there point to the package that was being unpacked when the process stopped. You can delete their contents once you have noted the names.
  4. If you see a plugin folder with an odd name such as plugin-name.tmp or two copies of the same plugin, that is the one that broke.
  5. Check the PHP error log in the hosting panel for messages from around the time of the update. "Allowed memory size exhausted" or "Maximum execution time exceeded" tells you the server limits need raising.

Re-running the update properly

With the culprit identified:

  1. Take a backup first. Use your backup plugin or the host's snapshot tool, so you can get back to this moment if the second attempt also fails.
  2. Update one item at a time. Start with WordPress core if that was involved, then each plugin individually, reloading the front end after each.
  3. Reinstall rather than update if files are damaged. For a plugin from the WordPress.org directory, deactivate and delete it (its settings normally stay in the database), then install it again. For a premium plugin, download a fresh zip from the vendor and upload it.
  4. Raise limits if the log showed them. Ask your host to increase PHP memory or execution time, or set them in the panel's PHP settings.
  5. Free disk space if the account was full. Old backup archives inside wp-content are often the largest files.

If the site shows a white screen or a "critical error" message instead of maintenance mode, that is a different fault: a plugin or theme is crashing PHP. Resolve the maintenance file first, then deal with the crash separately.

Update habits that prevent a repeat

  • Update in small batches. Selecting twenty plugins and clicking "Update" in one go is the most common way to end up here.
  • Stay on the page. Keep the tab open until WordPress shows the success message for every item.
  • Back up before every update round. An automatic daily backup plus a manual one before big updates (WooCommerce, page builders, major core versions) covers most risks.
  • Use a staging site for large updates. Many hosts offer one-click staging; test there, then repeat on the live site.
  • Pick a quiet time. Run updates when traffic is low so that a short outage affects few visitors.
  • Keep an eye on disk usage. Check storage in your hosting panel monthly so a full disk never interrupts an update.

The official Updating WordPress page covers manual core updates if the automatic route keeps failing.

FAQ

Is it safe to delete the .maintenance file?

Yes. It only contains a timestamp that triggers the notice. Deleting it does not remove content or settings. What it does not fix is whatever update failed, so check that afterward.

I cannot see the .maintenance file anywhere. What now?

Make sure hidden files are switched on and that you are in the folder containing wp-config.php. If it truly is not there and the message persists, purge your caching plugin, your host's server cache and any CDN, because a cached copy of the notice may be what visitors see.

Can a maintenance mode plugin cause the same message?

A maintenance or coming-soon plugin shows its own designed page, usually with your logo and text. The plain one-line "Briefly unavailable" text comes from WordPress core and the .maintenance file.

Should I turn off automatic updates to avoid this?

Not necessarily. Automatic minor core updates fix security issues. It is usually better to keep them, make sure backups run, and handle larger plugin updates yourself in small groups.

If updates keep stalling on your site and you would rather someone keep it patched and backed up, let us know how it is set up and we will suggest a maintenance routine.

Sources

WhatsAppBook a call