If your WordPress site is showing the message "Briefly unavailable for scheduled maintenance. Check back in a minute," it means WordPress started an update but did not finish cleaning up after itself. This article explains why it happens and how to fix it immediately.
Why this happens
When WordPress runs an update to a plugin, theme, or its own core files, it creates a temporary file called .maintenance in your site root. This file tells WordPress to display the maintenance message to visitors while the update is in progress.
Under normal conditions, WordPress deletes the .maintenance file as soon as the update completes. However, if the update process is interrupted for any reason, the file remains in place. Common causes of interruption include:
- Closing the browser tab before the update finished
- A server timeout during a large update
- Updating multiple plugins at once when one fails partway through
- A brief network interruption between your browser and the server
How to fix it
The fix is straightforward: delete the .maintenance file from your site root. Your site will start loading normally the moment the file is removed.
Option 1: Use File Manager
- Open the Web60 portal and go to your site management page.
- Open File Manager.
- Navigate to your site root directory. This is the top-level folder that contains
wp-config.php,wp-content, and other WordPress files. - Enable Show hidden files. The
.maintenancefile starts with a dot, which means it is hidden by default. - Find the
.maintenancefile and delete it. - Load your site in the browser. It should display normally.
Option 2: Use SFTP
- Connect to your site via SFTP using the credentials from your Web60 portal.
- Navigate to the site root directory.
- Find and delete the
.maintenancefile. - Refresh your site in the browser.
After removing the file
Once your site is back online, check whether the update that caused the problem actually completed. Go to your WordPress Dashboard and look at Dashboard, then Updates. If any plugins or themes still show as needing an update, run the update again. This time, make sure to stay on the page until the process confirms it has finished.
If the same plugin fails to update repeatedly, it may be incompatible with your version of PHP or WordPress. Check the plugin page on wordpress.org for compatibility information, or raise a support ticket if you need help.
FAQ
Q: What caused the .maintenance file to be left behind?
A: WordPress creates the .maintenance file at the start of any update to plugins, themes, or core files. It is supposed to delete the file automatically when the update finishes. If the update is interrupted by a timeout, a network issue, or a server error, the file is left behind and your site stays in maintenance mode.
Q: Is it safe to delete the .maintenance file?
A: Yes, it is completely safe. The .maintenance file is a temporary lock file, not a configuration file. Deleting it simply tells WordPress to stop showing the maintenance message and serve your site normally. It does not affect your content, settings, or any updates that completed successfully.
Q: How can I prevent this from happening again?
A: Avoid navigating away from the WordPress dashboard while an update is running. Do not close the browser tab or click other links until the update confirms it has finished. If you are updating several plugins at once, use the bulk update option and wait for all of them to complete before doing anything else.
Frequently asked questions
What caused the .maintenance file to be left behind?
WordPress creates the .maintenance file at the start of any update to plugins, themes, or core files. It is supposed to delete the file automatically when the update finishes. If the update is interrupted by a timeout, a network issue, or a server error, the file is left behind and your site stays in maintenance mode.
Is it safe to delete the .maintenance file?
Yes, it is completely safe. The .maintenance file is a temporary lock file, not a configuration file. Deleting it simply tells WordPress to stop showing the maintenance message and serve your site normally. It does not affect your content, settings, or any updates that completed successfully.
How can I prevent this from happening again?
Avoid navigating away from the WordPress dashboard while an update is running. Do not close the browser tab or click other links until the update confirms it has finished. If you are updating several plugins at once, use the bulk update option and wait for all of them to complete before doing anything else.
Last updated: 4 April 2026