If your site is showing “Briefly unavailable for scheduled maintenance. Check back in a minute.” and that minute turned into an hour, you are dealing with WordPress stuck in maintenance mode — and the fix is almost always simpler than the frustration of the situation suggests. WordPress enters maintenance mode at the start of every core update, plugin update, and theme update. It places a hidden file in the root of the installation to signal that work is in progress and displays the maintenance message to all visitors. The problem is that WordPress relies on a successful update completion to remove that file, and when an update fails, times out, or gets interrupted, the file stays in place indefinitely. The site remains WordPress stuck in maintenance mode while the file exists, regardless of whether the update was actually still in progress. I have fixed this dozens of times, usually in under two minutes, and the most common situation is always the same: a failed or interrupted update, a file that needs deleting, and a site that is otherwise completely fine underneath the maintenance screen. For a broader walkthrough, our WordPress Errors Complete Guide is a good next read.
Why WordPress Gets Stuck in Maintenance Mode
Understanding why WordPress stuck in maintenance mode occurs makes the fix more intuitive. When WordPress starts an update process — whether triggered manually through the dashboard or automatically by the background updater — it creates a file named .maintenance in the WordPress root directory. The content of this file is simply a PHP array with the timestamp of when maintenance began. While this file exists, WordPress serves the maintenance message to every visitor and blocks admin access. When the update completes successfully, WordPress deletes the .maintenance file, and the site returns to normal. The entire process is supposed to take 30 seconds to two minutes.
WordPress stuck in maintenance mode occurs when something interrupts the update before WordPress can delete the .maintenance file at the end. The most common interruptions are: a PHP timeout during a large update package download, a browser tab being closed mid-update, a hosting-side connection interruption, a plugin conflict that causes a fatal error during the update process, or an update being manually interrupted because it appeared to hang. In every case, the update process stops, the .maintenance file is never removed, and the site stays in maintenance mode indefinitely.
The second cause of WordPress stuck in maintenance mode that many people miss is a plugin that intentionally enables maintenance mode — either a dedicated coming-soon or maintenance mode plugin, or a plugin with a built-in maintenance toggle — that was enabled and then forgotten about or whose disable function failed silently. In these cases, deleting the .maintenance file resolves the immediate symptom but the plugin re-enables it on the next page load. Identifying whether the maintenance mode is file-based or plugin-based is therefore the first diagnostic step, and the simplest test is whether maintenance mode returns within minutes of being cleared.
The Immediate Fix — Delete the .maintenance File
If WordPress stuck in maintenance mode appeared immediately after an update attempt, deleting the .maintenance file is almost certainly all you need to do. Here is the process:
- Open your FTP client (FileZilla is the most common; your hosting cPanel file manager also works) and connect to your server
- Navigate to the WordPress root directory — the same folder that contains
wp-login.php,wp-config.php, and thewp-contentfolder - Enable hidden file visibility. In FileZilla: Server menu → Force showing hidden files. In cPanel File Manager: Settings → Show Hidden Files. The
.maintenancefile starts with a dot, which makes it hidden on Linux servers by default. - Look for a file named
.maintenancein the root directory. It will be small — typically under 100 bytes — and will have a recent timestamp matching the time the update was attempted - Delete the file
- Reload your website in a browser (using Ctrl+Shift+R or Cmd+Shift+R to bypass any browser cache)
In the vast majority of WordPress stuck in maintenance mode cases, that is the entire fix. The site returns to normal the moment the file is deleted. If the maintenance screen returns within a minute of deletion, a plugin is re-creating the file and you need the plugin-specific fix covered below rather than the file deletion approach.
After the site is back online, confirm the status of the update that was running when maintenance mode got stuck. Log in to the WordPress dashboard, go to Dashboard → Updates, and check whether all plugins, themes, and core are showing as current. If the interrupted update shows as incomplete, run it again — the WordPress stuck in maintenance mode fix does not affect the underlying files that the update was modifying, so a re-run completes from scratch safely.
When the Dashboard Is Locked and You Cannot Access WordPress Admin
One of the more disorienting aspects of WordPress stuck in maintenance mode is that it sometimes blocks the WordPress admin as well as the front end. The same maintenance message appears at /wp-admin/, leaving you without a way to check the update status or deactivate plugins through the normal interface. This is exactly the scenario where FTP or the hosting file manager becomes the only path forward.
The FTP approach described above works regardless of whether the admin is accessible — you are working with the file system directly rather than through WordPress. Once the .maintenance file is deleted, the admin panel becomes accessible again along with the front end. If your hosting plan does not include FTP access (unusual but possible with some managed hosts), the hosting control panel’s built-in file manager achieves the same result without an external FTP client. Log in to your hosting dashboard, navigate to the file manager, find the WordPress root directory, enable hidden files, and delete the .maintenance file exactly as you would through FTP.
Some managed WordPress hosts — Kinsta, WP Engine, Cloudways — provide a dashboard interface for directly managing the file system without FTP or cPanel. If your host offers this, it is often the fastest route to resolving WordPress stuck in maintenance mode because you do not need to configure a separate FTP client. The file system view in these dashboards typically shows hidden files by default, making the .maintenance file immediately visible when you navigate to the WordPress root.
When a Plugin Is Causing WordPress to Stay in Maintenance Mode
Plugin-caused WordPress stuck in maintenance mode is more persistent than update-caused maintenance mode because deleting the .maintenance file provides only temporary relief — the plugin recreates it on the next request. The most common plugin types that cause this are coming-soon page plugins, maintenance mode plugins, and some landing page builders that include a built-in maintenance toggle.
If the maintenance screen returns within seconds of you deleting the .maintenance file, a plugin is responsible. The fastest diagnostic step is to deactivate all plugins via FTP — rename wp-content/plugins/ to wp-content/plugins_off/ — and then reload the site. If the maintenance screen does not return after the bulk deactivation, rename the folder back to plugins/ and reactivate plugins one at a time until the WordPress stuck in maintenance mode recurs. The plugin whose activation causes maintenance mode to return is the culprit.
Within the offending plugin’s settings, look for any maintenance mode, coming soon, or under construction toggle. These settings are typically in the plugin’s dedicated settings page in the WordPress admin. Disabling the maintenance mode toggle in the plugin’s own settings is the correct fix — simply deactivating the plugin removes the symptom but leaves the setting in place, so the next activation re-enables maintenance mode. If the plugin does not have a maintenance mode toggle but is still causing WordPress stuck in maintenance mode, it likely has a bug and should be reported to its developer or replaced with an alternative.
Failed Updates and Incomplete WordPress Installations
When WordPress stuck in maintenance mode followed an update that clearly failed — not just timed out but produced an error message before timing out — there is an additional consideration beyond deleting the maintenance file. The update may have started replacing files before failing, leaving the installation in a partially updated state. Deleting the .maintenance file restores site access, but the underlying WordPress installation may have some files from the new version and some from the old version.
The safest resolution in this scenario is a manual update immediately after clearing the WordPress stuck in maintenance mode situation. Download the correct version of WordPress from wordpress.org, extract it, and upload the wp-admin and wp-includes folders over the existing ones via FTP. This ensures every file in the WordPress core is from the same clean version, eliminating any half-updated state that the failed update left behind. Do not skip this step just because the site appears functional after deleting the maintenance file — a partially updated installation can behave normally for weeks before a subtle incompatibility surfaces.
For plugin and theme updates that left the site in a mixed state after causing WordPress stuck in maintenance mode, deactivate the plugin or theme whose update failed, download a fresh copy from its source, and reinstall it cleanly. The fresh installation overwrites whatever partial update was applied and restores the plugin or theme to a consistent state. Attempting to run the update again through the WordPress dashboard is the alternative — WordPress downloads the complete package fresh on each update attempt, so a re-run effectively does the same thing as a manual reinstallation in most cases.
Preventing WordPress From Getting Stuck in Maintenance Mode
The most reliable prevention for WordPress stuck in maintenance mode is maintaining a reliable update environment rather than trying to prevent updates from ever failing. Realistic prevention focuses on the conditions that cause update failures rather than on suppressing the maintenance mode mechanism itself.
A stable, fast connection to WordPress.org update servers is the starting point. Sites on shared hosting plans with very low outbound bandwidth or with firewalls that intermittently block WordPress.org connections are disproportionately affected by update timeouts that lead to WordPress stuck in maintenance mode. Running updates during low-traffic periods reduces the server load competing with the update process and decreases the likelihood of a timeout. Always taking a backup before running updates — particularly major WordPress version updates — means that even a failed update that leaves the installation in a mixed state can be recovered to a clean starting point without data loss, which removes much of the risk associated with the WordPress stuck in maintenance mode situation.
Our guide on fixing the WordPress automatic update failed error covers the update process in more depth, including how to verify update completion and how to manually complete updates that WordPress could not finish automatically after clearing WordPress stuck in maintenance mode. Our guide on how to safely update WordPress covers the pre-update backup routine and the manual update steps that avoid relying on the automatic updater for situations where repeated maintenance mode failures suggest the automatic process is not reliable on your hosting environment. The WordPress documentation covers the maintenance mode behaviour in the update process documentation and lists the specific conditions under which the maintenance file is created and removed. If this sounds familiar, How to Fix WordPress Stuck in Maintenance Mode Safely With Proven Steps is worth a look.
