WordPress Stuck in Maintenance Mode? Fix the Briefly Unavailable Message

You clicked Update, the page reloaded, and your website now shows Briefly unavailable for scheduled maintenance. Check back in a minute. A minute passed, then ten. Visitors see the same message and the dashboard may be unreachable too. This guide explains what the message is, how to remove it safely and how to stop it returning.

If your site shows a different message, such as a critical-error screen or a blank page, start with the WordPress critical-error guide. Those failures have different causes, and the file described here will not be involved.

What the maintenance message actually means

Maintenance mode is a deliberate WordPress feature, not an error. The core maintenance check looks for a .maintenance file in the installation root. If the file exists and its recorded timestamp is less than ten minutes old, WordPress stops normal page loads and shows the notice with an HTTP 503 status. While updates are being installed, this protects visitors from loading a half-replaced plugin or theme.

The maintenance function also sends a Retry-After header, which tells search engines and other automated clients that the outage is temporary. A short maintenance window is therefore normal. The problem starts when the update process stops before it reaches the step that deletes the file.

• Update finished normally: the file is removed and the notice disappears within seconds. Nothing to fix.
• Update interrupted: the file remains and the notice continues for up to ten minutes, then WordPress ignores the old timestamp. The incomplete update still needs attention.
• Message continues beyond ten minutes: something is recreating the file, the server clock is unusual, or a maintenance plugin is showing its own page. Investigate rather than deleting the file repeatedly.
• A styled coming-soon page: that comes from a plugin setting or a maintenance.php drop-in, not from a stuck update.

Interruptions have ordinary causes: closing the browser tab mid-update, updating many plugins at once on a slow server, a PHP time or memory limit, a lost connection to the update servers, or file-permission problems that stop WordPress replacing files. The WordPress common-errors reference lists failed automatic updates and leftover maintenance mode as related symptoms for exactly these reasons.

1. Wait ten minutes before changing anything

Because WordPress ignores a .maintenance file whose timestamp is older than ten minutes, a brief wait resolves many cases on its own. Do not reload the update screen, start another update or restart the server during this time. If the update was still running slowly rather than dead, another attempt can create a second overlapping process.

Use the wait to collect facts: which update you started, roughly when, whether you saw an error, and whether you have a recent backup. If your host provides a dashboard with recent backups, confirm the newest one exists and when it was taken. The official updating guide recommends backing up before updates, and if a backup already exists you have a fallback before touching files.

If the site is back after the wait, skip to step four. The update that was interrupted may still be partial, and the dashboard will usually report the plugin or theme as still needing an update.

2. Remove the leftover .maintenance file safely

If the notice continues, connect to your hosting account with the file manager or an SFTP client and open the WordPress root folder, the one containing wp-config.php, wp-admin and wp-content. Enable hidden files if your client hides names beginning with a dot. Delete the single file named .maintenance.

1. 1Confirm you are in the correct installation, especially on accounts hosting several sites or a staging copy.
2. 2Enable hidden-file display in the file manager or SFTP client.
3. 3Delete only .maintenance. Do not remove .htaccess, wp-config.php or any folder.
4. 4Reload the public site in a private window and confirm the notice is gone.
5. 5Log in to the dashboard and note any update warnings.

This is the same step the official documentation gives for clearing a failed-update message. Deleting the file is safe because it contains only a timestamp. What it does not do is complete the update, repair a broken plugin or restore changed files.

3. Check whether the update itself completed

An interrupted update can leave a plugin or theme folder partially replaced. The dashboard may show the item still needing an update, show it as deactivated, or show a PHP error if files are inconsistent. Open Dashboard → Updates and Plugins and compare what you see with what you were updating.

• Item still listed for update: the files were not replaced. Run that single update again once the site is stable.
• Item deactivated or missing: WordPress may have removed the old folder before the new one finished. Reinstall that plugin or theme from its official source, then reactivate.
• Core update interrupted: follow the manual update steps, which replace wp-admin and wp-includes without touching wp-content or wp-config.php.
• Database upgrade prompt: if WordPress asks to update the database after a core update, allow it to run once.

For plugin updates, WordPress also keeps a short-lived lock while an update runs so that two processes do not install the same item at once. The upgrader lock expires on its own, which is why you may see Another update is currently in progress for a while after an interruption. Waiting is the correct response; deleting database rows is not.

If a plugin now causes an error whenever it is active, the problem is the incomplete plugin, not maintenance mode. Reinstall it cleanly from WordPress.org or the vendor's download, keeping its settings, and test on a staging copy where possible.

4. Find the reason the update was interrupted

Deleting the file fixes today's outage. Finding the interruption prevents the next one. The most useful evidence is the server's PHP error log and the hosting account's resource reports for the minutes around the update.

• Timeout or memory message in the log: the update needed more time or memory than PHP allowed. Ask the host what limits apply and whether they can be raised for your plan, rather than guessing a value.
• Connection or download failure: the server could not reach the update source. This is often temporary; retry a single update later.
• Permission denied: WordPress could not write to the plugin or theme folder. The upgrade handbook notes that one-click update problems are usually file-permission or ownership issues, which the host should correct rather than making folders world-writable.
• No log entry at all: the browser tab was probably closed or the connection dropped during the update. Keep the tab open until WordPress reports the update as complete.

Do not change PHP limits blindly in .htaccess or php.ini on a shared plan. Some hosts override those settings; others treat the change as unsupported. A confirmed log entry plus the host's guidance is a better basis than a number copied from a forum.

If this interruption happened during a migration or hosting move, check that file ownership and paths were preserved. The permalinks guide covers the separate rewrite problems that appear after moves, which can be confused with update failures.

5. Update more safely next time

Most stuck-maintenance incidents come from updating many items in one batch on a server with modest limits. A few habits reduce the risk without any new tooling.

1. 1Take or confirm a backup before updates, and know how to restore it.
2. 2Update one plugin or theme at a time, and wait for the completion message before starting the next.
3. 3Keep the browser tab open; WordPress performs the update through that request on many hosts.
4. 4Update during a quiet period for your visitors, because the site is briefly unavailable even when everything works.
5. 5Check the plugin's changelog and compatibility note for your WordPress and PHP versions before major version jumps.
6. 6Test significant updates on a staging copy first if your host provides one.

Automatic background updates behave differently. WordPress applies minor core and security updates in the background by default, and the handbook explains how site owners can enable or restrict automatic updates for plugins and themes. Automatic updates still use maintenance mode briefly, so the same ten-minute rule and the same clean-up applies if one of them is interrupted.

If you want a planned maintenance page for visitors while you work on the site, use a maintenance plugin or a maintenance.php drop-in deliberately. That is a design choice, separate from the update-time notice, and it is switched off from the plugin's own settings.

When to ask for help instead of trying again

Most sites recover with the steps above. Stop and ask for help when the file reappears without an update running, when the dashboard reports database errors, when the host's logs show repeated resource exhaustion, or when you are not confident which installation folder is the live one. Repeating the same update after each failure can leave more files in a mixed state.

Useful details to share with a developer or host: the exact message, the time of the update, which plugin, theme or core version was involved, whether the .maintenance file existed and what you deleted, and any lines from the PHP error log around that time. A sanitised log excerpt is enough; never send passwords or database credentials.

If you prefer the recovery and the follow-up handled for you, WordPress support covers one-off repairs, and ongoing maintenance covers staged updates, backups and monitoring. The maintenance cost guide explains what routine care typically includes. Describe what happened with the public URL and the details above.

Frequently asked questions

Is it safe to delete the .maintenance file?

Yes. The file holds only a timestamp that tells WordPress maintenance mode is active. Deleting it ends the notice. It does not undo or complete the update that created it, so check the affected plugin, theme or core files afterwards.

Why does the message say to check back in a minute but last much longer?

The wording assumes the update will finish. If the process is interrupted, nothing removes the file, and WordPress keeps showing the notice until the timestamp is more than ten minutes old or the file is deleted.

I deleted the file but the site still shows the notice. What now?

Clear any page cache and reload in a private window first; the cached 503 page can outlive the file. If the message persists, check for a maintenance or coming-soon plugin and for a maintenance.php file in wp-content. If the file keeps returning, an update may still be running or restarting; wait for it to finish rather than deleting the file again.

Can I avoid maintenance mode entirely when updating?

Not for standard updates, and you should not try. Maintenance mode protects visitors from loading half-replaced files. The practical goal is to keep it brief: update one item at a time, keep the tab open and fix any server limits that interrupt updates.

Sources and review scope

Reviewed on 22 October 2026 against the WordPress developer reference and the WordPress documentation linked beside the relevant guidance. This is a diagnostic guide, not a report of a repair performed on a customer's website. The photographs are contextual stock images, not WordPress screenshots or evidence that a repair worked. Hosting controls and dashboard labels vary; follow your provider's supported procedures.