Skip to main content
WordPress Nov 7, 2026 6 min read

WordPress Stuck in Maintenance Mode After an Update

WordPress still showing a maintenance message after an update? Check progress, protect your recovery copy and understand a stale update marker before retrying.

Ghana Troubleshooting Website Maintenance WordPress
A laptop displaying a purple hourglass illustration beside a phone on a stand and a closed notebook on a wooden reception counter.

You start a WordPress update, open your website and find this message instead of your homepage:

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

A short interruption can be part of the update. A message that keeps returning needs a closer look, but the next step depends on whether the update is still running. Repeatedly clicking Update or deleting files immediately can make the situation harder to investigate.

Start by recording what changed, checking progress and protecting a recovery copy. Then deal with the maintenance screen and the unfinished update as separate tasks.

1. Check which maintenance page you are seeing

WordPress uses a small file called .maintenance in the installation’s root folder during automatic updates. Its troubleshooting guide explains the connection between that file and the standard message.

A page with your logo, a countdown or a customised announcement may come from a maintenance plugin or a hosting control instead. The appearance alone does not establish the cause.

What you can observe What to check next
The standard message appeared just after an update The update’s progress and whether anyone else started maintenance
A branded coming-soon page appeared Which person or tool enabled that page
One browser shows the message while another shows the website Whether you are seeing an old saved response rather than the current page

Write down the exact page address and take a screenshot. If the address contains a temporary login link or security token, remove that part before sharing it.

If the problem is a browser connection error rather than a maintenance page, use our website-not-opening checks to investigate that symptom.

2. Give the current update time to finish

Keep the original update tab available. If it still shows progress, avoid starting the same update from another tab or asking a colleague to run it again. When a developer manages updates for you, check whether they have work in progress before changing anything.

Consider a fictional guesthouse in Cape Coast. Its owner starts a booking-plugin update at 14:10 GMT and sees the maintenance screen on a phone at 14:11. Recording those times and checking the original update window gives the person investigating a useful sequence of events. Starting another update does not.

The standard WordPress maintenance check normally stops treating the update marker as current when its recorded timestamp is at least ten minutes old. That is a check on the marker’s age, not a promise that an update finishes within ten minutes.

If the message persists beyond that period, have the running update, the marker and any cached or separately configured maintenance page checked. A continuing message does not prove that an old file is the only problem.

Compare the public page in a private browser window and, if possible, on a phone using mobile data. Note the result rather than repeatedly refreshing. If both still show maintenance and you cannot confirm progress, pause further update attempts.

3. Verify the backup before changing files

A useful WordPress recovery copy needs both the website files and its database. Downloading the website folder alone usually does not capture the database. The WordPress backup guidance explains the distinction.

Before a repair, establish:

  • Which site the backup belongs to and when it was created.
  • Whether the files and database are both included and their dates make sense together.
  • Whether the backup completed successfully and can be accessed.
  • Who can restore it and what newer information a restore would replace.

Keep a known working backup from before the update. A separate capture of the current failed state may help an investigation, but it should not overwrite that earlier recovery copy.

For the guesthouse, restoring an older database could replace bookings or enquiries recorded since that backup. Agree on how to preserve that newer information before authorising a restore. Clearing a maintenance message and restoring an entire website are different operations.

4. Remove only a confirmed stale update marker

Once the person managing the site has confirmed that no update is running and the recovery copy is available, a leftover .maintenance file may be appropriate to remove. WordPress documents this remedy for maintenance messages left after an upgrade.

The exact installation matters. A hosting account can contain more than one website, and its main folder is not automatically the WordPress root. The correct installation contains that site’s wp-admin directory. The leading dot in the marker’s filename may require hidden files to be shown in the file tool.

If you have authorised file access and are confident about the site and folder, limit the change to the confirmed stale marker. Otherwise, give the hosting administrator the details and have them perform that check. Do not delete WordPress folders or the database to remove the message.

If the marker returns, stop removing it repeatedly. Something may still be initiating maintenance, and that process needs to be identified. The same applies if a custom maintenance page remains after the marker is gone.

5. Check the result before running another update

A homepage appearing again does not establish that the update succeeded. In the dashboard, review the update result and the installed version of the component you were updating. If access is unavailable, have the administrator check those results before retrying.

Check the public homepage and the page most important to the business. For the guesthouse, that means opening the room and booking pages on a phone and confirming that the booking control loads. Use controlled test details for any agreed form test; avoid submitting a real payment simply to see whether a page works.

WordPress’s update instructions cover failed updates and follow-up checks. If an update failed, resolve the reported cause and confirm the recovery plan before repeating it. Keep firewall and rate protection active while investigating any separate access refusal.

Record a new error as a new finding. For example, our invalid JSON response guide covers a different editor problem; it is not evidence that the maintenance marker has returned.

6. Send a useful support report

A short report helps the person investigating distinguish an ongoing update from a leftover screen. This example is entirely fictional:

Website: coaststay.example
Started: 14:10 GMT while updating the booking plugin
Update result: original window stopped showing progress; no second attempt made
Still affected: homepage and booking page at 14:25 GMT
Comparison: same message in a private window and on mobile data
Backup: a pre-update backup is listed; please verify its contents and recovery route before making changes

Add the exact component name, version if known, and a redacted screenshot. Keep passwords, recovery codes and temporary login links out of the report. Naming the backup does not by itself confirm that it is usable.

Next step: If your Nakroteck-hosted WordPress site remains in maintenance mode, contact Nakroteck support with that report and ask for the active update and recovery copy to be checked before any file change or restore.

Need help choosing the right setup?

Talk to Nakroteck before you buy hosting, domains, SSL, or website services. We will help you choose the right option for your business.

We use optional analytics and advertising cookies to understand which campaigns lead to purchases. Essential cookies keep checkout and account access working. Cookie policy