WordPress puts the site into maintenance mode during updates and takes it out again when finished. If the update fails partway, the flag stays and the site keeps showing the notice. The visible problem is trivially fixable. The real question is what state the interrupted update left behind, which is what actually matters.
Before you buy — this one you can often fix yourself
We would rather tell you than sell you something you do not need.
Over SFTP, look in the site root for a file called .maintenance. Delete it and reload the site. It is a temporary flag and deleting it is safe.
Site comes back and works — you are done, and it cost you nothing.
Site comes back broken, or the notice returns — the update failed partway and left files half-written. That is the real problem, and that is what this fix is for.
Site stuck in maintenance mode
An update left the site stuck showing a maintenance notice. We clear it safely, check whether the update actually completed, and repair anything it left half-finished.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
This or something else?
| Maintenance notice and nothing else | Often self-fixable — see above |
| Notice returns after deleting the flag | This fix covers it |
| Site is broken once the notice clears | Fatal PHP error after update |
| Update failed and the site is blank | White screen of death |
| You want the update reverted entirely | Failed update rollback |
What you are seeing
- A maintenance notice on every page, including the admin
- It has been there far longer than an update should take
- It may have appeared after an automatic update overnight
- Deleting the flag brings the site back broken, or the notice returns
Common causes
- An update interrupted by a timeout, a memory limit, or a lost connection
- Two updates running at once and colliding
- A file permission problem preventing the update from completing
- Disk space exhausted partway through unpacking files
- The update itself failing and never reaching its cleanup step
What we do
- Take a full backup before touching anything
- Clear the maintenance flag and see what state the site is actually in
- Verify whether the interrupted update completed, partially applied, or failed
- Repair or complete anything left half-written
- Identify why the update failed, so the next one does not do the same
- Load-test every template and confirm the site is fully functional
What is included
- A site out of maintenance mode and verified working
- The interrupted update either completed properly or cleanly reverted
- A note on why the update failed and what to change before retrying
- The pre-fix backup, kept for 30 days
Not included
- Rewriting a plugin that fails to update cleanly every time
- Upgrading hosting where the cause is genuinely insufficient resources
- Restoring a full backup, which is a separate service
- Design changes or content work
Questions about this fix
You just told me how to fix it myself. Why would I buy this?
Because deleting the flag only removes the notice. If the update failed partway, you now have a site running half-old and half-new files, which breaks in ways that are much harder to trace later. This fix checks and repairs that.
How long should maintenance mode normally last?
Seconds. WordPress sets the flag, swaps the files, and clears it. Anything more than a minute means the update did not finish, and hours means it definitely failed.
It happens on every automatic update. Why?
Usually a timeout or a resource limit that the update cannot complete within. It will keep happening until that is addressed, which is part of what we diagnose here.
Is my site visible to visitors while this is showing?
No — they see the same notice. Search engines treat it as temporary, so a few hours does no harm. Days of it will start to affect crawling.
Can I prevent this on future updates?
Partly — running updates on staging first removes the risk entirely, and there are ways to make live updates more resilient to a dropped connection. We can set either up if repeated interruptions are a pattern for you.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.