Briefly unavailable for scheduled maintenance in WordPress – causes and solutions

You visit your WordPress website and suddenly see a message: “Briefly unavailable for scheduled maintenance. Check back in a minute.” In Dutch you might see “Tijdelijk niet beschikbaar vanwege gepland onderhoud. Probeer het over enkele minuten nog een keer.” Don’t panic — this usually isn’t serious and is easy to fix. In this article you’ll learn what the maintenance message means, why it happens, and how to bring your site back online yourself. I’ll also share tips to prevent your site from getting stuck in maintenance mode again.

What does this message mean and when does it appear?

“Briefly unavailable for scheduled maintenance. Check back in a minute.” is the standard message WordPress shows when your site is temporarily in maintenance mode. WordPress automatically activates this mode during updates of the core software, plugins, or themes. While updates are installing, your website is briefly unavailable to visitors so files can be updated safely. Visitors (and you) see the maintenance message instead of your site.

In principle, this message should appear only briefly — often just a few seconds during an update. It’s meant to tell users the site is “busy” and will return shortly. Normally updates are so fast that you barely notice. As soon as WordPress finishes updating, it turns off maintenance mode and the message disappears automatically.

Technical background: how WordPress maintenance mode works

Under the hood, WordPress puts your site in maintenance mode by creating a temporary file called .maintenance in the root of your website (the directory where wp-config.php lives). As long as that .maintenance file exists, WordPress will show the maintenance message to every visitor. Once the update completes successfully, WordPress normally deletes the .maintenance file automatically.

The message stays if something goes wrong and the .maintenance file is not removed. In that case the site remains “stuck” in maintenance mode and the message keeps showing even though the update stopped. Your site looks unavailable until you intervene.

Why does this happen? The most common reason is that an update process was interrupted or didn’t complete properly. Common scenarios include:

• You accidentally closed the browser or tab while an update was still running (or navigated away).
• You tried to run too many updates at once (for example, dozens of plugins/themes), causing something to hang or slow down.
• An update failed due to a server interruption, timeout, or lack of resources (for example a slow host or low memory).
• A conflict or bug in the new plugin/theme version prevented WordPress from exiting maintenance mode.

In all these cases, the .maintenance file remains on the server and the site stays in maintenance mode. The good news is you can fix this easily by deleting that file. Here’s how.

Solution: take your site out of maintenance mode

The fix for a stuck maintenance mode is simple: manually delete the .maintenance file on your server. Once it’s gone, WordPress will immediately show your normal site again. You can do this in different ways depending on the tools you have access to:

Option 1: Delete .maintenance via your hosting file manager (cPanel/DirectAdmin/Plesk)

Most hosting plans include a file manager in the control panel (cPanel, DirectAdmin, Plesk, etc.). This lets you access files via your browser. Follow these steps (cPanel example):

1. Log in to your hosting control panel and open the File Manager.
2. Navigate to the root folder of your WordPress installation (often public_html, or a subfolder if WordPress is installed there).
3. Look for a file named .maintenance. Note: it’s hidden because it starts with a dot. Enable “Show Hidden Files” if you don’t see it.
4. Delete the .maintenance file. In cPanel, right‑click and choose Delete, then confirm. In other panels it’s similar: select .maintenance and delete.
5. Reload your website. The maintenance message should be gone and your site should load normally.

Option 2: Delete .maintenance via FTP

If you prefer direct access via FTP (e.g., FileZilla), you can do that too. The steps are similar:

1. Connect to the server via FTP/SFTP using your hosting credentials (host, username, password, port).
2. Navigate to the WordPress root folder — usually the main folder where WordPress is installed (often public_html). You’ll recognize it by files like wp-config.php and folders like wp-content.
3. Make sure hidden files are shown in your FTP client. In FileZilla you can click Server and enable Force showing hidden files.
4. Locate .maintenance and delete it. In FileZilla, right‑click and choose Delete.
5. Reload your site in the browser. Maintenance mode should be lifted immediately.

Option 3: Disable maintenance mode via WP‑CLI (advanced)

If you have SSH access and know WP‑CLI (the WordPress command‑line interface), you can also end maintenance mode that way. WP‑CLI has a built‑in command:

wp maintenance-mode deactivate

This deactivates maintenance mode by removing the .maintenance file. Once run, your site is accessible again. (Note: WP‑CLI is an advanced option — only use it if you’re comfortable with the command line and WP‑CLI is properly installed.)

Tip: in rare cases your site stays in maintenance mode even after deleting .maintenance. That usually means something else went wrong during the update. You can try another fix, like checking wp-activate.php for a misconfiguration (advanced). But in most cases, removing .maintenance is enough to fix it.

Tips to prevent this in the future

Prevention is better than cure. Here are practical tips to avoid getting stuck in maintenance mode again:

• Let updates finish (don’t interrupt). Be patient and don’t close your browser or tab while an update is running. Wait until WordPress reports that updates are completed (e.g., “Maintenance mode disabled” or “Updates have been completed”). Only then is it safe to leave the page.
• Update plugins and themes one by one. Don’t run a huge batch of updates at once. Updating one plugin or theme at a time reduces the chance of something hanging and lowers conflict risk.
• Monitor automatic updates. If you have auto‑updates enabled for core or plugins, make sure you receive notifications and check your site shortly after updates run. Auto‑updates are usually fine, but if something goes wrong, you’ll want to know quickly. Consider disabling auto‑updates if they cause issues frequently, so you can update manually in a controlled way.
• Use a staging environment for major updates. Many good hosts offer staging (test environments) where you can safely test updates before applying them to your live site. Testing on staging helps you resolve conflicts before your live site updates.
• Choose fast, reliable hosting. Sometimes updates fail because of slow servers or limited resources. A high‑quality host with sufficient capacity completes updates faster and is less likely to time out. If you often get stuck updates, consider upgrading your hosting plan or switching to a host that handles updates better.

With these measures, you significantly reduce the chance of seeing the maintenance message for longer than necessary. Updates are more likely to run smoothly, and if something does go wrong, you can fix it quickly.