Stuck in maintenance mode
"Briefly unavailable" — for three hours now.
WordPress shows that message during updates, then removes it automatically. When an update dies mid-flight, the message stays — and your whole site, admin included, sits behind a sign that promises 'briefly' and means 'until someone intervenes.'
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
Before every update, WordPress drops a temporary file named .maintenance into the site root, which switches all traffic — including yours — to the holding message. The update's final act is deleting that file. If the update crashes, times out, or the connection drops mid-process, the flag file survives, and WordPress keeps obeying it forever.
The message itself is almost never the real problem, then — it's the leftover flag. The real question worth a minute of attention is why the update died: a timeout is trivia, a half-installed plugin is a follow-up repair waiting to announce itself.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
An update interrupted mid-process
Browser tab closed, connection dropped, or server timeout during a bulk update — the flag file's deletion never ran. The overwhelming majority case.
Updating too much at once
Ten plugins in one batch on modest hosting invites a timeout partway. The batch died; the flag stayed.
The update actually failed
Sometimes the flag lingers because the plugin update underneath genuinely broke. Removing the flag then reveals the real casualty — which is still progress, but not the finish line.
A maintenance-mode plugin misbehaving
Different mechanism, same costume: a 'coming soon' plugin that lost its off switch. Distinguishable because wp-admin usually still loads.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Wait ten honest minutes
A big update on slow hosting may still be finishing. Ten minutes, not ten seconds — and only once. If the message survives a real wait, it's stuck.
- 2
Check whether wp-admin loads
Admin working while the front shows maintenance points at a plugin's maintenance mode, not the core flag — a settings toggle rather than a file fix.
- 3
If you know your way to the file manager, look for .maintenance
In the site root, a file named exactly '.maintenance'. Deleting it is the textbook fix and safe if that's all you touch. If file managers aren't your territory, this is a two-minute professional job — no shame in that trade.
Stop and call when…
- The flag is gone but the site came back broken — the update underneath failed
- You can't find or access the site root confidently
- This is the second time this month — the updates themselves need investigating
From there it’s our job: same-day look, flat quote, and the $229 flat repair covers most cases of exactly this.
Single Error Fix — buy it now, skip the hunt.
One error, hunted down and fixed — 500s, white screens, redirect loops, broken pages.
Covers one specific error or broken behavior on one site. Diagnosis, the fix, and a plain-English note on what happened. If we can't fix it, you get a full refund.
Questions we hear a lot.
Is my site broken or just hidden?
Usually just hidden — the site is intact behind the flag, and removing the leftover file restores it exactly as it was. The exception is when the interrupted update also broke something, which reveals itself the moment the curtain lifts.
Can I prevent this?
Mostly: update in small batches rather than all at once, don't close the tab mid-update, and run updates at quiet hours. Chronic stickiness usually means underpowered hosting timing out — a capacity conversation worth having once instead of a flag file conversation monthly.
The flag's deleted but now I have a white screen. What happened?
The update that died mid-flight left a half-installed plugin or theme — the maintenance flag was hiding the crash. That's the white-screen playbook from here; the good news is the failing component is almost certainly the one that was updating.
What does the flat fix cover?
Removing the flag, verifying the interrupted update completed or completing it cleanly, and confirming the site's actually healthy underneath — not just visible. $229, same-day, refunded if we somehow can't.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Lift the curtain. Check what's under it.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.