Maintenance
"Briefly unavailable for scheduled maintenance" — how to fix it
14 September 2026 · 5 min read
On this page
Your site shows a single line of text: "Briefly unavailable for scheduled maintenance. Check back in a minute." A minute passes. An hour passes. It is still there.
This is one of the easiest WordPress problems to fix, and it takes about two minutes once you know where to look.
What actually happened
When WordPress updates itself or a plugin, it puts the site into maintenance mode first, so visitors do not see a half-updated site. It does this by creating a file called .maintenance in your WordPress root folder.
When the update finishes, WordPress deletes that file and the site returns.
If the update did not finish — the connection dropped, the server timed out, PHP ran out of memory, or you closed the tab — the file is never deleted. WordPress keeps showing the maintenance message forever, because as far as it is concerned the update is still running.
The site is not broken. One file is telling it to stay hidden.
The fix
You need file access. Your hosting control panel's File Manager is usually the quickest route; SFTP works too.
- Open your WordPress root folder — the one containing
wp-admin,wp-content,wp-includesandwp-config.php - Find the file called
.maintenance(with the dot at the start) - Delete it
- Reload your site
That is it. The site should return immediately.
The file starts with a dot, which means it is hidden by default in most file managers. In cPanel File Manager, click Settings in the top right and tick Show hidden files. Over SFTP, enable "show hidden files" in your client.
If you cannot find the file
Check you are in the right folder. On many hosts WordPress lives in public_html, www, or a folder named after your domain. The right one contains wp-config.php.
Check hidden files are visible. This is the usual reason, and it catches nearly everyone.
If it genuinely is not there, the maintenance message is coming from somewhere else — a maintenance mode plugin, or your host's own maintenance page. Check your plugins list for anything like "Coming Soon" or "Maintenance Mode", and check your host's dashboard.
The site is back but something is broken
Deleting the file reveals whatever state the interrupted update left behind. Usually everything is fine. Occasionally you get a partially updated plugin.
Go to Dashboard → Updates and run the update again. A clean second attempt normally completes and resolves it.
If you now see a different error, the update left something in a bad state. Our guide to recovering from a broken update covers that — the short version is to deactivate or roll back the plugin that was updating.
If you see a white screen or a critical error, start here instead.
Why the update failed in the first place
Worth knowing, because it will happen again otherwise:
PHP memory limit too low. The most common cause. Add define( 'WP_MEMORY_LIMIT', '256M' ); to wp-config.php, and if that does not help, ask your host to raise the server limit.
The script timed out. Shared hosting often caps execution time at 30 seconds. A large plugin update can exceed it.
The connection dropped, or you navigated away mid-update.
Too many updates at once. Updating twenty plugins in one click is more likely to time out than doing them in batches.
Avoiding it
- Update in smaller batches — five or six at a time rather than everything
- Do not close the tab while an update runs
- Back up first, so an interrupted update is recoverable rather than alarming
- Fix the memory limit if this has happened more than once
That is most of the safe update routine — and if the idea of your site being stuck like this while you are not watching is the actual problem, that is what a care plan solves: updates applied and checked by someone whose job it is, with a rollback if anything goes wrong.