WordPress creates a temporary .maintenance file during updates. If the update process crashes or times out, the file can remain and keep the whole site unavailable.
Symptoms
- Every page says “Briefly unavailable for scheduled maintenance. Check back in a minute.”
- The message remains long after an update should have finished.
- The problem started during bulk plugin/theme updates.
- wp-admin is unavailable with the same maintenance message.
Common causes
The same visible WordPress error can have several causes. A reliable fix starts by matching the symptom to logs, request behavior and recent changes.
- Update process was interrupted before cleanup.
- PHP timeout, process kill or connectivity failure.
- Multiple updates ran at once on a constrained server.
- Filesystem permissions prevented finalization.
Safe diagnosis
- Confirm no WordPress update process is still actively changing files.
- Check for the .maintenance file in the WordPress root.
- Review update logs/files to confirm whether any component is incomplete.
- Verify the site after maintenance mode is removed.
Production safety: create a recovery point before changing code, plugins, database values or server configuration. Business-critical WooCommerce sites should avoid random deactivate/update experiments during active traffic.
How the issue is fixed
- Remove the stale .maintenance file when the updater is no longer running.
- Complete or roll back any partially installed plugin/theme/core update.
- Resolve the timeout, storage or permission cause before retrying.
- Test frontend, wp-admin and scheduled tasks.
Avoid this shortcut: Do not remove maintenance mode while an update is still writing files. That can expose visitors to a partially updated application.
When to request expert WordPress bug fixing
Professional troubleshooting is useful when the site is business-critical, the error returns after a temporary fix, wp-admin is unavailable, the failure began after a complex update/migration, or you cannot identify the responsible code from logs. WP•FIX focuses on the smallest safe change that restores the failing path and explains the root cause.
FAQ
Can I just delete .maintenance?
Usually, if the update process has definitely stopped. You should still check whether the interrupted update left incomplete files.
Why does this happen during bulk updates?
Several packages may compete for CPU, I/O or execution time, making an interruption more likely on constrained hosting.
Will this delete my content?
Removing a stale maintenance file does not delete content, but the interrupted update itself may still need repair.
Can WP•FIX check the update after the site comes back?
Yes. Verifying component versions and functionality is important after an interrupted update.
Need this WordPress issue fixed?
Send the URL, error message and what changed immediately before the problem started.
Request troubleshooting