WordPress Stuck In Maintenance Mode? Here’s What It Means & How To Prevent It

You update a plugin, theme, or WordPress itself, and your site suddenly goes offline. Visitors now see one line: “Briefly unavailable for scheduled maintenance. Check back in a minute.“

The minute passes, the message stays, and while it’s showing, nobody can reach your site. This is WordPress stuck in maintenance mode.

It usually means an update didn’t finish cleanly, so WordPress never switched your site back on. It’s often quick to fix. But clearing the message only gets your site online again; it doesn’t repair the failed update, and if you skip that step, the problem can return.

This guide explains maintenance mode, why your site gets stuck, and how to fix WordPress maintenance mode one step at a time. You also learn what to check once your site is live, and how to stop this recurring.

You don’t need to be a developer to follow this guide. You only need access to your site’s files through your hosting File Manager or FTP, and we’ll show you where to look.

KEY TAKEAWAYS

• Maintenance mode is automatic during updates and clears on its own once they finish.
• A stuck website means the .maintenance file was left behind in your root directory.
• Common causes: interrupted updates, server timeouts, bulk updates, and compatibility clashes.
• Fix it by deleting the .maintenance file, then clearing every cache.
• Removing the file restores access only. You need to rerun the failed update on its own and test your key pages afterwards.
• To prevent a WordPress maintenance mode error, back up first, update one item at a time, and avoid busy hours.

What Is WordPress Maintenance Mode?

WordPress maintenance mode is a temporary state that takes your site offline while it installs updates to plugins, themes, or the core. It isn’t a fault; it’s a built-in safety feature that WordPress switches on and off automatically. Replacing old files with new ones takes a moment, and a visitor who loads a page mid-update could encounter a broken layout or an error message. When this happens, WordPress pauses the site until the new files are in place.

In a normal update, that pause lasts only a few seconds, which is why most people never see it. You tend to notice maintenance mode only when it doesn’t clear.

Behind the scenes, WordPress manages this with a single file. The moment an update starts, it writes a temporary file called .maintenance into your site’s root directory, the folder that also holds wp-config.php, wp-admin, and wp-content. While that file sits there, WordPress displays the following maintenance message to everyone instead of your pages:

Once the update finishes, it deletes the file automatically and your site loads as normal.

IMPORTANT:

The name starts with a full stop (.), which makes .maintenance a hidden file. It won’t appear in your folders unless hidden files are switched on, and that’s the first thing you will sort out when you are looking for it.

Why WordPress Gets Stuck in Maintenance Mode

Normally, WordPress deletes the .maintenance file the moment an update finishes. Your site gets stuck when something prevents it from loading, so the file stays there, and the message keeps displaying. Here are the most common reasons:

Interrupted or Incomplete Updates

This is the most common cause. If an update stops partway through, WordPress never reaches the point where it removes the .maintenance file. Closing the browser tab, clicking away to another page, or dropping your internet connection can all cut the process short.

Core updates rarely fail this way, but when they do, it’s more serious, because they change the files WordPress itself runs on.

Server Timeouts or Limited Hosting Resources

Updates need a little time and memory to run. On shared or entry-level hosting, the server can hit its time limit or run low on memory before the update is done, and the process is stopped early.

Larger sites and resource-heavy plugins make this more likely. If it keeps happening, your site may have outgrown its plan and could run more reliably on VPS hosting for resource-heavy WordPress websites.

Updating Too Many Plugins or Themes at Once

Bulk updates push everything through in a single run. If one item fails or the run times out along the way, everything can stall, leaving your site stuck.

It also hides the cause, since you can’t easily tell which plugin or theme broke. We recommend updating one item at a time. It’s slower, but far easier to sort out when something goes wrong.

Plugin or Theme Compatibility Problems

An update can also fail because the new version doesn’t get on with your WordPress version, your PHP version, or another plugin. When that clash triggers an error mid-update, WordPress may stop before it clears the file.

Outdated or abandoned plugins are frequent culprits, so a WordPress update failed notice often traces back to something that was already behind on its own updates.

Cache Still Showing Old Message

Sometimes the update worked, and the file is already gone, but you or your visitors still see the maintenance message. That’s usually cache at play.

A caching plugin, your server, a content delivery network (CDN), or even your own browser can hold on to a saved copy of the old page. Here, the fix is already in place, and the cache just needs to be cleared for the live site to show through.

Why a Stuck Site Matters for Your Business

WordPress stuck in maintenance mode isn’t only a technical problem. For as long as the downtime lasts, your website cannot do the job you built it for.

Someone who clicks through and meets a maintenance message won’t wait to find out the reason why. Most leave within seconds, and some go directly to a competitor. If it’s their first visit, that’s the impression they are left with.

For many South African businesses, the website is the hub through which everything else runs. It’s where people request a quote, tap to WhatsApp you, click to call, or book a slot.

When the site is down, those routes close with it. A stalled update at 8 pm can quietly cost you every enquiry that would have arrived overnight, long after you have left the office.

If you sell online, the cost is more direct. A buyer can’t reach a product page, add an item to their cart, or check out, so the sale simply doesn’t happen, and a half-filled cart rarely returns.

There’s also a slower cost. A visitor who finds your site down once might let it go. Someone who sees it twice starts to wonder whether you’re reliable, and that doubt is harder to win back than a single lost visit. It matters even more here, where most people browse on their phones, often on mobile data, and expect a page to load on the first try.

If you manage sites for clients, the stakes multiply. One stalled update means a client’s business is offline, and the first thing you receive is a phone call. Across a whole portfolio, a shaky update routine becomes a steady stream of them.

None of this makes a few seconds of maintenance a crisis. It means extended or repeated downtime is worth taking seriously, because the longer it runs, the more it quietly costs you.

Does Maintenance Mode Hurt Your SEO?

Not for a normal update. The pause lasts only seconds, and search engines are built to cope with it.

Here’s why. While WordPress is in maintenance mode, it doesn’t tell search engines that your page is gone. It returns a status called 503, which means temporarily unavailable; check back soon. Googlebot reads that, backs off, and tries again later. A short outage of this type rarely leaves a mark.

The risk starts when downtime drags on or keeps repeating. If your site continually returns that 503, search engines slow down how often they crawl it while they wait for it to recover. But when left unresolved for days rather than minutes, the pages they can’t reach can be dropped from the index.

Once a page falls out of the index, it stops appearing in results, and the traffic it brought in goes with it. A site that breaks on update after update sends a similar signal over time that it can’t be counted on to stay up.

So, the SEO question really comes down to two things:

1. How long the downtime lasts?
2. How often it happens?

A few seconds during a clean update is nothing to worry about. A site stuck for a long stretch, or one that keeps failing every time you update, is where the damage is. It’s another reason to clear a stuck site quickly and stop it recurring.

How to Fix WordPress Stuck in Maintenance Mode

Fixing this comes down to removing that leftover .maintenance file and clearing anything still displaying the old message. It’s a short job, and you can do it without touching any code. Work through these steps in order:

Wait a Few Minutes First

Before you change anything, give it a moment. A large update on a busy server can take longer than the “minute” the message promises, and if it’s still running, it will finish and clear on its own. WordPress removes the .maintenance file automatically the instant the update completes.

So, wait two or three minutes, then refresh the page once. What you shouldn’t do is refresh repetitively or start another update, as that can interrupt one that’s still working and make things worse.

If the message is still there after about five minutes, it isn’t going to clear by itself, and it’s time to step in.

Access Your Website Files

To remove the file, you need to get into your site’s files. There are two ways in, and either works:

• The quickest method is to use your hosting File Manager, found in your control panel. There’s nothing to install, and you can be in within a minute.
• The other option is an FTP or SFTP client, an app on your computer that connects to your files, with FileZilla and WinSCP being two common ones. Use these if you already have it set up or simply prefer it.

Have your login details ready before you start. For File Manager, that’s your control panel login. For FTP or SFTP, you need the host, username, password, and port from your hosting account. For step-by-step instructions, see:

• How to login to control panel (cPanel) and
• How to find FTP details in your control panel (cPanel).

NOTE:

While your site is in maintenance mode, the WordPress dashboard is usually also blocked. That’s why file access is the reliable way in, rather than trying wp-admin.

Find Your WordPress Root Directory

Once you’re in, open your site’s root directory. This is the folder that holds all your WordPress files.

If you’re a Domains.co.za client, click public_html. Be aware that some hosting providers name it www. And if your site runs on an add-on domain or a subdomain, its files may reside in a subfolder or at a different path. Go with the files you can see, not the folder name.

Show Hidden Files

Remember that .maintenance starts with a full stop, which makes it hidden. Before you can find it, you need to turn on hidden files, or it won’t appear.

Here’s how to do it on File Manager:

1. Click Settings near the top corner.
2. Tick Show Hidden Files (dotfiles).
3. Click Save.

Here’s how to do it using FileZilla:

1. Connect to your web server.
2. Click Server.
3. Choose Force showing hidden files.
4. Once that’s on, the file list will refresh and any hidden files, including .maintenance, will appear.

Delete .maintenance File

Now find .maintenance in the root directory, right-click it, and choose Delete. That’s the entire job. Removing it lifts the lock, and your site should return online immediately.

There are two things to keep in mind:

1. Delete only this one file. Leave wp-config.php, the wp- folders, and everything else exactly as they are, because those files run your site.
2. Deleting .maintenance will get your pages loading again, but it doesn’t repair the update that failed in the first place. Your site is back, but the original problem may still be sitting under the surface, which is why the below sections matter.

Clear Your Cache & Retest

If the message is still showing after you’ve deleted the file, don’t panic and don’t delete anything else. This is almost always the cache serving a saved copy of the old page. In this case, you just need to clear the cache, so the live site shows through.

Clear it in this order:

1. Your caching plugin first if you use one.
2. Then any server cache from your control panel.
3. Follow this with your CDN if you run one.
4. Finally, your own browser cache.

What to Check After You Remove the .maintenance File

Your site is loading again, but that’s only half the story. Deleting the file lifted the lock; it didn’t finish the update that stalled. So, before you continue, ensure the update went through, and nothing broke on the way. These few checks take a couple of minutes and save you a nasty surprise later.

Check Your WordPress Dashboard

Now that you can reach it again, login to your dashboard and go to Updates. Look at the plugin, theme, or core version that was busy when things stalled.

If it still shows an update as available, it didn’t complete, and you should run it again, but on its own this time. WordPress also sometimes shows a notice about a failed update at the top of the screen, so read anything it flags before continuing.

Check Plugin or Theme That Was Updating

Next, look at the exact item that was updating. For a plugin, open Plugins, check its version against the latest, and confirm it’s still active. For a theme, do the same under Appearance → Themes.

Then open a page that uses it and ensure that feature still works. An update can install and still misbehave if it doesn’t get on with your setup, and this is usually where that shows.

Test Key Site Functions

Don’t stop at the homepage loading. Click through the parts people really use: your menus, search, and any contact or enquiry form, and send a test through to be sure it arrives.

If you run an online store, open a product page, add an item to the cart, and go to checkout. If you take bookings, run a test one.

Then, check this all on your phone, as most visitors are on mobile and a layout that has slipped is easy to miss on a computer. It’s far better that you find a broken form than a customer does.

Review Your Error Logs

If something is still off, your error log will usually tell you why. It records plugin, theme, and PHP errors, so a failed update often leaves a clear trail pointing to the file or plugin responsible.

You’ll find logs in your hosting control panel, or you can set them up by following our guide on how to configure WordPress error logs. For a closer look while you test, WordPress debug mode shows errors as they occur.

On a live site, switch it on only while you’re checking and turn it off again afterwards, so visitors never see the messages.

What to Do If Deleting .maintenance Doesn’t Fix It

Most of the time, removing the file is enough. Sometimes you delete it, and the site still won’t load, showing a blank page or a critical error message instead of your homepage.

That means the failed update left a deeper problem, and the item that was updating is your first suspect. Here’s where WordPress troubleshooting goes a step further:

Disable Plugin That Was Updating

Your dashboard is probably still out of reach, so do this through the same file access you used to remove the .maintenance file.

1. Open the wp-content/plugins folder.
2. Find the folder named after the plugin that was updating.
3. Rename it, adding something to the end so WordPress can’t load it, for example changing seo-plugin to seo-plugin-off.

That switches it off. If your site returns, that plugin was the cause. To rule out plugins altogether, rename the entire plugins folder, which turns them off immediately.

Switch to a Default Theme Temporarily

If a theme update caused it, the fix is much the same. In wp-content/themes, rename the folder of your active theme. WordPress then falls back to a default theme, one of the Twenty Twenty-Something themes, if one is still installed.

If your site loads on the default theme, your own theme is the problem; you can reinstall it or restore its files. It’s worth keeping a default theme on your site for exactly this reason.

Use WordPress Recovery Mode

If you’d rather not rename folders, WordPress may have already stepped in. When it detects a critical error, it emails a special recovery link to your admin address.

Open that email and click the link to access a protected version of your dashboard, where the broken plugin or theme is paused, allowing you to deactivate or replace it cleanly.

It’s a tidier route than editing files when it’s on offer. Our guide to WordPress recovery mode covers it in full.

Restore a Recent Backup

If none of that works, or the update left files half-written, rolling back is the cleanest fix. Restoring a recent backup returns your site to how it was just before the update, files and database together.

You will lose anything added since that backup, so it’s a step to weigh, but on a broken site it’s often faster than hunting for the fault. Here’s how to back up your WordPress site, so you’ve always got one ready.

Contact Your Host or a Developer

Sometimes, the problems need another pair of hands. If your site still shows a critical error or you encounter a WordPress 500 internal server error, your logs point to PHP issues you can’t place, or it’s a store or booking site losing money by the minute, ask for assistance rather than guessing.

Hosting support can check things at the server level, and a developer can go into the code.

How to Prevent WordPress Getting Stuck in Maintenance Mode

Getting your site back is one thing. Stopping it from recurring is what saves you the real trouble. Nearly all the causes we’ve covered can be avoided with a few simple update habits, and none of these take long to build.

Back Up Before Every Update

Make a full website backup every time before you update anything. That involves your files and your database together, since a WordPress site needs both to work.

If an update goes wrong, you’ve got a clean copy to roll straight back to, and a problem that could have taken hours of troubleshooting takes a few minutes to fix. Many hosts, including Domains.co.za, run automatic backups, but take your own before a big change rather than assuming one is there.

Test Major Updates on a Staging Site

A staging site is a private copy of your live site where you can try updates safely first. Run the update there, check nothing breaks, and only then repeat it on the live site. If you don’t have a staging site, read our guide on how to set up a WordPress staging site.

It’s worth the extra step for any site you can’t afford to go down: an online store, a site built to attract enquiries, a membership or booking site, or anything with steady traffic. You will catch the clash on the copy, where no visitor ever sees it.

Update One Item at a Time, & Keep Updates Regular

Update plugins and themes one at a time and let each finish before starting the next. It’s slower than a bulk run, but if something fails, you know exactly which item did it.

Keeping to a regular routine matters just as much. Updates that pile up over months become a large, risky batch, while small, frequent ones are far easier to manage and far less likely to stall.

Check Compatibility & Changelogs First

Before you update, take a moment to check that the item still suits your site. On the plugin or theme page, check whether it supports your version of WordPress and PHP, then read the changelog and the developer’s note on what’s changed.

If it flags a known issue or hasn’t been updated in a long time, hold off and wait for a stable release or ask the developer. A two-minute check now will save a broken update later.

Update During Quiet Hours & Don’t Interrupt the Process

Choose a low-traffic window for updates, an evening or early morning when few people are on your site, so any brief downtime affects as few visitors as possible.

Once an update starts, let it run. Don’t close the tab, click away, or put your computer to sleep, because cutting it off partially is one of the quickest ways to leave the site stuck. Give it the moment it needs to finish cleanly.

Choose Reliable WordPress Hosting

Good hosting quietly prevents a lot of this. Updates need enough memory and time to run, and a stable server with sensible resources is far less likely to stop one halfway.

Fast, dependable file and database performance helps updates finish as they should. If your site is growing or update failures keep cropping up, solid WordPress hosting in South Africa built for the job gives your updates the capacity to complete without stalling.

Maintenance Mode vs Maintenance Mode Plugin

These share a name, but they aren’t the same thing, and it helps to know which one you’re dealing with.

• The maintenance mode covered in this guide is automatic. WordPress switches it on by itself during an update, holds the site for a few seconds, then switches it off. You never asked for it, and when it sticks, it’s a fault to fix.
• A maintenance mode plugin is the opposite. It’s something you turn on deliberately. When you’re redesigning your site, setting it up, or making big changes, a plugin allows you to show visitors a tidy “under maintenance” or “coming soon” page instead of a half-finished site. Popular options include WP Maintenance Mode and SeedProd. You decide when it’s on and off; you can brand the page and add a way to reach you, and visitors see something intentional rather than a bare system message.

So, one is WordPress protecting an update on its own, and the other is you choosing to pause your site on your terms. If yours is stuck after an update, it’s the automatic type, and the earlier steps are what you need.

Extra Care for WooCommerce & Online Stores

An online store has more moving parts that can break, so a stuck update deserves extra caution. Alongside your normal pages, a store runs product pages, a cart, a checkout, and a live link to a payment provider. If maintenance mode catches a buyer mid-purchase, the sale drops at the worst possible moment, and someone entering card details on a page that stalls won’t try a second time.

Stores also carry more weight behind the scenes. WooCommerce and its extensions update often, and those updates tend to be larger, which makes a timeout or a clash more likely than on a simple blog. Your orders and customer records are in the database as well, so a half-finished update has more it can disturb.

This is where the earlier habits matter most. Back up before you update, first test store and extension updates on a staging copy, and keep updates clear of busy trading hours or a sale. After any update, put a test order through to the end so you catch a broken checkout before a customer does.

What South African Businesses Should Keep in Mind

If you’re running a site in South Africa, a few local realities make a stable update routine worth the effort.

Protect Your Leads, Calls, WhatsApp Enquiries & Bookings

For many local businesses, the website is where the day’s work comes from. People request a quote, tap through to WhatsApp, click to call, or book a slot, and much of this often lands outside office hours.

A site that’s down overnight or over a weekend can quietly cost you enquiries you’ll never know existed. The answer is timing: update in a quiet window that you’ve chosen, clear of your busiest trading hours and any campaign you’re sending traffic to.

If you manage client sites, that predictable routine matters even more, because a stalled update means their business is offline and the call comes to you.

Keep Your Site Stable Through Load-Shedding

Load-shedding already interrupts plenty of local businesses, so your website should be the channel that keeps working when other things stop. There’s a direct link worth knowing: if the power or your internet drops mid-update, that update is cut off, and an interrupted update is one of the main reasons a site ends up stuck.

So, update only when you have stable power and a reliable connection behind you, whether that’s a UPS, a backup line, or a slot clear of scheduled load-shedding. Let it finish before anything can pull the plug.

Handle Backups, Logs & Data Responsibly

Troubleshooting a stuck site can put you near personal information without you noticing.

• Backups contain customer and order data.
• Logs can contain email addresses.
• Form entries and account details are personal too.

Under South Africa’s POPIA, this information should be handled with care. So, keep backups and logs somewhere secure, don’t paste them into public forums, and when you share files to get assistance, send them only to your hosting support or a developer you trust.

NOTE:

This isn’t legal advice, just sensible handling that keeps personal data where it belongs while you fix the problem.

Common Mistakes When Fixing Maintenance Mode

Most stuck sites are fixed in minutes. These are the slips that turn a quick job into a long one, so it’s worth a quick scan before you start:

• Deleting the wrong file, when .maintenance is the only one that should go.
• Forgetting to switch on hidden files, then not finding .maintenance at all.
• Assuming the update worked just because the site loads again.
• Skipping the cache, so the old message lingers after the fix is done.
• Firing off another bulk update immediately, instead of one item at a time.
• Ignoring compatibility warnings and updating anyway.
• Never checking the error logs when something still seems off.
• Troubleshooting with no backup to fall back on.
• Waiting too long to get assistance on a site that’s losing money.
• Mixing up automatic maintenance mode with a maintenance plugin you switched on yourself.

Post-Fix Checklist

Once your site is back, run through the following to confirm the fix held, and that nothing has been left broken:

• The .maintenance file is removed.
• Your homepage loads normally.
• You can login to the admin dashboard.
• You’ve found the update that failed.
• You have rerun that update on its own.
• Every cache is cleared.
• Your forms work, and submissions come through.
• Checkout works if you sell online.
• The mobile layout looks correct.
• You’ve reviewed the error logs.
• You have taken a fresh backup after the fix.
• Uptime monitoring is switched on.

When to Ask Domains.co.za Support

Knowing when to ask for assistance saves time and money. Reach out to Domains.co.za support or a trusted developer when:

• The dashboard is still locked even after you’ve deleted the file.
• The .maintenance file is gone, and caches have been cleared, but the message still appears.
• A plugin, theme, or core update failed and won’t complete.
• The site shows a 500 or critical error.
• Your logs point to PHP errors you can’t place.
• It’s a store or other business-critical site that’s losing money while it’s down.
• You’re unsure where your backups are or how to reach your files.
• The same problem keeps returning.

That last one matters most. A site that sticks on update after update has an underlying cause worth tracing, rather than clearing by hand each time.

Final Thoughts

Most of the time, WordPress stuck in maintenance mode looks worse than it is. Removing the .maintenance file lifts the lock, clearing your cache shifts the old message, and your site returns. The part you shouldn’t skip is the failed update behind it. Restoring access and repairing the update are two different jobs, and leaving the second undone is what turns a one-off into a pattern of downtime.

So, clear the site, then check what stalled, run that update cleanly on its own, and put the prevention habits in place: back up first, update one item at a time, and keep them regular. Do that, and this will stop being something that catches you out.

A lot of it also comes down to where your site sits. Keep your WordPress website easier to maintain and quicker to recover with reliable WordPress Hosting from Domains.co.za, backed by secure infrastructure, practical local support, and hosting built for growing South African websites.

Power Up Your Site: How to Install a WordPress Plugin

VIDEO: Power Up Your Site: How to Install a WordPress Plugin

FAQS

Other Blogs of Interest

• Your WordPress Header Does More Than Sit At The Top Of The Page
• Deleting Unused WordPress Themes Keeps Your Website Cleaner, Safer, And Easier To Manage
• Disabling xmlrpc.php Can Reduce a Common WordPress Security Risk – If Your Site Does Not Need It
• The WordPress get_post_meta Function Helps You Turn Custom Fields Into Dynamic Content
• The wp_get_attachment_image Function Makes WordPress Image Output Cleaner & More Reliable