Ffile2fix
Sign in Get started

Fix "Briefly unavailable for scheduled maintenance" in WordPress

Briefly unavailable for scheduled maintenance. Check back in a minute.

WordPress creates a .maintenance file in the site root while it installs updates and deletes it when finished. If the update is interrupted, by a timeout, closed browser tab or error, the file stays behind and every visitor sees this message. Deleting the file restores the site; then re-run the update that failed.

Also appears as: WordPress stuck in maintenance mode · Briefly unavailable for scheduled maintenance after plugin update · Another update is currently in progress.

Common causes

  • An update was interrupted by closing the browser or losing the connection
  • PHP timed out or ran out of memory during a large update
  • Updating many plugins at once on a slow server
  • A plugin or theme update failed partway, leaving files incomplete
  • Insufficient disk space or file permissions during the update

How to fix it

  1. Delete the .maintenance file. Connect over SFTP or the hosting file manager and delete .maintenance from the WordPress root, next to wp-config.php. It is a hidden file, so enable 'show hidden files'. From a shell: rm /var/www/html/.maintenance.
  2. Check the site and dashboard. Reload the site and wp-admin. If you now see a critical error, the interrupted update left a plugin or theme broken; disable it by renaming its folder in wp-content/plugins or wp-content/themes.
  3. Re-run the update. Go to Dashboard > Updates and update the item again, one at a time. With WP-CLI run wp plugin update plugin-name or wp core update.
  4. Clear the core update lock if needed. If WordPress says 'Another update is currently in progress', wait 15 minutes for the lock to expire, or delete the core_updater.lock option with wp option delete core_updater.lock.
  5. Fix resource limits. If updates keep timing out, raise max_execution_time and memory_limit in PHP, and check free disk space with df -h. WordPress downloads and unpacks packages in wp-content/upgrade, which needs space and write permission.

Shell / WP-CLI

# Remove the leftover maintenance flag
rm /var/www/html/.maintenance

# Re-run updates one at a time
wp plugin update --all --dry-run
wp plugin update woocommerce

# Clear a stuck core update lock
wp option delete core_updater.lock

How to stop it happening again

  • Keep the browser tab open until updates finish
  • Update plugins one or a few at a time on slower hosting
  • Run updates with WP-CLI, which is not subject to web request timeouts
  • Take a backup before major updates

Frequently asked questions

Is it safe to delete the .maintenance file?

Yes. It only contains a timestamp that tells WordPress to show the maintenance message. Deleting it does not undo or damage the update.

Why can't I see the .maintenance file?

Files starting with a dot are hidden by default in most FTP clients and file managers. Enable the option to show hidden files or use ls -a on the command line.

Does the maintenance message go away by itself?

WordPress ignores a .maintenance file older than 10 minutes, so the message usually disappears on its own. If it persists, a cache may still be serving the maintenance page, so delete the file and purge your page cache and CDN.