WordPress problem fix
A failed update left a marker file behind. Delete it and the site is back. Then we make sure it never happens again.
WordPress shows 'briefly unavailable for scheduled maintenance' when an update is in progress. If the update fails or times out, the marker file does not get cleaned up and the site stays in maintenance mode. The fix is to connect over SFTP or the host file manager, delete the file named .maintenance in the WordPress root, and reload the page. The site comes back immediately. After that, address the underlying cause, usually a slow host or too many plugins updating at once, so it does not recur.
If any of these match, you are on the right page.
Every page shows 'briefly unavailable for scheduled maintenance'
wp-admin is also unreachable
It started during a plugin or theme update
Waiting did not fix it
The update process timed out before it could delete the .maintenance file, usually because the server is slow, memory is low, or too many plugins were updated at once.
Yes if the underlying cause is not fixed. Updating one plugin at a time, on a host with enough resources, prevents it.
The real method, in the order it works.
Connect to the site over SFTP or the host file manager.
Find the file called .maintenance in the WordPress root folder.
Delete it.
Reload the site. It should come back instantly.
Re-run the update that failed, but one plugin at a time.
Real fix, from our work
A client tried to bulk-update fifteen plugins on a low-tier shared host. The host killed the update halfway through, leaving the site in maintenance mode. We deleted the .maintenance file, ran the remaining updates one at a time with staging snapshots between each, and moved the site to a faster host the same week so it would not happen again.
Written by Ali Yasin Jatoi
Founder of WebCare Studios. Ali has worked with WordPress for more than 10 years, including managing a fleet of 150+ sites with WP-CLI automation for updates, security cleanup, and malware removal. He has hands on experience across major hosts including Cloudways, A2 Hosting, Hostinger, and Bluehost.
Site down, hacked, or broken checkout gets a senior engineer within 4 hours. No ticket queues, no bots.
Flat quote up front. If we cannot get you back online, you do not pay. Risk sits with us, not you.
We work on a snapshot first and never touch your live database until the fix is verified safe.
We run a fleet of WordPress sites every day. The errors you are seeing are ones we have closed hundreds of times.
WordPress creates a .maintenance file at the start of any update so visitors see a friendly message instead of broken pages. Normally the file is deleted automatically when the update finishes. If the update fails, the file is left behind and the site stays in maintenance mode.
No. It just removes the lock. Any incomplete update may need to be re-run, but no data is lost by deleting the file.
Update one plugin at a time, take a backup before each one, and use staging when the plugin is critical. We do this every week on every site we manage.
Yes. Our maintenance plan handles plugin updates in staging, runs visual regression, and pushes only after the site is verified.
Two fields. Email and your URL. A senior WordPress engineer reads it within minutes and replies on email and WhatsApp with what is wrong and what we will do next.