Table of Contents
WordPress Website Down? What to Check First
A WordPress website suddenly going down can be stressful, especially when it is generating leads, sales, bookings, or customer enquiries.
The good news is that a broken WordPress website does not necessarily mean that your data is lost or that the entire site needs to be rebuilt. In many cases, the cause is something relatively simple: a failed plugin update, PHP error, hosting issue, database connection problem, expired SSL certificate, or configuration conflict.
The key is to troubleshoot the problem in the right order.
In this guide, we explain what to check first when your WordPress website is down, what common error messages mean, and when it is better to get professional help instead of making further changes yourself.
1. Confirm That Your WordPress Website Is Actually Down
Before changing anything in WordPress, make sure the problem is not limited to your computer, browser, or internet connection.
Try opening the website:
- in another browser;
- in a private or incognito window;
- from your phone using mobile data;
- from another computer or internet connection.
Also try accessing the WordPress administration area directly:
yourwebsite.com/wp-admin/
If the website works from another device or network, the problem may be related to your browser cache, DNS cache, firewall, or local connection rather than WordPress itself.
If the website is unavailable everywhere, continue with the checks below.
2. Check the Error Message
The exact error displayed on the screen is one of the most useful clues when diagnosing a WordPress website.
500 Internal Server Error
A 500 Internal Server Error usually indicates a server-side problem.
Possible causes include:
- a PHP error;
- a faulty plugin;
- a theme conflict;
- corrupted
.htaccessrules; - incorrect server configuration;
- insufficient PHP memory.
If the error appeared immediately after installing or updating something, start there.
502 Bad Gateway
A 502 Bad Gateway error usually means that one server or service did not receive a valid response from another.
Possible causes include PHP processes, hosting infrastructure, a CDN or proxy, server overload, or temporary hosting problems.
503 Service Unavailable
A 503 Service Unavailable error means that the server is temporarily unable to process the request.
This can happen because of:
- excessive server load;
- hosting resource limits;
- WordPress maintenance mode;
- a malfunctioning plugin;
- PHP problems.
504 Gateway Timeout
A 504 Gateway Timeout occurs when a server operation takes too long.
Heavy database queries, malfunctioning plugins, external API requests, insufficient hosting resources, or PHP processes can all contribute to this problem.
Error Establishing a Database Connection
This message means WordPress cannot communicate correctly with its database.
Possible causes include:
- incorrect database credentials;
- unavailable database server;
- corrupted database tables;
- hosting problems;
- incorrect
wp-config.phpsettings.
There Has Been a Critical Error on This Website
The WordPress critical error message usually indicates a fatal PHP error.
Plugins, themes, custom code, or PHP compatibility problems are common causes.
Before making changes, take a screenshot or copy the exact error message. It may make identifying the problem significantly easier.
3. Check Your Hosting
If the entire WordPress website is unavailable, your hosting account should be one of the first places you check.
Look for:
- server outage notifications;
- maintenance notices;
- exceeded CPU or memory limits;
- insufficient disk space;
- PHP errors;
- database server problems;
- account suspension.
If several websites hosted on the same server or hosting account are down simultaneously, the problem is more likely to be related to the hosting environment than WordPress itself.
Server and PHP error logs can also provide valuable information about what happened immediately before the website stopped working.
4. Ask: What Changed Before the Website Went Down?
This simple question can save a lot of troubleshooting time.
Think about what happened shortly before the problem started.
Did you:
- update WordPress?
- update a plugin?
- install a new plugin?
- update the theme?
- modify custom code?
- change the PHP version?
- change DNS settings?
- configure caching or a CDN?
- migrate the website?
- change security settings?
If the website stopped working immediately after one of these actions, investigate that change first.
5. Check WordPress Plugins
Plugin conflicts are a common cause of WordPress problems.
If you can still access WordPress Admin, temporarily deactivate the plugin that was most recently installed or updated.
If /wp-admin/ is inaccessible, plugins can also be disabled through your hosting file manager or FTP/SFTP.
The plugin directory is normally located at:
/wp-content/plugins/
Temporarily renaming the plugins folder prevents WordPress from loading those plugins.
If the website starts working again, a plugin is likely responsible.
You can then restore the directory name and test the plugins individually to identify the problematic one.
Avoid deleting plugins or their data during initial troubleshooting unless you have a reliable backup.
6. Check the WordPress Theme
Themes can also cause fatal errors, particularly after WordPress, plugin, or PHP updates.
Potential causes include:
- outdated theme code;
- incompatible PHP functions;
- child theme modifications;
- custom functions;
- page builder conflicts;
- incomplete updates.
Temporarily switching to a standard WordPress theme can help determine whether your active theme is responsible.
Make sure you have a backup before making significant theme changes.
7. Check the PHP Version
WordPress, plugins, and themes all depend on PHP.
A website that worked yesterday can stop working after a hosting provider changes the PHP version or after an update introduces new PHP requirements.
Check which PHP version your hosting account currently uses.
An old plugin may not work with a newer PHP release, while newer WordPress software may no longer work correctly with an outdated PHP version.
Do not repeatedly switch PHP versions without checking compatibility first, as doing so can introduce additional problems.
8. Check the WordPress Database
If WordPress displays Error establishing a database connection, investigate the database before making unrelated changes.
WordPress database credentials are normally stored in:
wp-config.php
The problem could involve:
- database username or password;
- database hostname;
- unavailable MySQL/MariaDB service;
- corrupted tables;
- hosting resource limits.
If nobody recently changed the website configuration and the database error appeared suddenly, check the hosting provider’s server status before modifying wp-config.php.
9. Check the .htaccess File
On Apache-based WordPress hosting, the .htaccess file controls important URL and rewrite behaviour.
Incorrect or corrupted rules can cause:
- 500 errors;
- redirect loops;
- inaccessible pages;
- broken WordPress permalinks.
Always make a backup of .htaccess before editing it.
Once access to WordPress Admin is restored, WordPress can often regenerate its standard rewrite rules by saving the Settings → Permalinks page again.
Custom .htaccess rules should not be removed permanently unless you know what they are used for.
10. Check SSL and HTTPS
Sometimes WordPress itself is working correctly, but visitors cannot access it because of an SSL problem.
Check whether:
- the SSL certificate has expired;
- automatic SSL renewal failed;
- the domain points to the correct server;
wwwand non-wwwversions are configured correctly;- HTTPS redirects are working;
- your CDN or proxy has the correct SSL configuration.
Browser security warnings can prevent visitors from using an otherwise functional website, so SSL problems should be resolved quickly.
11. Check DNS
DNS determines which server visitors reach when they enter your domain.
A DNS problem can therefore make a perfectly healthy WordPress installation appear offline.
Pay particular attention to DNS if you recently:
- changed hosting providers;
- changed nameservers;
- modified DNS records;
- enabled a CDN;
- moved the website to another server.
DNS changes can also take time to propagate. During that period, the website may work for some visitors but not others.
12. Check Caching and CDN Services
WordPress websites often use several caching layers:
- WordPress caching plugins;
- server-side caching;
- CDN caching;
- reverse proxies;
- browser caching.
An incorrect configuration or stale cache can sometimes make a website appear broken even when WordPress itself is functioning.
Purging the appropriate cache or temporarily bypassing the CDN can help identify the problem.
Be particularly careful when changing caching settings on WooCommerce or other dynamic websites.
13. Check WordPress Debug and Server Logs
When the cause is not obvious, logs are often more useful than guessing.
WordPress debugging and server logs may reveal:
- the exact PHP error;
- the affected PHP file;
- the responsible plugin;
- the responsible theme;
- memory-limit problems;
- database errors.
Debug information should normally be logged rather than displayed publicly on a production website because detailed errors can expose technical information about your server.
WordPress also provides built-in debugging tools that can help identify PHP errors. You can find instructions for enabling debugging in the official WordPress debugging documentation.
14. Restore a Backup When Necessary
If the website broke after an update or modification and repairing it would take longer than restoring a known working version, a backup may provide the fastest recovery route.
A complete WordPress backup should include:
- website files;
- the WordPress database.
However, restoring a backup should not be done blindly.
An e-commerce site, membership site, booking system, or active website may contain new orders, registrations, enquiries, or customer data created after the backup.
Whenever possible, preserve the current data before restoring an older version.
Regular WordPress maintenance: Website Maintenance 2025 – Keep Your Site Secure & Fast
What NOT to Do When Your WordPress Website Goes Down
When a business website stops working, it is tempting to start changing everything.
That can make the original problem much harder to diagnose.
Avoid immediately:
- reinstalling WordPress;
- deleting plugins;
- deleting the database;
- replacing the theme;
- modifying unfamiliar server files;
- changing multiple settings simultaneously;
- restoring an old backup without checking what data will be lost.
Instead, make one controlled change at a time and check the result.
Common website mistakes: Website Mistakes 2025 – Top Errors & How to Avoid Them
WordPress Website Down: Quick Troubleshooting Order
If your WordPress website is down, use this order:
- Confirm the website is unavailable to other users.
- Record the exact error message.
- Check your hosting and server status.
- Identify anything that changed recently.
- Check server and PHP error logs.
- Test recently updated plugins.
- Check the active theme.
- Check PHP compatibility.
- Check the database.
- Check
.htaccess. - Check SSL and DNS.
- Check caching and CDN configuration.
- Restore a known working backup if necessary.
Following a structured troubleshooting process reduces the risk of turning a relatively small WordPress problem into a much larger one.
When Should You Get Professional WordPress Help?
Professional website repair may be the safer option when:
- both the website and WordPress Admin are inaccessible;
- you repeatedly receive 500 or critical errors;
- you cannot identify the faulty plugin or theme;
- the database appears damaged;
- the website may have been compromised;
- an update caused multiple problems;
- WooCommerce orders or customer data could be affected;
- you do not have a reliable backup;
- downtime is costing your business enquiries or sales.
The goal should not simply be to make the error disappear. The underlying cause should be identified so that the same problem does not return.
Need Help With a Broken WordPress Website?
If your WordPress website is down, displaying a critical error, or stopped working after an update, Verto.rocks can help diagnose and repair the problem.
Our website repair service can help with WordPress errors, plugin and theme conflicts, PHP problems, failed updates, database issues, SSL problems, redirects, configuration errors, and other technical website failures.
Visit our Website Repair page to tell us what happened and get help with your website.
Frequently Asked Questions
Why is my WordPress website down?
If your WordPress website is down, the cause could be a hosting outage, plugin or theme conflict, PHP error, database problem, failed update, DNS issue, or SSL configuration error. Start by checking whether the website is unavailable on multiple devices and then review your hosting status and recent website changes.
What should I check first when my WordPress website is down?
When your WordPress website is down, first record the exact error message and check whether your hosting server is online. Next, consider any recent WordPress, plugin, theme, PHP, DNS, or server changes. This can often narrow down the cause quickly.
Can a WordPress plugin cause my website to go down?
Yes. A faulty or incompatible plugin can cause PHP errors, critical errors, redirect loops, or even make the entire WordPress website inaccessible. If the problem started after installing or updating a plugin, temporarily disabling that plugin is a good troubleshooting step.
Why does WordPress say “There has been a critical error on this website”?
A WordPress critical error usually means that PHP encountered a fatal error. Common causes include incompatible plugins, theme code, custom functions, failed updates, or PHP version conflicts. Server error logs can often identify the exact file responsible.
Can I fix a WordPress website that is down without wp-admin access?
Often, yes. Even if /wp-admin/ is unavailable, troubleshooting can still be performed through your hosting control panel, file manager, FTP/SFTP, database tools, and server logs. However, make a backup before modifying website files or the database.
Will restoring a backup fix a WordPress website that is down?
A backup can restore a previously working version of the website, but it does not necessarily explain why the WordPress website went down. The original problem could return if it was caused by a plugin, PHP incompatibility, server configuration, or security issue. Active websites may also lose newer orders, enquiries, or other data when an older backup is restored.
How long does it take to repair a WordPress website?
It depends on the cause. Simple plugin conflicts or configuration errors may be identified quickly, while database corruption, malware, server problems, or multiple conflicting issues can require more investigation. Providing the exact error message and explaining what changed before the problem occurred can speed up diagnosis.
Who can help if my WordPress website is down?
If your WordPress website is down and you cannot identify the cause safely, a professional WordPress repair service can investigate the hosting environment, plugins, themes, PHP errors, database, SSL, DNS, and other potential problems. Verto provides WordPress website repair for businesses that need help getting their website working again.








