Table of contents14
If WordPress is stuck in maintenance mode, your content is usually still safe. Wait a few minutes for any update to finish, then look for the small file called .maintenance in your site root folder and remove it only after you are sure no update is still running. In most cases the site returns at once. This guide shows you how to check safely, fix it without losing work, and stop it happening again.
What this guide will help you achieve
- Get your site back without deleting posts, pages or settings
- Find out why maintenance mode stuck, instead of guessing
- Fix it through your hosting file manager or by file transfer
- Check the site properly after it returns
- Stop the same problem happening at the next update
- Know when a backup restore is the safer answer
Get your site back without losing work
Maintenance mode is a normal part of WordPress updates. When you update WordPress itself, a theme or a plugin, WordPress briefly puts up a short message saying the site is briefly unavailable for scheduled maintenance. Visitors see that message instead of a half-updated site. When the update finishes, WordPress removes the message and the site returns to normal. The problem in this guide is different: the message stays, long after any update should have finished, and you cannot reach your dashboard or your public pages.
Start with the least risky checks. First, wait a few minutes and reload the site in a private or incognito window. Updates can take longer on a slow connection or a busy server, and a cached maintenance page can make a recovered site look stuck. If the message is still there after a few minutes, try your dashboard address directly. If the dashboard also shows the maintenance message, the site is still in maintenance mode, not just showing an old cached page.
Do not start by reinstalling WordPress, deleting plugins or restoring a backup. Those steps can create a second problem on top of the first. The usual cause is a single file that was not removed when an update was interrupted. Finding and removing that file, in the right order, is the fix for most stuck sites. If you are unsure whether an update is still running, wait longer and check with your host before you change anything. A few extra minutes of patience is safer than interrupting an update that is still writing files.
Find out why it stuck
WordPress creates a file called .maintenance in the root folder of your site at the start of an update and deletes it at the end. The dot at the start of the name means the file is hidden in many file managers, so you may need to show hidden files to see it. If the update is interrupted, that file can be left behind. The site then keeps showing the maintenance message because WordPress still thinks an update is in progress. Other causes are less common but worth knowing, because they change what you should do next.
| Situation | What you will see | First safe fix | Risk if you rush |
|---|---|---|---|
| Update interrupted by a closed browser tab or lost connection | Maintenance message on every page, update may be half done | Wait, then check for the .maintenance file | Removing the file while files are half updated can leave a broken feature |
| Server timeout during a large update | Maintenance message, update may not have finished | Check with your host whether the update process is still running | Starting the update again too soon can overwrite files twice |
| Theme or plugin update conflict | Maintenance message, then an error or blank page after removal | Remove the .maintenance file, then check the site and recent updates | Deleting the wrong plugin can remove settings or content you need |
| File permissions problem | Maintenance file remains even though the update finished | Remove the file through your hosting file manager | Changing many permissions at once can lock you out of files |
| Maintenance mode switched on by a tool or setting | Maintenance page with a custom message, dashboard may still work | Switch the setting off in the tool or dashboard | Deleting files will not help if a setting is the real cause |
Ask yourself what changed just before the problem appeared. Did you start an update and close the tab? Did an update run automatically overnight? Did you change a theme or plugin? The answer points to the most likely cause and helps you decide whether a simple file removal is enough or whether you need to check recent updates more carefully after the site returns.
Fix it through your hosting file manager
Most site owners can do this fix without special software. Your hosting account usually includes a file manager that shows the files of your site in a browser. The exact labels differ between hosts, but the steps are the same in principle. Work slowly, and do not delete anything except the file named in this section unless you are sure what it is.
- Sign in to your hosting account and open its file manager.
- Open the root folder of your WordPress site, usually the folder that contains wp-admin, wp-content and wp-includes.
- Turn on the option to show hidden files, if your file manager hides files that start with a dot.
- Look for a file named exactly .maintenance, with no other name before the dot.
- Before you delete it, check its time. A very recent time can mean an update is still running, in which case wait and check again.
- If no update is running, delete only the .maintenance file.
- Reload your site in a private window and check both the homepage and the dashboard.
If the site returns, do not stop there. Visit a few key pages, check that recent posts and pages are present, and look at any plugin or theme that was updating when the problem started. If a plugin or theme looks half updated, update it again from the dashboard, one item at a time, and check the site after each one. Updating everything at once after a stuck update makes it harder to know which item caused trouble if something breaks again.
Fix it when you cannot reach the file manager
If your hosting account does not offer a file manager, or you cannot sign in to it, file transfer is the other common route. You will need the file transfer details from your hosting account. Those details are sensitive, so keep them private and do not share them in comments or support forums. Connect to your site, open the same root folder described above, show hidden files in your file transfer program, and remove only the .maintenance file. Then disconnect and test the site in a private window.
If you do not have file transfer details and you cannot reach your hosting file manager, contact your host. Explain that the site is stuck in maintenance mode, that you believe the .maintenance file was left behind after an interrupted update, and ask them to check whether any update process is still running before the file is removed. That wording helps support staff help you quickly, because it names the likely cause and the safety check that matters.
If the site does not return after the file is removed, do not keep deleting files. A white screen, an error message or a missing page after removal usually means the interrupted update left something else unfinished. Note the exact message you see, including any file or line it mentions, and work through the checks in the next section before you try another fix. A clear note of the message will also help anyone you ask for help.
Check the site properly after it returns
A site that loads again is not automatically a site that is fully fixed. An interrupted update can leave one feature broken while the homepage looks fine. Use this checklist before you tell visitors or clients that everything is back to normal.
- Homepage, one post, one page and your contact or enquiry form all load
- Dashboard opens and you can save a test change, then undo it
- Recent posts, pages, images and comments are present
- Menus, search and any shop or booking pages work as expected
- The plugin or theme that was updating is up to date or can be updated cleanly
- No new error messages appear in the dashboard
- A backup was taken after the site returned, before further changes
If a page or feature is still broken, think about what was updating when the problem started. Reinstalling or updating that one item, from a trusted source, is often safer than changing many things at once. If you need to restore a single file, the guide on how to restore a single file from a backup explains a careful way to do it without restoring the whole site. If the whole site feels unstable, a backup may be the safer answer, as explained below.
Stop it happening again
You cannot prevent every interrupted update, but you can make the next one much less risky. Update one item at a time when you can, and do not close the browser tab while an update is running. Avoid starting updates when your connection is unstable or when you need to leave the computer in the middle of the process. If your host offers a staging copy of your site, test larger updates there first, especially theme changes and updates that affect many parts of the site.
Backups are the safety net that turns a stuck update from a crisis into an inconvenience. Follow the 3-2-1 backup strategy, and test your backups with restore drills before you need them in an emergency. Keep at least one copy away from your own server, as explained in the guide on why to stop storing backups on your own server. If a backup fails, do not ignore the warning, because a failed backup will not help when you need it. The guide on backup failure causes and fixes works through the common reasons in order.
Good general site care also helps. Keeping WordPress, themes and plugins up to date in small, regular steps is usually safer than leaving many updates until they must all be done at once. The guides on security best practices and speed optimisation explain related habits that keep a site easier to maintain. If your site is slow during updates, page caching explained can help you understand what caching does and does not do during an update, so you do not mistake a cached page for a recovered site.
When a backup is the right answer
Removing the .maintenance file is right when the update itself was sound and only the cleanup step failed. A backup restore is the safer answer when the site returns but key features are broken, when an update clearly corrupted files, or when you cannot tell what was changed during the interrupted update. In those cases, restoring from a known good backup can be quicker and cleaner than trying to repair file by file, especially if you have tested that backup before.
Before you restore, note what has changed since the backup was taken, because a restore can undo recent posts, orders or settings. If the damage looks like a security problem rather than a failed update, read the hacked site recovery guide before you restore, because restoring over a compromised site without closing the entry point can bring the problem back. If a block or page still shows an error after the site returns, the guide on how to fix block validation failed errors explains that separate problem, which has different causes and fixes.
Frequently asked questions
Is my content lost if the site is stuck in maintenance mode?
Usually not. Maintenance mode is a temporary message, not a deletion. Your posts, pages and media normally remain in the database and media library. The risk comes from interrupting an update or deleting the wrong files, which is why this guide starts with waiting and checking before you change anything.
Can I just wait for maintenance mode to clear on its own?
Sometimes, yes, if an update is still running. If the message is still there after a few minutes, and especially after an hour, it is unlikely to clear on its own, because the file that causes it is usually left behind by an interrupted process. At that point, checking for the .maintenance file is the next step.
What if the .maintenance file keeps coming back?
If the file returns, an update is probably starting again, or a tool is putting the site into maintenance mode on purpose. Check whether an automatic update is running, and check any maintenance setting in your dashboard or hosting tools. Do not keep deleting the file while an update is actively running.
Do visitors see the same message I see?
Visitors normally see the short maintenance message, while logged-in administrators may sometimes see the site normally. That difference can be confusing. Test in a private window, where you are not logged in, to see what a visitor sees.
Should I restore a backup straight away?
Not usually as a first step. Try the file check first, because it is quicker and does not undo recent changes. Restore a backup if the site returns but is unstable, if files were corrupted, or if you cannot tell what the interrupted update changed. Always use a backup you have tested if you can.
Tell me in the comments what caused your stuck maintenance screen, and which fix worked for you. I read every comment, and your experience may help the next person who lands here with the same message on their screen.
