How to Fix “Briefly Unavailable for Scheduled Maintenance” in WordPress

← Back to all WordPress fixes

Introduction

You update a few plugins, step away for a moment, and come back to find your entire site showing a single line: “Briefly unavailable for scheduled maintenance. Check back in a minute.” A minute passes. Then ten. The message never goes away. Your site is stuck in maintenance mode — and the good news is that this is one of the easiest WordPress errors to fix, usually in under a minute.

Here’s why it happens and exactly how to get your site back online.

Why WordPress Gets Stuck in Maintenance Mode

Whenever WordPress updates a plugin, theme, or its core, it briefly puts your site into maintenance mode so visitors don’t see a half-updated site. It does this by creating a hidden file called .maintenance in your site’s root folder, and it deletes that file automatically the instant the update finishes.

The problem happens when an update doesn’t finish cleanly — for example, if you closed the tab mid-update, the server timed out, or you updated many plugins at once and one stalled. The update stops before WordPress can remove the .maintenance file, so it’s left behind — and as long as that file exists, every visitor sees the maintenance message.

The Fix: Delete the .maintenance File

Because the stuck state is caused by one leftover file, removing it brings your site straight back. You’ll need FTP access or your host’s File Manager:

1. Connect to your site via FTP (with a client like FileZilla) or open your host’s File Manager.
2. Go to your WordPress root folder — the same directory that contains wp-config.php, wp-content, and wp-admin.
3. Find the file named .maintenance. (It starts with a dot, so you may need to enable “show hidden files” in your FTP client or File Manager.)
4. Delete it.
5. Reload your site — it should be back to normal immediately.

After You’re Back Online: Finish What the Update Started

Deleting the file clears the symptom, but the update that triggered it was interrupted — so check that everything actually completed:

• Log in to wp-admin and open Dashboard → Updates. Re-run any plugin, theme, or core update that didn’t finish.
• Update one item at a time this round, rather than in a big batch, so a single slow update can’t stall the whole queue.
• If an update keeps stalling, the underlying cause is often a server timeout or low memory — see how to fix the 500 Internal Server Error and why processes time out on shared hosting.

How to Avoid Getting Stuck Again

• Don’t close the tab during updates. Let each update finish before navigating away.
• Update in small batches. A handful at a time is far less likely to stall than updating everything at once.
• Back up before every update. If an interrupted update leaves more than a leftover file — say, a half-applied database change — a fresh before-update backup lets you roll back instantly.
• Test big updates on staging. Major version jumps are safest rehearsed on a staging site first.

Frequently Asked Questions

Will deleting the .maintenance file break anything?
No. It’s a temporary flag, not part of your site’s content or configuration. WordPress recreates it automatically the next time it runs an update, then removes it when finished.

I don’t see a .maintenance file — what now?
Make sure hidden files are visible in your FTP client or File Manager (files starting with a dot are hidden by default). If it’s genuinely not there, your stuck page may be a different issue — check for a white screen or 500 error instead.

Could the interrupted update have damaged my site?
Usually it just leaves the flag file. But if a plugin was only half-updated, you might see other errors afterward. Re-running the update normally fixes it — and a pre-update backup is the safety net if it doesn’t.

How do I access the file if I don’t have FTP set up?
Most hosts include a File Manager in their control panel (cPanel, Plesk, or a custom dashboard) that lets you browse and delete files without an FTP client.

Conclusion

“Briefly unavailable for scheduled maintenance” looks like your site is broken, but it’s really just a leftover flag from an update that didn’t finish. Delete the .maintenance file, reload, and you’re back — then re-run the update that stalled. Keep updates small and a backup handy, and this one becomes a non-event.