How to Fix “It Is Temporarily Unavailable Due to Maintenance”

A website that displays “It is temporarily unavailable due to maintenance” is usually not broken beyond repair. In most cases, this message appears when a WordPress update is interrupted, leaving the site stuck in maintenance mode. The issue can look alarming to visitors, but it is typically fixed in a few minutes by removing one small file or completing the failed update.

What the Maintenance Message Means

When WordPress updates its core files, plugins, or themes, it briefly places the website into maintenance mode. During this process, WordPress creates a temporary file named .maintenance in the main website directory. This file tells visitors that the site is unavailable while updates are being applied.

Normally, the file is removed automatically once the update finishes. However, if the update is interrupted, the file may remain in place. As a result, the website continues showing the maintenance message even though no update is actively running.

Common causes include:

• A failed plugin update caused by compatibility problems or timeout errors.
• A theme update interruption due to server limits or unstable connections.
• A WordPress core update failure that stops before completion.
• Low memory limits on the hosting server.
• Multiple updates running at once, which can increase the chance of errors.
• Browser or admin panel interruption, such as closing the update page too soon.

Step 1: Wait a Few Minutes

Before taking technical action, the site owner should wait for a short period. Some updates take longer than expected, especially on shared hosting or large websites. If the message has appeared for less than 5 minutes, the update may still be processing.

If the message remains after 10–15 minutes, it is likely that WordPress is stuck in maintenance mode. At that point, the administrator can move to manual troubleshooting.

Step 2: Access the Website Files

To remove the stuck maintenance notice, the administrator needs access to the website’s file system. This can usually be done through one of the following methods:

• Hosting file manager: Available inside most hosting control panels.
• FTP or SFTP: Accessed through software such as FileZilla or another FTP client.
• SSH access: Used by more advanced administrators through a terminal.

The person managing the site should open the main WordPress installation directory. This is often named public_html, www, or the domain name itself. The correct folder usually contains files such as wp-config.php, wp-load.php, and folders named wp-admin, wp-content, and wp-includes.

Step 3: Delete the .maintenance File

Inside the root WordPress folder, the administrator should look for a file named .maintenance. Because the file begins with a dot, it may be hidden by default. If it is not visible, the file manager or FTP client may need to be set to show hidden files.

Once found, the .maintenance file should be deleted. After that, the website can be refreshed in a browser. In most cases, the maintenance message disappears immediately and the site loads normally again.

Important: Only the .maintenance file should be removed. Core folders such as wp-admin, wp-content, or wp-includes should not be deleted.

Step 4: Check for Failed Updates

After the site becomes available again, the administrator should log in to the WordPress dashboard and check whether any updates failed. A stuck maintenance message is often a symptom, not the full problem.

The administrator should review:

• Dashboard > Updates to see pending WordPress, plugin, or theme updates.
• Plugins to check whether any plugin is inactive, missing, or partially updated.
• Appearance > Themes to confirm that the active theme still works correctly.
• Site Health to identify memory, PHP, or server issues.

If a specific plugin caused the issue, it may be safer to update it separately rather than running many updates at the same time. On larger sites, updates should ideally be tested on a staging copy first.

Step 5: Clear Cache

Sometimes the maintenance message remains visible because of caching, even after the issue has been fixed. The website may be working correctly, but the browser, caching plugin, server cache, or content delivery network may still be showing an old version of the page.

The administrator should clear:

• Browser cache or test the site in an incognito window.
• WordPress caching plugin cache, if one is installed.
• Hosting cache from the hosting control panel.
• CDN cache, if the website uses a content delivery network.

After clearing cache, the site should be tested again from different devices or networks to confirm that visitors can access it normally.

Step 6: Increase Server Resources if the Problem Repeats

If the error keeps returning during updates, the website may be hitting server limits. WordPress updates require enough memory, execution time, and stable server performance. A small hosting plan may struggle with larger plugins, complex themes, or high traffic.

The administrator can ask the hosting provider to review or increase:

• PHP memory limit, commonly increased to 256 MB or higher for heavier sites.
• Maximum execution time, which controls how long scripts can run.
• File permissions, especially if WordPress cannot write update files properly.
• PHP version, since outdated versions can cause compatibility issues.

For example, a site with 35 active plugins may fail updates more often on a low-resource shared plan than on managed hosting. If maintenance errors happen every month, server performance should be treated as part of the solution.

Step 7: Disable a Problem Plugin or Theme

If the site returns but behaves incorrectly after the maintenance issue is fixed, a plugin or theme may have updated only partially. The administrator can temporarily disable plugins to identify the problem.

If the dashboard is accessible, plugins can be deactivated from the Plugins page. If the dashboard is not accessible, the administrator can use FTP or the hosting file manager and rename the plugins folder inside wp-content. This disables all plugins temporarily. The folder can later be renamed back to plugins, and plugins can be reactivated one by one.

If the active theme is suspected, switching to a default WordPress theme can help confirm whether the theme caused the issue.

How to Prevent the Error in the Future

Although the maintenance message is usually easy to fix, prevention is better than emergency repair. A careful update routine reduces downtime and protects the site from failed changes.

Best practices include:

• Back up the website before updates, including both files and database.
• Update one item at a time instead of running all updates together.
• Use a staging site for major plugin, theme, or WordPress core updates.
• Keep plugins and themes current to avoid large version jumps.
• Remove unused plugins to reduce update conflicts and security risks.
• Schedule updates during low traffic periods, such as late evening or early morning.

A small business website that receives most of its traffic between 9 a.m. and 5 p.m. should avoid updating during business hours. Even a 10-minute outage during peak time can affect leads, sales, or customer trust.

When to Contact Hosting Support

If deleting the .maintenance file does not resolve the problem, the issue may involve deeper server or file permission problems. Hosting support can check error logs, server timeouts, PHP settings, and disk space usage.

Professional help is especially useful when:

• The .maintenance file is not visible but the message remains.
• The website shows a different error after the file is removed.
• The WordPress dashboard cannot be accessed.
• Updates fail repeatedly.
• The site is an ecommerce, membership, or high-traffic website where downtime is costly.

FAQ

Why does WordPress say “It is temporarily unavailable due to maintenance”?

This message appears when WordPress enters maintenance mode during an update. If the update is interrupted, the temporary .maintenance file may remain and keep the message visible.

How long should maintenance mode last?

Normal maintenance mode usually lasts less than a few minutes. If the message remains for more than 10–15 minutes, the site is probably stuck.

Is deleting the .maintenance file safe?

Yes, deleting the .maintenance file is generally safe when WordPress is stuck in maintenance mode. It is a temporary file created during updates.

What if the .maintenance file cannot be found?

The file may be hidden. The administrator should enable hidden files in the hosting file manager or FTP client. If it still does not appear, caching or a server-level issue may be involved.

Can visitors see the website while this error is active?

No. Visitors usually see only the maintenance message until the issue is fixed or the temporary maintenance file is removed.

How can the error be avoided during future updates?

The safest approach is to back up the site, update items individually, avoid peak traffic hours, and use a staging site for major changes.