Is your WordPress website showing a maintenance message instead of your pages? A stalled update may be responsible. Here’s how to check what’s happening, remove a leftover maintenance file when appropriate, and make sure your website is working before you move on.
Why is WordPress stuck in maintenance mode?
WordPress temporarily puts your site into maintenance mode during certain updates. Visitors may see “Briefly unavailable for scheduled maintenance. Check back in a minute.” Normally, the message disappears when the update finishes.
If an update is interrupted, a file named .maintenance can remain in the WordPress installation folder. Removing that leftover file can clear the update-related message, but first confirm that an update is no longer running.
A branded “coming soon” page can have a different cause: a maintenance plugin, a site-building tool, or a setting in your hosting account. Identify which kind of screen you’re seeing before changing files.
Check these things before making changes
- Look for an active update. Check the original update screen and your host’s update activity, if available. Let an active update finish. If you cannot tell whether it is still running, ask your host to check.
- Confirm you have a recovery option. Locate your latest backup of both the files and database. Before further changes, ask your host for a current snapshot if needed; keep any backup from before the failed update too.
- Record what happened. Note which plugin, theme, or WordPress update was running and save any error message.
For a broader approach to diagnosing problems, read our guide to troubleshooting WordPress safely.
How to clear a leftover WordPress maintenance file
1. Open your website’s files
Use your hosting account’s file manager or an SFTP connection. These let you access the files even when the WordPress dashboard is unavailable. If you manage several websites, confirm you have selected the affected site.
2. Find the WordPress installation folder
Look for the folder containing wp-admin, wp-content, and wp-includes. Its name and location depend on your hosting setup; do not assume it is always public_html.
Find the file named exactly .maintenance, including the leading dot. Enable “show hidden files” in your file manager or SFTP application if needed.
3. Remove only the leftover .maintenance file
Once you have confirmed the update has stopped, delete the .maintenance file from that folder. Leave the other WordPress files and folders alone. This is the file-removal remedy described in WordPress’s troubleshooting documentation.
If you cannot find the file, do not create one or start deleting other files. Continue with the checks below.
4. Reload the site and check the update
Open your website in a private browser window, then try the WordPress dashboard. If the site loads, review Dashboard → Updates and the relevant plugin or theme’s installed version. An accessible homepage does not prove the update completed.
If an update failed, review its error before retrying. After resolving the cause and confirming your backup, retry the affected update on its own. If it fails again, stop and ask your host or developer to investigate.
What if the maintenance message stays?
WordPress’s standard maintenance check normally stops treating an update as active once the timestamp stored in the file is ten minutes old. This is a behavior of the WordPress maintenance check, not a guarantee that an update has finished. A persistent message needs a closer look.
- Check caching. Once maintenance has ended at the source, clear the relevant website, hosting, or CDN cache. A CDN is a service that delivers cached copies of your pages. Ask your host if you are unsure which cache is involved.
- Check maintenance or coming-soon settings. If you see a custom page, check the tool or hosting setting that enabled it. Turn it off only when the planned work is complete.
- Confirm the installation folder. A hosting account can contain multiple sites or a staging copy. Your host can identify the correct folder.
- Watch for a recurring update. If the file keeps returning, ask your host to inspect update activity and error logs rather than repeatedly deleting it.
If the maintenance screen changes to a different error, follow the symptoms you now see. Our guides cover the WordPress white screen of death and 500 internal server errors.
Check the parts of your website that matter
Before considering the problem resolved, test more than the homepage. Choose checks that match how visitors use your site:
- Open important service pages and check navigation on mobile.
- Submit a test inquiry and confirm it reaches the right inbox.
- Check login and account access where applicable.
- For stores or donation sites, use your established test process to check the purchase or donation journey without unintentionally charging a customer.
Reduce the chance of another interrupted update
Use a repeatable update routine: keep recoverable backups, test significant changes on a staging copy, schedule work when disruption will be lower, and check the site afterward. Avoid starting overlapping updates from different tools.
For guidance on planning that routine, see how often to update WordPress, themes, and plugins. If you would rather have ongoing help, explore GRIDD’s WordPress maintenance and support.
Frequently asked questions
Will deleting .maintenance delete my website content?
The file is an update-related marker, not the database holding your posts or pages. Removing that specific file does not delete your content. It also does not repair an incomplete update, which is why the checks afterward matter.
Can I fix this without signing in to WordPress?
Yes. Your hosting file manager or SFTP can provide access to the installation folder. If you do not have those credentials, contact your host or the person who manages your website.
Should I restore a backup immediately?
First identify the problem. A leftover maintenance file alone may not require a full restore. If an update damaged the site, discuss recovery with your host or developer. Restoring an older database can remove newer orders, inquiries, or content, so plan how to preserve recent activity.
Need help getting your website working again?
If the update keeps failing or you are unsure which files to change, explore GRIDD’s one-time WordPress fixes. Share the maintenance message, the update you were running, and what you have already tried so we can understand the problem.
You can also browse our WordPress troubleshooting and fixes resources for related guides.