WordPress stuck in maintenance mode? Start here
If your WordPress site is stuck in maintenance mode, visitors usually see one plain message: “Briefly unavailable for scheduled maintenance. Check back in a minute.” WordPress displays it while core, a plugin, or a theme is updating. The page should disappear when the update finishes.
Give the update a few minutes before changing anything. Open the site in a private browser window or on your phone to rule out a cached page. If the same message remains and no update is still running, WordPress probably left a temporary .maintenance file in the site’s main directory.
The immediate fix is often simple: remove that file. However, the interrupted update still needs attention. Bringing the website back does not prove that every file finished installing or that forms, checkout, and other important features still work.
The quick, safe recovery order
- Wait a few minutes and confirm that the message is not temporary.
- Check the site from a private browser window or another connection.
- Make sure nobody is still running an update.
- Open the WordPress installation through your host’s file manager or SFTP.
- Show hidden files and locate
.maintenancebesidewp-config.php. - Delete the
.maintenancefile, then reload the public site and/wp-admin/. - Identify the failed update and verify the site before trying it again.
WordPress documents this same recovery step in its official updating WordPress guide. Its core update process creates .maintenance while files are copied and removes it when the process completes. A timeout or other failure can stop the process before cleanup, as the WordPress core update reference explains.
First, make sure the update is really stuck
A short maintenance message during an update is normal. Do not delete the file the moment you see it. Interrupting an active update can create the partial-file problem you are trying to avoid.
Check whether another administrator, developer, host, or automated maintenance service started an update. Look for a recent WordPress auto-update email. If you still have wp-admin access in another tab, let the current process finish.
Then test the public URL without relying on the same cached browser tab. Add a harmless query such as ?check=1, use a private window, or try mobile data. If only one browser shows the maintenance page, clear that browser’s cache before touching server files.
How to remove the .maintenance file
You need access to the files for the affected WordPress installation. Most hosting accounts provide a file manager. SFTP also works. The correct folder is the one that contains wp-admin, wp-content, wp-includes, and wp-config.php.
- Sign in to your hosting control panel or connect through SFTP.
- Open the document root for the affected domain.
- Enable “show hidden files” or “show dotfiles.”
- Find the file named exactly
.maintenance. - Confirm that no update is currently running, then delete only that file.
- Reload the homepage and
/wp-admin/.
The leading dot makes the file hidden in many file managers. If you cannot see it, check the file manager settings before deciding that it is missing. Also confirm that you opened the correct domain folder; hosting accounts often contain several WordPress installations.
Do not delete wp-config.php, plugin folders, the uploads directory, or unfamiliar server files to “clear maintenance mode.” If you are unsure which directory is live, stop and ask the host or a WordPress professional to confirm it.
WordPress stuck in maintenance mode but no .maintenance file?
The page may come from a different layer. A maintenance or coming-soon plugin can show its own screen. Your host or deployment system may also place the site behind a maintenance page. Finally, a full-page cache or CDN can continue serving an old response after WordPress has recovered.
| What you see | Likely source | Next check |
|---|---|---|
| The exact plain WordPress maintenance sentence | Interrupted WordPress update | Look for .maintenance in the WordPress root |
| A branded or designed maintenance page | Maintenance plugin, theme, host, or deployment tool | Check that tool’s setting and recent changes |
| The site works with a query string but not normally | Stale page or CDN cache | Purge the relevant cache and retest |
| A critical error, blank page, 500, or broken layout | The failed update left another problem | Move to error diagnosis and rollback |
If the message disappears but the site now shows a different error, do not keep deleting files. Use the recovery order in our guide to a WordPress critical error after a plugin update.
Check what failed before updating again
After wp-admin opens, go to Dashboard > Updates and the Plugins or Themes screen. Look for the component that still shows an update, a failure notice, or an unexpected version. Review the update email and any error log available in the hosting panel.
Do not immediately click “update all” again. First create or confirm a current backup. Record the installed and available versions. If the failed component controls payments, forms, bookings, memberships, security, caching, or the page builder, treat it as a higher-risk change.
Re-run one update at a time so you can identify the component that fails. A complex business website should test the update on staging when the failure could interrupt revenue or customer access. Our WordPress staging workflow explains how to keep that test meaningful.
Verify the site after it comes back
A working homepage is only the first check. An interrupted update can leave one feature broken while the rest of the website looks normal.
- Open the homepage, main service or product pages, and contact page.
- Test wp-admin and the editor for an important page.
- Submit the primary contact or quote form and confirm delivery.
- For WooCommerce, test product, cart, checkout, account, and order email flows safely.
- Check mobile navigation, popups, consent controls, search, and login.
- Review PHP and server logs for new fatal errors or repeated update failures.
- Clear the correct caches, then test a normal URL and a cache-busting URL.
If core was updating, WordPress may ask you to complete a database upgrade after you log in. Follow the official prompt, then check the public site again. If a plugin or theme update failed, compare its current files and version with the vendor’s clean release before returning the site to normal operation.
Why WordPress gets stuck in maintenance mode
The leftover file is the visible cause, but it is not always the root cause. Common triggers include a PHP timeout, low memory, low disk space, incorrect file ownership, a slow connection to an update server, a server process ending early, or a plugin package that could not be unpacked or copied.
Bulk updates increase the number of moving parts. They also make it harder to tell which component failed. A recurring problem deserves investigation rather than repeated deletion of .maintenance.
WordPress recommends keeping plugins and themes current and maintaining reliable backups before enabling auto-updates. Its plugin and theme auto-update guidance also notes that update scheduling depends on WordPress Cron and that failed attempts can generate administrator emails.
How to stop the problem from returning
- Keep enough free disk space for download, extraction, and rollback files.
- Run high-risk updates in a quiet window with a current off-site backup.
- Update business-critical components separately instead of using one large batch.
- Review PHP limits, server errors, and file permissions after a repeated failure.
- Use staging for large core, builder, commerce, membership, or custom-code changes.
- Monitor the public site and important user journeys after every update.
- Keep a record of changed versions, test results, and any rollback.
A repeatable monthly WordPress maintenance process should prove that backups work, updates complete, and the website’s important actions still function. The update button is only one part of that process.
When to ask for WordPress help
Professional help is appropriate when you cannot access the correct server files, the site changes from maintenance mode to a critical error, the failed update controls sales or lead delivery, or the same problem returns. It is also safer to escalate when you have no recent backup or cannot confirm whether an update was still running.
Before handing the problem over, note when the message appeared, which update was running, what you already changed, and whether the public site or wp-admin is reachable. Preserve update emails and error logs. That short record saves diagnostic time and reduces guesswork.
Webless provides WordPress maintenance services for business owners who want updates handled with backups, controlled testing, monitoring, and clear verification. We can remove the immediate maintenance lock, find why the update stopped, recover the affected component, and test the lead or sales paths that the website needs to protect.
Bring the site back, then prove it works
When WordPress is stuck in maintenance mode, deleting the leftover .maintenance file usually restores access. Take that step only after confirming that the update has stopped. Then identify the failed component, verify its version and files, and test the website as a customer would.
The visible message is often easy to remove. The valuable work is making sure the interrupted update did not leave a quieter problem behind.