WordPress Stuck on "Briefly Unavailable for Scheduled Maintenance" Print

What you're seeing

Your site shows a short message: Briefly unavailable for scheduled maintenance. Check back in a minute. Except the minute passes, and another, and it is still there. The site is stuck.

Good news first: this is the most harmless problem on this list, and often the quickest to fix. Nothing is broken and nothing is lost. WordPress has simply got stuck in a mode it should have left automatically.

Why it happens

Whenever WordPress updates a plugin, theme, or its core, it briefly puts the site into maintenance mode so visitors do not see a half-updated page. It does this by dropping a small temporary file into your site, showing the maintenance message, and then deleting that file the instant the update finishes. Normally you never even notice.

If an update is interrupted partway, the browser tab closed, two updates started at once, a connection dropped, the update never reaches its final step, so the temporary file is never deleted. WordPress keeps showing the maintenance message because, as far as it knows, an update is still running. It is not. It just needs that leftover file removed.

The fix

The file is called .maintenance, and it sits in the main folder of your WordPress installation. Deleting it ends maintenance mode immediately and your site returns.

1. Log in to cPanel at yourdomain.tld/cpanel.
2. Open File Manager and go into your site's main folder, usually public_html, as described in our cPanel tour.
3. Make sure hidden files are visible. The file begins with a dot, which hides it by default, in File Manager's Settings, tick Show Hidden Files (dotfiles).
4. Find the file named .maintenance and delete it. It is safe to delete, it is only ever meant to exist for a few seconds during an update.
5. Reload your site. It should be back.

This is one of the few file-level fixes that is genuinely safe to do yourself, because you are deleting a temporary file that should not be there, not editing anything that matters.

Afterwards: finish what was interrupted

Your site is back, but remember why it stuck: an update did not finish. So check that whatever was updating actually completed. Go to your WordPress dashboard and look at Updates, and finish any that are still pending, this time letting each one complete fully before moving on. Our article on updating WordPress safely covers doing this without a repeat.

Hand it to us when

You have deleted the .maintenance file and the site is still stuck, which points at a separate problem wearing the same message, or you would simply rather not go into File Manager at all. Open a support ticket and we will clear it in moments. It is a small job and we are glad to do it, no client should be staring at a stuck site over a leftover file.

Good to know

The way to avoid this entirely is to let updates finish before doing anything else, one at a time, without closing the tab, which is part of the discipline our article on updating WordPress safely lays out. And this is a small, low-stakes preview of a larger truth about WordPress: most of its scares come down to an interrupted or outdated update, which is exactly why keeping updates done properly, whether by you or through our WordPress update service, prevents most problems before they start.