How to fix the WordPress maintenance mode error ("Briefly unavailable for scheduled maintenance")

WordPress maintenance mode is a temporary state WordPress enters every time it installs core, plugin, or theme updates. During the swap, WordPress replaces old files with new ones — and it doesn't want visitors hitting a half-updated site, so it shows a message instead: "Briefly unavailable for scheduled maintenance. Check back in a minute."

Under the hood, WordPress does two things when an update starts. It creates an empty file called .maintenance in the site root, and it loads a tiny helper file (wp_maintenance()) that checks for that file on every request. If the file exists, WordPress shows the maintenance message instead of the site. When the update finishes, WordPress deletes the .maintenance file and normal service resumes — usually within seconds.

So the message itself isn't a bug. It's a feature. It only becomes an error when the file gets stuck.

The .maintenance file gets left behind whenever an update is interrupted before WordPress reaches the cleanup step. In our incident logs at WebCare Studios, the four most common causes are: (1) the admin closed the browser tab mid-update, (2) the PHP process hit max_execution_time and died, (3) shared hosting killed the request for using too much memory, or (4) a plugin update triggered a fatal error that stopped the update runner.

None of these are your fault as a site owner. They're symptoms of the environment WordPress is running in — usually a host that's undersized for the site, or a bulk update run directly on production without staging.

• 1. Connect to your site via SFTP (FileZilla, Cyberduck, Transmit) or open your host's File Manager (cPanel, Plesk, MyKinsta, SiteGround Site Tools).
• 2. Navigate to the WordPress root folder — the folder that contains wp-config.php, wp-login.php, and the wp-content directory.
• 3. Turn on "show hidden files". The .maintenance file starts with a dot, which hides it by default. In FileZilla: Server menu → "Force showing hidden files". In cPanel File Manager: Settings → tick "Show Hidden Files".
• 4. Delete the file named .maintenance. Only that file. Don't touch wp-config.php or anything else.
• 5. Reload your site in a fresh browser tab (or private window to bypass cache). The maintenance message is gone.

Deleting the file gets visitors back in, but if the update was still mid-flight some plugin files may be half-swapped. You'll usually see PHP warnings, a broken plugin, or in the worst case a critical error.

Log into wp-admin and go to Dashboard → Updates. Re-run whatever update was in progress. WordPress finishes the swap cleanly and the warnings clear.

If wp-admin itself throws a critical error, force-disable the plugin that was being updated: rename its folder inside wp-content/plugins via SFTP (for example rename 'woocommerce' to 'woocommerce_off'). WordPress will deactivate it, the admin loads, and you can reinstall the plugin fresh.

Update in staging, not on live. Every WebCare Studios care plan tests updates on a staging clone first. If an update breaks staging, live never sees it — and live never gets stuck in maintenance mode.

Raise PHP timeouts on shared hosting. Ask support to bump max_execution_time to 300 seconds and memory_limit to at least 256M. That single change removes the most common cause of interrupted updates.

Put Cloudflare or Bunny CDN in front of the site. During slow origin responses (like an update running), the CDN absorbs the delay so the browser doesn't disconnect first.

If your site gets stuck in maintenance mode more than once a quarter, it's not a WordPress problem — it's a hosting or workflow problem. That's usually when founders move to a managed care plan.