If your site is showing “Briefly unavailable for scheduled maintenance. Check back in a minute” — and that minute has stretched into ten, or an hour — your WordPress site is stuck in maintenance mode. It’s a common scare, but it’s almost always a trivial fix that takes about a minute once you know the trick. Better still, nothing is broken and nothing is lost. WordPress just forgot to flip a switch back off, and you’re going to flip it for it.
Here’s what happened: when WordPress updates itself, a plugin, or a theme, it puts the site into maintenance mode so visitors don’t see a half-updated page. It does this by creating a single temporary file. When the update finishes, it deletes that file and the site returns. If the update was interrupted — a timeout, a memory limit, a lost connection — the file never gets deleted, and your site stays “briefly unavailable” indefinitely.
The fix: delete the .maintenance file
The whole problem is one hidden file called .maintenance sitting in your main WordPress folder (the same folder as wp-config.php and wp-admin). Delete it and the site comes straight back.
Connect to your site over SFTP (a secure way to connect to your site’s files) or through your host’s file manager, then:
- Go to the root WordPress folder (usually
public_html, or the folder that containswp-config.php). - Make sure hidden files are shown — the file starts with a dot, so it’s hidden by default. In most file managers there’s a “show hidden files” toggle; in an SFTP client, enable showing dotfiles.
- Find
.maintenanceand delete it. - Reload your site. It should be back instantly.
That’s genuinely the entire fix in most cases. Deleting this file doesn’t undo anything or harm your site — it just tells WordPress the maintenance is over.
Step 2: Finish the update that stalled
Your site is back, but the update that got interrupted may not have completed. Log into your dashboard and check Updates, plus your plugins and themes list. Re-run whatever was mid-update so nothing is left half-applied. Update one thing at a time here, rather than clicking “update all,” so if one stalls again you know exactly which one.
Step 3: Find out why the update stalled
Deleting the file cures the symptom; you also want to know why the update timed out, so it doesn’t happen every time. The usual reasons:
- Too little memory or too short a timeout — the update ran out of room or time mid-way. This is common on crowded budget hosting.
- Updating too much at once — bulk-updating a dozen plugins together makes a timeout far more likely than doing them one by one.
- A slow or overloaded server — if the server is already straining, an update is the extra push that tips it over.
If the site is still broken after deleting the file
If you remove .maintenance and the site returns with a different problem — a blank page, or a “there has been a critical error” message — then the interrupted update didn’t just get stuck, it left something half-installed. That’s a separate fix: see our guide to the “there has been a critical error” page, which walks through deactivating the plugin or theme that didn’t finish. If you’d rather not chase it, restoring a clean backup puts everything back to the moment before the update.
How to avoid it next time
Getting stuck in maintenance mode is really a symptom of updates being run in a risky way — live, all at once, on a server without the headroom to finish them. The safer approach is to update on a staging site first, apply updates in small batches, and make sure the server has enough memory and time to complete each one. That’s the difference between an update that finishes cleanly and one that strands your site behind a “check back in a minute” sign. Our guide on whether WordPress updates break sites goes deeper on doing them safely.
When the fix is really the host
An update that stalls halfway isn’t bad luck — it’s usually a sign of a server without the resources or the care to see updates through. On bargain shared hosting, updates run unsupervised on stretched-thin resources, so a stuck maintenance mode is just something that happens now and then, and it’s on you to go delete a hidden file to recover.
That’s the everyday difference with managed WordPress hosting. Every time we update your site, we verify it still looks and works right — updates are applied carefully, with enough resources to finish, and checked afterward, so they don’t strand your site behind a maintenance screen in the first place. If one ever does, there’s a real US-based team who catches it, not a customer discovering it hours later. And it’s the same flat price whether you run one site or many — careful updates are part of the plan, not a premium tier.
The short version
- Connect over SFTP or the file manager and show hidden files.
- Delete the
.maintenancefile in your root WordPress folder. - Reload the site — it’s back.
- Re-run the update that stalled, one item at a time.
- If a different error appears, treat it as an interrupted update or restore from backup.
If you’d rather not be hunting for hidden files while your site is down, or updates keep stranding you here, hand it over. Keeping updates from breaking sites is routine work for our US-based team — and if a stuck update left real damage, our guide to restoring from a backup is the clean way back.