Quick answer
When a WordPress update fails, the site often remains in maintenance mode due to a leftover `.maintenance` file in the installation root. Simply delete or rename it and the site will be available again. Then check if the update completed and repeat it if necessary.
How to recognize the problem
- The site shows the message "Briefly unavailable for scheduled maintenance"
- The message appears on all pages, not just in the admin area
- Access to the admin panel is disabled
- After attempting to update WordPress, a plugin, or a theme, the site went down
- A `.maintenance` file exists in the site root
Most common causes
Leftover `.maintenance` file
During an update, WordPress automatically creates a `.maintenance` file in the installation root. If the update is interrupted (power outage, connection loss, lack of resources), the file remains and the site stays in maintenance mode.
Update interrupted due to time limit
If the update takes longer than the allowed PHP script execution time, the process is terminated and the `.maintenance` file remains.
Insufficient permissions
If WordPress does not have permission to delete `.maintenance` or write to the plugin/theme folder, the update cannot complete properly.
Conflict with a plugin or theme
Rarely, a plugin that interferes with updates or a security plugin can block the process and leave the site in maintenance mode.
Step-by-step fix
- 1
Check if the site is really in maintenance mode
Open the site in a browser. If you see the message "Briefly unavailable for scheduled maintenance. Check back in a minute.", confirm that it is maintenance mode and not another error. Also try to access the
/wp-admin/path; if that is also blocked, proceed to the next step. - 2
Access the site files via FTP or file manager
Log in to your hosting panel (cPanel, Plesk, or similar) and open the file manager, or connect with an FTP/SFTP client. Go to the root directory of the WordPress installation, where
wp-config.php,wp-content, andwp-adminare located. - 3
Find and delete the `.maintenance` file
In the root, look for a file named exactly
.maintenance. First check that an update is not in progress; if it is, wait for it to finish. If it exists and the update was interrupted, delete it or rename it to.maintenance.old. Refresh the site in your browser; maintenance mode should disappear. If the file is not visible, enable showing hidden files in your file manager or FTP client. - 4
Check if the update completed
Log in to the WordPress admin. Go to
Dashboard > Updates. If it says WordPress is on the latest version, the core update is complete. If it still offers the same core update, it was probably interrupted and needs to be repeated. - 5
Repeat the update if necessary
If the update was interrupted, restart the WordPress, plugin, or theme update from the admin. Before that, make a backup of the site (files and database). Update one plugin at a time to more easily identify any problem.
- 6
Check file permissions and ownership
Make sure WordPress has write permissions to
wp-contentand its subfolders. Typically, folders have permissions755and files644. If you are unsure, contact your hosting support; incorrect permissions can cause security issues. - 7
Disable plugins that might interfere
If the problem persists, temporarily deactivate all plugins, then repeat the update. If it succeeds, enable plugins one by one until you find the culprit. Do not forget to re-enable all plugins.
- 8
Restore the site from backup if nothing helps
If the site still does not work or the update caused damage, restore files and database from the last backup. Before restoring, make a copy of the current state if possible, because restoring overwrites files and database. Do this through the hosting panel or a backup plugin. After restoring, first check if the site works, then try the update again.
If nothing helps: error checking and contacting hosting
If you deleted .maintenance but the site still shows maintenance mode or another error, enable WP_DEBUG in wp-config.php. Before making changes, make a copy of wp-config.php. Define define( 'WP_DEBUG', true );, define( 'WP_DEBUG_LOG', true );, and define( 'WP_DEBUG_DISPLAY', false ); to see error details in wp-content/debug.log without showing errors to visitors. Often the log will reveal the name of the plugin or theme causing the problem. When you finish checking, disable WP_DEBUG or remove those lines. If you do not have file access or need help with the database, contact your hosting support. They can check if the update is blocked at the server level (e.g., resource limits) and if there is a security mechanism blocking access. Do not attempt to manually modify WordPress core files unless you know exactly what you are doing.
How to prevent it
- Regularly make backups of the site (files and database) before every update.
- Update WordPress, plugins, and themes regularly, but first on a test copy of the site.
- Maintain file and folder permissions according to recommendations (folders 755, files 644).
- Use reliable hosting with sufficient resources and automatic backups enabled.
When to call a professional
If you do not have access to the site files, do not know if the update completed, or the problem repeats with suspicion of a damaged database, it is better to contact IT support. They can safely check the state, restore a backup, and prevent the problem from recurring.
Website development · Fast, SEO-ready, multilingual websitesFAQ
Is it safe to delete the `.maintenance` file?
Yes, if the update was interrupted and the site is stuck in maintenance mode; do not delete it while an update is in progress. WordPress creates that file temporarily and deletes it automatically when the update finishes. Deleting it will not cause data loss, but make a backup first if possible.
How do I know the update is complete?
Log in to the admin and go to `Dashboard > Updates`. If it says WordPress is on the latest version and there are no available core updates, the process is complete. Also check the site page to see if it loads normally.
What if I cannot access the site files?
Contact your hosting support and ask them to delete the `.maintenance` file or give you access to the file manager. Without file access, you cannot manually remove maintenance mode.