What the WordPress maintenance message means
During certain updates, WordPress creates a temporary file named .maintenance in the root directory of the WordPress installation. While that file is active, normal visitors see the maintenance message instead of pages that might otherwise load with a mixture of old and new code.
After a successful update, WordPress removes the temporary file automatically. If the PHP process stops, the connection fails or an update ends unexpectedly, the file can remain behind and the website appears stuck in maintenance mode.
This message does not by itself mean that the database is damaged or the website has been hacked. The important next step is to establish whether only the temporary maintenance file remains or whether the interrupted update also left a plugin, theme or WordPress core update incomplete.
Why WordPress gets stuck in maintenance mode
The most common trigger is an interrupted update. That can happen when a browser session is closed during the process, the server reaches a resource limit, file permissions prevent WordPress replacing a file, or several updates are being processed and one fails part-way through.
Plugin and theme updates also depend on WordPress being able to write to the required directories. Incorrect ownership or permissions can therefore cause the update itself to fail even after the maintenance message has been removed.
A full disk, unavailable temporary directory or hosting problem can produce similar symptoms. This is why simply removing .maintenance should be followed by checks in the dashboard rather than treating removal of the message as proof that every update completed correctly.
How to remove WordPress maintenance mode safely
Before changing site files, take a full backup of both files and the database. If your hosting platform already creates restore points, confirm that a current one exists.
- Wait briefly and refresh once. An active update may genuinely still be running. Avoid repeatedly starting the same update in multiple browser tabs.
- Check the WordPress dashboard if it is accessible. Look under Dashboard, then Updates, for an update that failed or still needs to be completed.
- Locate the WordPress root directory. Using your host's file manager or SFTP, open the directory containing wp-admin, wp-content and wp-includes. Configure the file manager to show hidden files if necessary.
- Delete only the .maintenance file. WordPress documentation specifically identifies removal of this temporary file as the recovery step after a failed update. Do not delete wp-config.php, WordPress core directories or unrelated hidden files.
- Reload the website and dashboard. Then check which core, plugin or theme update did not finish and retry it only after confirming the site is otherwise stable.
- Investigate repeated failures. Check available storage, file ownership and permissions, PHP errors and hosting logs. Do not make directories world-writable as a routine fix.
If an update has left the site with a PHP error rather than the maintenance message, use the WordPress support guidance rather than repeatedly deleting files.
When a failed WordPress update needs help
Get technical help if the maintenance message disappears but the site then shows a fatal error, blank page or broken dashboard. The interrupted update may have left mismatched plugin, theme or core files that require a controlled repair.
You should also stop if you cannot identify the correct WordPress root, file ownership is wrong, updates repeatedly fail or you would need to change server permissions without understanding the hosting setup.
Web Support Services offers an Emergency Fix for £249 per incident, with a response within 2 working hours. Care plans start from £59 a month and include managed updates and maintenance intended to reduce repeat update failures.