How to Fix WordPress Stuck in Maintenance Mode

To fix a WordPress site stuck in maintenance mode, first confirm that no update is running, then delete the .maintenance file from your WordPress root folder. Afterward, clear your caches and test the site while logged out.

WordPress maintenance mode usually clears automatically, but a failed update can leave its temporary notice behind. Start with the update status before removing anything, because an unfinished update needs attention too.

Key Takeaways

  • Don’t remove the maintenance file while an update is actively replacing files.
  • Use your hosting file manager or an FTP client to delete .maintenance, then investigate any failed update.
  • If the notice returns, check permissions, plugins, themes, custom maintenance settings, and cached pages.

First, Make Sure the Update Has Stopped

WordPress displays “Briefly unavailable for scheduled maintenance. Check back in a minute.” during short automatic tasks, including plugin updates. It isn’t a custom holding page for a redesign.

An interrupted update, server timeout, or software conflict can leave WordPress treating an update as incomplete. Closing or refreshing the update screen can also leave you unsure whether the server finished.

If your site is stuck in maintenance mode after an update, give it time. Look for completion messages in the update screen or ongoing activity in your hosting logs. Don’t launch another update over the first one.

The standard maintenance check normally stops applying after ten minutes. However, that timeout doesn’t prove every file updated successfully.

Removing the notice restores access; it doesn’t repair a plugin, theme, or core update that stopped halfway through.

Remove the .maintenance File Using FTP or File Manager

A technician's hands resting on a workbench beside network equipment and a checklist.

Once no update is running, save an available backup or hosting snapshot before making changes.

Find the correct WordPress folder

Open your hosting dashboard’s file manager, or connect using an FTP client such as FileZilla. Prefer SFTP when your host supports it.

Navigate to the folder containing wp-admin, wp-content, and wp-includes. It’s often public_html, but an addon domain or subdirectory installation can use another location.

Enable the option to show hidden files or dotfiles. Otherwise, .maintenance might be invisible.

Delete only the maintenance marker

Follow this sequence:

  1. Locate the file named exactly .maintenance, including the opening dot.
  2. Download a copy if you want a record of its contents.
  3. Delete that file without changing other WordPress files.
  4. Refresh your website and try opening /wp-admin/.

The WordPress troubleshooting FAQ identifies the base folder as the location WordPress uses for this automatic-update file.

If you have SSH access, run wp maintenance-mode status from the installation directory. Then use wp maintenance-mode deactivate once the update has stopped. The official maintenance-mode commands manage WordPress’s built-in marker, not an independent plugin’s maintenance setting.

If the Maintenance Notice Returns, Find the Cause

Repeatedly deleting the same file won’t solve whatever keeps recreating it. Note which update or action triggers the problem.

Check permissions and update errors

Read the failed update’s message and your hosting PHP error log. Messages such as “Permission denied” or “Could not copy file” point toward filesystem access problems.

Typical starting permissions are 755 for directories and 644 for files. However, ownership also matters, especially after a migration. Record existing permissions and correct affected items rather than changing the entire installation blindly.

Never use 777 as a shortcut. If ownership prevents WordPress from replacing files or removing its marker, ask your host to repair ownership.

Also investigate timeout or memory errors before retrying the failed update.

Isolate plugins, then test your theme

Start with the plugin updated immediately before the failure. Deactivate it through the dashboard, or rename its individual folder inside wp-content/plugins/ using SFTP.

Retry the failing action after each change. Our guide to finding WordPress plugin conflicts covers controlled testing without disabling unrelated features unnecessarily.

If plugins aren’t responsible, temporarily activate an installed default theme such as Twenty Twenty-Five.

A branded maintenance page may come from a plugin, page builder, or custom redirect. Turn off that feature separately. If your setup uses maintenance.html, remove its redirect rules before deleting the page, or visitors may reach a missing file.

Clear Caches and Verify the Site Works

After removing WordPress maintenance mode, purge your caching plugin, hosting cache, and CDN cache. Then clear your browser cache or open a private browsing window.

Test the homepage and an inner page while logged out. Next, log in to /wp-admin/ and repeat the operation that originally failed. For a store, also test the cart and checkout; for a lead-generation site, submit a contact form.

Use your browser’s developer tools to inspect the main document request under Network. A normal published page should return HTTP 200, not a 503 status code or a maintenance redirect. Check that it doesn’t return HTTP 503.

Finally, open Dashboard > Updates to see whether the interrupted update still needs attention. If recovery reveals a blank screen instead, follow our WordPress white screen troubleshooting steps.

Don’t treat a working homepage alone as proof of a complete recovery.

Choose a Maintenance Plugin for Planned Work

For scheduled downtime, use a maintenance page with a custom message that gives visitors more useful information than WordPress’s brief automatic notice.

Use a maintenance plugin

In the WP Maintenance Mode plugin interface, open Settings > WP Maintenance Mode > General, select Activated beside Status, and click Save settings. Reverse the status when your work is complete.

Plugin names and screens can change between releases. Maintenance Mode for WordPress by Robert DeVore is another free option. It uses the WordPress content editor and automatically returns HTTP 503.

The WebFactory Maintenance plugin’s 503 setting needs particular attention: enable its temporary-unavailability option rather than assuming the visual page sets the response correctly.

Configure access and page-builder settings

Maintenance plugins generally let logged-in administrators continue working, and many offer role-based bypass controls. Test the visitor experience in a private window because your administrator session may hide the maintenance screen.

With Elementor, open Elementor > Tools > Maintenance Mode. Choose Maintenance Mode or Coming Soon Mode, select your saved template, and click Save Changes.

Use maintenance mode for an existing live website. Coming soon mode and a coming soon page suit a website that hasn’t launched.

Manual Maintenance Methods Without a Plugin

Manual methods require file access and a clear way to reverse your changes. Back up before editing, and keep SFTP or your hosting file manager available.

Create a .maintenance file

Create .maintenance in the WordPress root with this single line:

<?php $upgrading = time();

Delete the file to bring the site back online. This invokes WordPress’s built-in maintenance handling, so don’t expect the administrator bypass controls offered by plugins.

With WP-CLI, you can instead run wp maintenance-mode activate, inspect it with wp maintenance-mode status, and finish with wp maintenance-mode deactivate.

Add a temporary functions.php snippet

Jetpack recommends backing up before editing functions.php. Back up the child theme’s functions.php file and save a separate copy before making changes. Add this to a child theme’s existing PHP code, without another opening PHP tag:

add_action( 'get_header', function () {
    if ( ! current_user_can( 'manage_options' ) ) {
        wp_die(
            'Under Maintenance',
            'Under Maintenance',
            array( 'response' => 503 )
        );
    }
} );

After testing, remove the snippet from the child theme’s functions.php. It covers requests reaching the theme’s get_header hook, so it isn’t a complete site-wide access restriction.

Use an Apache redirect cautiously

An Apache setup can use maintenance.html in public_html, with these rules before the existing WordPress rules:

RewriteEngine On
RewriteCond %{REQUEST_URI} !^/maintenance\.html$
RewriteRule ^ /maintenance.html [R=307,L]

This excludes the destination to prevent a redirect loop. However, 307 is a temporary redirect, not a 503 response. Prefer a properly configured 503 maintenance method for planned downtime. Remove these rules before deleting maintenance.html.

Prevent Another Stuck Update

A man in a workshop working on server equipment and tools at a wooden table.

Back up both files and the database before substantial updates. With WP-CLI, wp db export handles the database, but it doesn’t back up plugins, themes, or uploads. Keep exported databases outside publicly accessible folders.

Test major changes on a WordPress staging site, especially page-builder and ecommerce updates. Schedule production work during low-traffic hours and avoid starting overlapping updates.

Update likely problem components individually so you can identify which change fails. Keep the update screen open until completion, although browser activity alone doesn’t control every server-side operation.

For command-line maintenance, read each command’s output before continuing. After core updates, run any requested database upgrade. You can also use wp core verify-checksums to identify unexpected core-file differences.

Finish by clearing caches and testing the same important pages and actions every time.

WordPress Maintenance Mode FAQ

Will maintenance mode hurt SEO?

A maintenance page should return HTTP 503 Service Unavailable to signal temporary downtime to search engines and support correct SEO interpretation. In developer tools, inspect the main page request’s status while logged out.

A 503 isn’t indefinite ranking protection. Jetpack recommends limiting maintenance to a day or two and using staging for work that takes several hours or days. There’s no guaranteed risk-free cutoff.

What should your maintenance page include?

Give visitors an estimated return time and a useful contact route. Larger organizations can list departmental contacts.

For longer downtime, use a countdown timer to show the expected return time, and keep the countdown timer accurate. Add social media buttons or an email signup only if they’ll work during downtime.

Why is there no .maintenance file?

You might be viewing the wrong installation folder, hidden files may be concealed, or the page may come from another maintenance system. Review plugin and page-builder settings, custom redirects, and caches instead of creating a file to delete.

Restore Access, Then Finish the Recovery

Deleting a leftover .maintenance file usually restores access once an update has stopped. The next job is confirming that the update completed and your important site features still work.

Keep recovery and verification together. Fix the underlying failure, remove temporary changes, and test while logged out before considering the site ready for visitors.

Picture of Andy Feliciotti

Andy Feliciotti

Andy has been a full time WordPress developer for over 15 years. Through his years of experience has built 100s of sites and learned plenty of tricks along the way. Found this article helpful? Buy Me A Coffee

Leave a Reply

Your email address will not be published. Required fields are marked *

WordPress Tips Monthly
Get the latest from SmartWP to your inbox.