Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix Briefly Unavailable for Scheduled Maintenance

Short answer

Delete the .maintenance file from your WordPress root folder, then re-run the interrupted update from Dashboard > Updates. WordPress creates that file during every update and deletes it when the update ends, so a file left behind after a failed update keeps the “Briefly unavailable for scheduled maintenance” message on screen. If the message lasts past 10 minutes, check for a plugin maintenance page or a cached copy.

Key takeaways

  • WordPress creates a .maintenance file during every core, plugin or theme update and deletes it when the update finishes.
  • If the update stops part-way, the leftover file keeps the maintenance message on screen with a 503 status.
  • WordPress ignores a .maintenance timestamp older than 10 minutes, so a message that lasts longer has another cause.
  • Delete the file from the WordPress root folder with a file manager, FTP, or the WP-CLI command wp maintenance-mode deactivate.
  • After the file is gone, open Dashboard > Updates and run the interrupted update again so nothing stays half-installed.
  • Clear every cache layer after the fix, or a stored copy of the maintenance page can keep showing.

What does “Briefly unavailable for scheduled maintenance” mean?

The message means WordPress is updating core, a plugin or a theme and has locked the site until the files finish changing.

WordPress.org's Updating WordPress guide says the site enters maintenance mode during an update and the message is normal for a short time. Once the update ends, WordPress removes maintenance mode on its own and the site comes back. Updating WordPress

Behind the message, WordPress sends an HTTP 503 status with a Retry-After: 600 header. The 600 stands for 600 seconds, or 10 minutes, and it tells browsers and search engines to try again later.

The WordPress developer reference for wp_is_maintenance_mode() documents the 10-minute check behind this behavior. wp_is_maintenance_mode()

The message is plain by design. WordPress.org's Updating WordPress guide says you can replace it with your own page by adding a maintenance.php file to the wp-content folder.

Why does WordPress get stuck in maintenance mode?

An update that stops part-way leaves the .maintenance file behind, so the lock never clears.

WordPress creates that file in the site root before it replaces files and deletes it when the update ends. The file sits beside wp-config.php and holds one line of PHP with the update start time in a variable called $upgrading. How to Fix WordPress Stuck in Maintenance Mode

Kinsta lists three common triggers: a closed browser tab during an update, too many plugins updated at once, and a compatibility problem.

CauseWhy it stops the updateWhat to do
Closed browser tab or dropped connectionThe update process ends before cleanup runsDelete the file, then re-run the update
Too many updates at onceA bulk update can hit a PHP time or memory limitUpdate items one at a time
File permission problemWordPress cannot delete the file it createdAsk the host to fix ownership or permissions
Plugin or theme conflictA compatibility problem breaks the updaterUpdate the problem item alone after the fix

SiteGround adds low memory to the same list, and notes that the file normally deletes itself once the update ends. When any of these stops the process, the cleanup step never runs. How to Fix the Error Briefly Unavailable for Scheduled Maintenance

Should you wait before you fix it?

Wait 2 to 3 minutes if an update started moments ago, because a live update clears the message on its own.

WordPress ignores a .maintenance file once its timestamp is 10 minutes old. The WordPress developer reference for wp_is_maintenance_mode() states that a timestamp older than 10 minutes counts as maintenance over, even if the file is still on disk. wp_is_maintenance_mode()

So a message that lasts well past 10 minutes has another cause. Either a new update is rewriting the file, a plugin is showing its own maintenance page, or a cache is serving a stored copy of the message.

Do not start a second update while you wait. WordPress.org's Updating WordPress guide says to keep the page open until the update finishes, and a second update can collide with the first.

How do you delete the .maintenance file with a file manager?

Delete the .maintenance file from your WordPress root folder with your host's file manager.

  1. Log in to your hosting account and open File Manager.
  2. Open the WordPress root folder, usually public_html, where wp-config.php sits.
  3. Turn on the option to show hidden files, because names that start with a dot stay hidden.
  4. Select .maintenance and choose Delete, then confirm.
  5. Reload your site in a private browser window.

SiteGround's guide gives the same path for its own panel: Client Area, then Websites, then Site Tools, then Site, then File Manager, then public_html. The file name is .maintenance, with a leading dot and no other text. How to Fix the Error Briefly Unavailable for Scheduled Maintenance

How do you fix it with FTP or SFTP?

Use FTP or SFTP when your host has no file manager, or when you already have an FTP client set up.

  1. Connect with the SFTP details from your hosting account.
  2. Go to the WordPress root folder, the one that holds wp-config.php.
  3. Turn on hidden files in your FTP client.
  4. Right-click .maintenance and delete it.

Kinsta recommends this method in its own fix guide and says the site should work normally once the file is gone. Kinsta also recommends clearing the site cache after deleting the file. How to Fix WordPress Stuck in Maintenance Mode

How do you fix it with WP-CLI?

Run one WP-CLI command from the WordPress root to switch maintenance mode off.

wp maintenance-mode status
wp maintenance-mode deactivate

The WordPress developer reference for wp maintenance-mode deactivate shows the expected reply: “Disabling Maintenance mode...” followed by “Success: Deactivated Maintenance mode.” wp maintenance-mode deactivate

WP Engine notes that its User Portal toggle uses WP-CLI and switches off on its own after 10 minutes. That 10-minute limit is default WordPress core behavior, so a longer planned outage needs a maintenance plugin instead. Enable Maintenance Mode

Use WP-CLI only if your host gives you SSH access. If you have no terminal access, use the file manager method above instead.

What should you do after the message is gone?

Re-run the interrupted update, because deleting the file restores access but does not finish the update.

  1. Open Dashboard, then Updates.
  2. Look for the item that failed and run its update on its own.
  3. Check the site front page and a few key pages.
  4. Clear every cache layer, including any CDN cache.

WordPress.org's Updating WordPress guide says to check Dashboard, then Updates for remaining plugin and theme updates after a core update, and to visit the site afterward. If the core update failed, the Dashboard Updates screen says to delete the .maintenance file and run the upgrade again. Updating WordPress

If the update broke files instead of only stalling, restore from a backup. Our guide to restoring a backup with UpdraftPlus walks through the restore steps.

How do you check the fix worked?

Open the home page and wp-admin in a private browser window and confirm both load normally.

  • Home page loads with no maintenance message.
  • Dashboard opens at /wp-admin.
  • Dashboard, then Updates shows no failed update still waiting.
  • A post and a page load, including images.

If the old message still shows, clear the cache. Kinsta recommends clearing the site cache after the fix, and WP Engine says a cached maintenance page can linger after deactivation until the server cache is cleared. Enable Maintenance Mode

A 503 error that stays after the file is gone is a different problem. Our guide to fixing the 503 Service Unavailable error covers the other causes.

What if the message keeps coming back?

A message that returns means something is recreating the file, running its own maintenance page, or serving a cached copy.

First, check for a maintenance or coming-soon plugin that is still switched on. WP Engine notes that its portal toggle does not switch off a plugin maintenance page, so turn that mode off inside the plugin settings. Enable Maintenance Mode

Next, look for a maintenance.php file in wp-content. WordPress.org's Updating WordPress guide says WordPress loads that file instead of the default message while maintenance mode is active, so a leftover drop-in can keep showing a maintenance page.

WordPress.org's Updating WordPress guide says minor and security updates have applied automatically in the background since WordPress 3.7, as of November 2026, so a retry can write a fresh file while you check the old one.

SiteGround lists 755 for directories and 644 for files as the recommended permissions, as of November 2026. Wrong permissions can stop WordPress deleting the file. How to Fix the Error Briefly Unavailable for Scheduled Maintenance

If a new error appears instead of the maintenance message, find its cause before you update again. A 500 error after a failed update is common, and our guide to fixing the 500 Internal Server Error explains the next steps.

When should you contact your host?

Contact your host when you cannot reach your files, the file keeps returning, or the site shows a new error after the fix.

  • You have no file manager, FTP or SSH access.
  • The .maintenance file returns within minutes of deletion.
  • File permissions stop you deleting the file.
  • The site shows a database or 500 error after the fix.
  • The disk is full or PHP limits keep stopping updates.

Your host can delete the file for you, check the server error log and raise a PHP time or memory limit. WordPress.org's Updating WordPress guide also notes that one-click update failures are often tied to filesystem permissions, which the host controls.

Ask the host to confirm the update finished cleanly. A short PHP time limit can also stop large updates, and our guide to updating the PHP version in WordPress explains where that setting lives.

What mistakes should you avoid?

Avoid these mistakes, because each one turns a 2-minute fix into a longer outage.

  • Deleting wp-config.php or other files instead of only .maintenance.
  • Starting a second update while the first is still running.
  • Deleting maintenance.php in wp-content and expecting it to clear core maintenance mode; it is a custom page, not the flag file.
  • Restoring a full backup before checking for the file; the file check takes 2 minutes and a restore takes far longer.
  • Updating every plugin at once after the fix instead of one at a time.

Back up before every update, not after a failure. If you are unsure which backup route fits your site, our comparison of cPanel backups and plugin backups lays out the trade-offs.

Frequently asked questions

How long does WordPress maintenance mode normally last?

Only a few seconds to a few minutes. WordPress creates the .maintenance file when an update starts and deletes it when the update ends. WordPress also ignores a timestamp older than 10 minutes, so a message that stays on screen far longer than that means the update failed, a plugin page is active, or a cache is serving an old copy.

Will deleting the .maintenance file delete my content?

No. The file holds only one line with the update start time, and deleting it removes only the lock that shows the maintenance message. Your posts, pages, media and settings stay untouched. Still, back up the site before you re-run a failed update, because the update itself changes files.

Why does the message come back after I delete the file?

Something is writing a fresh file or showing its own page. An automatic update can retry and recreate the file, a maintenance or coming-soon plugin can stay switched on, or a page cache can serve a stored copy. Check the plugin settings, look for a maintenance.php file in wp-content, and clear every cache layer.

Can I fix this from the WordPress dashboard?

No, not while the message is active, because the dashboard sits behind the same maintenance screen. You need file access through your host file manager, FTP or SFTP, or WP-CLI over SSH. Once the file is gone and the site loads again, use Dashboard > Updates to finish the interrupted update.

Does this error hurt my search rankings?

A short outage does little harm, because WordPress answers with a 503 status and a Retry-After header that tells search engines the downtime is temporary. A message left up for days can still cost crawls and visits, so fix it the same day and confirm the home page returns a normal 200 response.

What if I cannot find the .maintenance file?

Turn on the option to show hidden files in your file manager or FTP client, because names that start with a dot stay hidden by default. Check the WordPress root folder, usually public_html, beside wp-config.php. If it is still missing, the message may come from a plugin page or a cache instead.

Sources

  1. Updating WordPress WordPress.org Documentation
  2. wp_is_maintenance_mode() WordPress Developer Resources
  3. wp maintenance-mode deactivate WordPress Developer Resources
  4. How to Fix WordPress Stuck in Maintenance Mode Kinsta
  5. Enable Maintenance Mode WP Engine Support
  6. How to Fix the Error Briefly Unavailable for Scheduled Maintenance in WordPress SiteGround

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test