Help for owners
A WordPress update failed and my site is stuck on a maintenance message
Short answer
During an update WordPress creates a .maintenance file in the site root. If the update is interrupted the file stays, and visitors keep seeing the maintenance message. The WordPress handbook says to delete that file over FTP. Do it only after copying the site, because an update that stopped half way can also leave files and database out of step.
Does this sound like your situation?
- The site says Briefly unavailable for scheduled maintenance and never goes away.
- I clicked update, the page timed out, and now the site is broken.
- The admin shows an update that will not finish.
- Part of the site looks old and part looks new.
- It happened while updating several plugins at once.
Why does this happen?
The maintenance file was not removed
The WordPress handbook explains that after an upgrade WordPress creates a .maintenance file, and if it is not removed properly visitors may see the Briefly unavailable message. Deleting the file from the site root via FTP clears it.
Confirmed by developer.wordpress.org
The update ran out of time or memory
The handbook lists memory limits and connection timeouts, common on shared hosting, as recurring causes of errors. A large update that runs out of either stops in the middle.
Confirmed by developer.wordpress.orgTechnical detail: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted
A plugin or theme failed after the update
An update that completes but leaves a plugin broken can show a blank screen or a critical error. The handbook advises deactivating plugins and reactivating them one by one.
Confirmed by developer.wordpress.orgTechnical detail: wp-admin loads a completely blank page in WordPress
Files and database got out of step
WordPress needs both the files and the database for a working site. If an update stops after writing some of one but not the other, the site can load but behave oddly.
Confirmed by developer.wordpress.org
No backup was made first
The handbook advises backing up the database regularly and always before an upgrade. Without it, a failed update leaves nothing to return to.
Confirmed by developer.wordpress.org
What can I do about it today?
- Do not click update againA second attempt on top of a half-finished one can make it worse.
- Ask your host for a backup copyFiles and database both. The handbook says a site needs both to be fully restored. Ask what restore points the host already keeps.
- Note what was being updatedCore, one plugin, several plugins, or a theme, and when. This decides the next step.
- Leave file deletion to someone who can restoreRemoving the .maintenance file is the handbook's fix, and it is small, but do it only once a copy exists.
- Put a message on social channels if you sell onlineA short note that the site is being maintained prevents lost trust while it is fixed.
- After it returns, update one thing at a timeUpdate plugins singly, with a backup, and check the site between each.
When should I bring someone in?
- The maintenance message stays after the file is removed, or the site now shows an error.
- You do not have FTP or file access.
- The site takes orders, bookings or payments.
How do I handle it?
- Copy firstFiles and database are saved in their current state before I change anything.
- Find how far the update gotVersion numbers, file dates and the log show whether core, plugins or the database stopped part way.
- Clear the lock and finish or reverse the updateI remove the maintenance file, then complete the update on a copy, or restore the earlier version if that is safer.
- Find why it failedMemory, time limits, disk space or file permissions are checked so it does not repeat.
- Set a safer update routineBackup, test on a copy, update singly, check forms and checkout, with a tested rollback.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is it safe to delete the .maintenance file?
The WordPress handbook gives it as the fix for the stuck message. I would still copy the site first, because the update that stopped may have left other things unfinished.
Will I lose my content?
Posts and pages live in the database, which an interrupted file update normally does not erase. A copy first removes the doubt.
Should I turn on automatic updates?
The hardening guide says automatic updates have been available since version 3.7 and can make updating easier. With a shop, I would still want backups and a test first.
Why did it work before?
Small updates fit inside the time and memory limits. A bigger one, or a slower server, can hit them.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
wp-admin shows an empty white page and no errorwp-admin loads a completely blank page in WordPressFatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes)PHP Fatal error: Allowed memory size of 134217728 bytes exhaustedA white page with no output at all (HTTP 500 in the access log)PHP shows a blank page and no error message