You ran an update, and now your entire site — front end and admin — shows nothing but “Briefly unavailable for scheduled maintenance.” The update didn’t finish cleanly and left your site locked. It looks alarming, but the fix is deleting a single file.
Why it’s stuck
When WordPress begins an update, it drops a hidden file named .maintenance into your site’s root and shows the maintenance notice to everyone. Once the update completes, it deletes that file automatically. If the update fails partway — a timeout, a memory shortage, a dropped connection — the file is orphaned and your site stays in maintenance mode indefinitely.
The fix in three steps
- Log in to cPanel and open File Manager.
- Go to your site root (usually
public_html) and enable Show Hidden Files from the Settings menu — the file starts with a dot, so it’s hidden by default. - Find the file called
.maintenanceand delete it.
Reload your site. The maintenance message is gone and your site is back.
Now finish what the update started
Clearing the file unlocks the site, but the update itself may be half-applied. Log into wp-admin, go to Dashboard → Updates, and re-run whatever didn’t complete. Check your plugins and theme are on their intended versions. A half-finished update can cause subtle issues, so it’s worth confirming everything actually updated.
Fix the reason it failed
Updates stall for a reason — usually too little PHP memory or too short an execution time. Add define('WP_MEMORY_LIMIT', '256M'); to wp-config.php and raise max_execution_time to 300 in cPanel’s INI Editor. With more headroom, updates finish cleanly and never leave the file behind.
Update more carefully next time
Update one plugin at a time rather than in a big batch, during quiet hours, and always take a backup first. If an update fails, you’ll know exactly which one and you’ll have a clean restore point.
If updates keep failing even after raising the limits, there may be a server-side cap involved — send us a ticket and we’ll investigate.
