If your WordPress site shows "Briefly unavailable for scheduled maintenance" and won't go away, delete the file called .maintenance in your site's root folder. WordPress creates this file automatically during every plugin, theme, or core update, then deletes it when the update finishes. If an update gets interrupted, the file gets stuck and so does your site.
Connect via FTP or the portal's file manager, open your site's root directory (usually public_html or a subfolder if WordPress isn't installed at the domain root), and look for .maintenance. It's a hidden file, so make sure your FTP client or file manager is set to show hidden files. Delete it and reload your site - this often fixes it right away.
Why the file gets stuck
WordPress writes .maintenance the instant an update starts, as a safety measure so visitors don't hit a half-updated site. It's supposed to be a matter of seconds. Three things on our stack commonly interrupt that window and leave the file behind:
1. The update timed out
A slow plugin download, a large core update, or a PHP execution limit can cause the update process to stop before it finishes cleanly. The maintenance file never gets cleaned up because the script that would delete it never reached that line. This is more likely if you were updating several plugins at once, or updating over a shared connection during high traffic.
2. You navigated away or closed the tab mid-update
If you closed the browser tab, hit back, or lost your connection while wp-admin was mid-update, the PHP process on our end may have been cut off before completion. Same result: the flag file stays.
3. A plugin or theme update triggered a fatal error
If the update itself introduced a fatal PHP error (an incompatible plugin version, a theme conflict), WordPress can get stuck between "update running" and "update finished." In this case, deleting .maintenance will bring the site back, but you may immediately see a different error afterward. If that happens, treat it as its own issue: check database connection errors if you see a blank database error, or work through the white screen of death steps if the page goes blank, since both explain how to turn on WP_DEBUG and isolate the offending plugin or theme.
If deleting the file doesn't fix it
Rarely, the maintenance file gets recreated immediately after you delete it. This usually means an update is genuinely still running in the background, not stuck, just slow. Wait a minute and check again before assuming it's stuck a second time.
If the site comes back but shows "There has been a critical error on this website" instead of your homepage, the interrupted update left a plugin or theme in a broken state. That article walks through the recovery mode email and the plugin-by-plugin isolation process, which is the fastest way to find the specific file that's failing.
Avoiding this next time
Update plugins and themes one at a time rather than in a single batch, especially on sites with many active plugins. Keep the browser tab open and connected until you see the "Updated!" confirmation. If you're updating a site that historically times out, check the PHP version tile in the portal, since some update failures trace back to a plugin requiring a newer PHP version than the one currently active.
When to contact support
If .maintenance isn't present in the root directory but the site still shows a maintenance-mode message, or the file reappears repeatedly without an update running, open a ticket from the portal's Support section. Include the exact message text and roughly when it started so support can investigate.