WordPress Stuck on "Briefly Unavailable for Maintenance"

If WordPress is stuck on “Briefly unavailable for scheduled maintenance. Check back in a minute”, an update was interrupted and left a file called .maintenance in your site’s root folder. Delete that file over FTP or your host’s file manager and the site comes back immediately. Then check that the update finished, and run it again if it did not.

Key Takeaways

• The message is normal for a few seconds during an update. If it lasts more than a few minutes, something got stuck.
• The cause is a leftover .maintenance file in the root folder, next to wp-config.php.
• It is a hidden file, so switch on “show hidden files” before you look for it.
• After deleting it, confirm the update finished and re-run it if needed.
• Back up before updating, so an interrupted update is never serious.

This is one of the easiest WordPress errors to fix once you know where to look, and it rarely damages anything. Do not panic and do not keep refreshing.

What Does “Briefly Unavailable for Scheduled Maintenance” Mean?

When WordPress updates core, a plugin or a theme, it puts the site into maintenance mode. It does that by creating a small file named .maintenance in the site’s root folder. While the file exists, visitors see “Briefly unavailable for scheduled maintenance. Check back in a minute.” When the update ends, WordPress deletes the file and the site returns.

If the update is interrupted, the file is never deleted, so the message stays. That is all it is. It is a status message, not a sign of hacking.

What Causes It to Get Stuck?

• Closing the browser tab or losing your connection during an update.
• A server timeout or resource limit hit during a large update.
• Updating many plugins at once, which can overload a small hosting plan.
• An update that crashed because of a plugin conflict or low memory.
• A slow or interrupted file transfer on the server.

How Do You Fix It?

First wait five minutes. A large update on a slow server can legitimately take that long. If the message is still there, carry on.

Take a backup of your site files before you start, if you can.

1. Connect to your site files

Use FTP, SFTP or your host’s file manager (cPanel, Plesk and similar all have one). Go to the root folder, which is the folder containing wp-config.php, wp-admin and wp-content. It is often called public_html or www.

2. Show hidden files

Because the file name starts with a dot, many tools hide it. In FileZilla go to Server > Force showing hidden files. In cPanel’s File Manager, open Settings and tick “Show Hidden Files (dotfiles).”

3. Delete the .maintenance file

Find .maintenance and delete it. Reload your site. It should load normally. Clear your browser cache if you still see the message, and clear any caching plugin or host cache too.

4. Check what the update left behind

Log in to wp-admin. Go to Dashboard > Updates to see whether the core, plugin or theme update finished. If it still shows as available, the update did not complete.

Also check the Plugins page and the front end for problems. An update that stopped halfway can leave a plugin in a broken state.

5. Run the update again

Re-run the failed update, this time on its own and without closing the tab. If a plugin update keeps failing, download the latest version from its page on wordpress.org (or the vendor), deactivate and delete the old copy, and upload the new one. Do the same by FTP if the dashboard route fails. Your settings are normally kept in the database, but make sure of that for your plugin before deleting it.

If the update broke the site badly, the white screen of death guide or the critical error guide covers what to do next.

6. If a core update failed

If WordPress core itself was updating, a failed update may leave a wp-content/upgrade folder with temporary files. Once the site works, you can delete its contents. Re-run the update afterwards. If it fails again, upload a fresh copy of WordPress files (excluding wp-content and wp-config.php) over FTP.

How Do You Stop It Happening Again?

• Update one thing at a time, and stay on the page until it finishes.
• Avoid bulk updates on small hosting plans.
• Back up first. An interrupted update is a small problem when you have a recent backup.
• Update at quiet times, and make sure your host has enough memory and execution time.
• Check whether an update is safe before you install, especially for big plugins.
• Monitor the site. A forgotten maintenance page can sit there for hours, turning away customers. Monitoring catches it.

TalkToWP checks every site every 5 minutes on every plan, Free included. If your site gets stuck in maintenance mode or breaks after an update, it tells you which plugin or update caused it and hands you the fix in plain English. The free plan covers one site, and you can sign up here.

Frequently Asked Questions

Where is the .maintenance file?

It sits in the root folder of your WordPress install, in the same place as wp-config.php. It is hidden because its name starts with a dot, so enable “show hidden files” in your FTP client or file manager before you look.

Is it safe to delete the .maintenance file?

Yes. WordPress creates it automatically at the start of an update and deletes it at the end. Removing it simply ends maintenance mode. The only risk is that the update was incomplete, so check it afterwards.

How long should maintenance mode last?

Normally a few seconds, and rarely more than a minute or two. If the message is still there after five minutes, the update is stuck and you should remove the file.

I deleted the file and the message is still there. Why?

Clear your browser cache, then any caching plugin or host cache, which may be serving the old page. Also check that you deleted the file in the correct root folder, especially if you have more than one site on the account.

Could a stuck update mean I was hacked?

Unlikely. It is nearly always a timeout or an interruption. If the site behaves oddly afterwards, scan it for modified core files and check your user list for accounts you do not recognise.