Site stuck on “Briefly unavailable for scheduled maintenance”: how to get back online fast

You clicked “Update,” closed the tab or lost your connection for a second, and now your entire site shows a single line: “Briefly unavailable for scheduled maintenance. Check back in a minute.” No page loads, and the admin dashboard is locked too. It's the kind of moment where it feels like you broke everything.

The good news: you almost certainly didn't. That message isn't an error — it's a WordPress safety mechanism that got stuck in the “on” position after an interrupted update. In most cases you can fix it in a few minutes by deleting a single file. Below I'll show you what actually happened, how to unlock it step by step, and how to keep it from happening again.

Why the message appears (the .maintenance file)

When you update WordPress core, a theme, or a plugin, the system automatically creates a hidden file called `.maintenance` in your site's root folder. As long as that file exists, WordPress shows every visitor the maintenance page — so nobody sees a half-updated site while the new files are being copied in.

Normally WordPress deletes that file by itself the instant the update finishes. The trouble starts when the process is cut short: you closed the tab too quickly, your session timed out, your connection dropped, or the server was slow. The update never reaches its final step, `.maintenance` stays on the server, and your site remains locked in maintenance mode indefinitely.

So your content isn't broken — it's just a padlock left hanging on the door.

The quick fix: delete the .maintenance file

You need to delete that file from your site's root. That means file access: either through your hosting panel (File Manager in cPanel/Plesk, or your host's own manager) or via FTP (FileZilla).

• Go to your site's root folder — where you can see `wp-config.php`, `wp-content`, and `wp-admin`.
• Turn on showing hidden files. `.maintenance` starts with a dot, so it's hidden by default. In cPanel: Settings → “Show Hidden Files.” In FileZilla: Server → “Force showing hidden files.”
• Delete the `.maintenance` file. Just that one, nothing else.
• Do a hard refresh in your browser (Ctrl+F5 or Cmd+Shift+R).

In most cases the site comes right back. If you use a caching plugin, clear the cache afterward.

If it still won't load: the update stalled halfway

If, after deleting the file, the site loads but a page is blank, throws errors, or something looks broken, it means the update did manage to replace some files before it stopped. Don't panic — there's a clean path forward:

• Log into the admin (`/wp-admin`) and check Updates to see whether WordPress, the theme, or that plugin still shows as needing an update. Run it again — this time leave the tab open until it fully finishes.
• If you get a completely white screen, temporarily disable the plugin that was updating. You can rename its folder inside `wp-content/plugins` (e.g. `plugin-x` → `plugin-x-off`), which switches it off, then reactivate it from the admin.
• Clear your cache (both the caching plugin and any host/CDN cache).

If you have a backup from before the update, restoring it is the safest way back to a working state.

How to keep it from happening again

A stuck maintenance mode is almost always the result of an interrupted update. A few simple habits prevent it:

• Don't close the tab or navigate away until you see “Update complete.” An update can take longer than you'd expect on slow connections or servers.
• Update one thing at a time, not dozens of plugins at once. If something hangs, you know exactly what caused it.
• Take a backup before major updates (WordPress core or important themes). Most good hosts run automatic backups — find out where they are and how to restore them.
• Ideally, test updates on a staging environment before applying them to the live site.

Decent hosting plus updates done sensibly is the difference between “five minutes of fright” and “a lost day.”

When it's worth asking for help

If you've deleted the file and the site still won't come back, or you're getting database errors or a white screen and you're not sure what you touched, that's the moment to stop forcing it — every blind attempt can make things messier. Someone who has seen this before usually pulls the site out of maintenance and fixes the stalled update quickly, without losing content.

At MPO Web Studio we work fully remote, across the whole country, so it doesn't matter where you are: send us access, we take a look, and we tell you honestly what happened and how long it'll take. If you'd like a hand right now, message us on WhatsApp with a short description and a screenshot of the message — we respond quickly and tell you straight whether it's a five-minute fix or something bigger.