Short answer: the message “Briefly unavailable for scheduled maintenance. Check back in a minute” that never goes away means an update was interrupted. WordPress left a .maintenance file at the site root and never removed it.
Why it happens
Before updating core, a plugin or a theme, WordPress writes a .maintenance file that puts the whole site behind that message, then deletes it when the update finishes. If the update is interrupted — a timeout, a fatal error, a closed browser tab, updating many plugins at once — the file is left behind and the site stays locked.
The fix, step by step
- Connect over SFTP or the hosting file manager.
- In the WordPress root (where
wp-config.phplives), delete the.maintenancefile. It starts with a dot, so enable “show hidden files” if you do not see it. - Reload the site — it should return immediately.
Do not stop there
Removing the file unlocks the site, but the update that was interrupted may be half-applied. Check that core, the plugin or the theme finished updating: an incomplete update can leave mismatched files that cause a later fatal error. Enable WP_DEBUG_LOG and re-run the update cleanly, one component at a time, with a backup in place.
Prevent the repeat
Update one plugin at a time rather than in bulk, avoid closing the tab mid-update, and ensure the server has enough memory and time for the operation. If updates routinely time out, that underlying resource limit is the real issue to fix.
WP REPAIR INCIDENT STANDARD
Safe intervention sequence
The persistent maintenance message usually means an update did not remove .maintenance. Removing the marker restores access but the interrupted component still needs integrity and version checks.
- Confirm the message is WordPress maintenance mode, not a host or proxy maintenance page.
- Preserve the update timestamp and identify the component being changed.
- Remove .maintenance only from the correct WordPress root.
- Verify core, plugin or theme files and rerun the update one component at a time.
What must be verified
- No .maintenance marker remains unexpectedly.
- The component reports a complete, consistent version.
- Admin, front end and the component's critical feature work.
Official technical sources
This guide explains the diagnosis. If the site is affected now, the intervention should preserve a rollback path and verify the real business journey.
See the emergency repair service →