If your WordPress website is down, don’t start changing plugins, restoring backups or editing files at random. First establish what has actually failed. A WordPress site can become unavailable because of a failed update, plugin conflict, hosting problem, database error, expired domain or SSL certificate, or a security issue. The quicker you identify the cause, the quicker you can get the website safely back online.
Need Urgent WordPress Help?
If your business website is down, broken, hacked or showing a critical error, Swart Digital provides emergency WordPress support to diagnose the problem and get your website operational again.
Get Emergency WordPress Support →
1. Check Whether the Website Is Actually Down
First, make sure the problem isn’t limited to your computer or internet connection.
Try opening the website:
- on your phone using mobile data rather than Wi-Fi
- in a private/incognito browser window
- from another internet connection
- using an online website-status checker
If the website loads elsewhere, the problem could be a local cache, network, DNS or IP-blocking issue rather than the website itself. Checking from another connection is also recommended in WordPress.com’s troubleshooting guidance.
If nobody can access it, continue troubleshooting.
2. Look at the Error Message
What you see on screen can provide an important clue.
“There Has Been a Critical Error on This Website”
A WordPress critical error commonly points to a PHP, plugin, theme or compatibility problem.
If WordPress detected the fatal error, the site’s administrator may also have received an email containing more information and a Recovery Mode link.
500 Internal Server Error
This is a server-side error and can have several causes, including plugins, themes, PHP problems or server configuration.
502, 503 or 504 Error
These can indicate a hosting or server availability/resource problem rather than WordPress itself.
“Error Establishing a Database Connection”
WordPress can’t communicate properly with its database. This could relate to the database server, configuration or hosting environment.
Completely Blank or White Page
A blank WordPress website can result from a fatal PHP error, frequently involving a plugin, theme or custom code. Take a screenshot or copy the exact error message before changing anything. It can make diagnosing the problem considerably faster.
3. Think About What Changed Before the Website Went Down
Ask yourself what happened immediately before the problem started.
Did someone:
- update WordPress?
- update a plugin?
- install a new plugin?
- update or change the theme?
- edit website code?
- change the PHP version?
- change hosting or DNS settings?
A recent change is often an important diagnostic clue, particularly when a plugin, theme or WordPress update is involved. If the website stopped working immediately after an update, avoid making five more changes trying to fix it. You can quickly turn one identifiable problem into several.
4. Check Your Hosting, Domain and SSL
Not every WordPress outage is actually caused by WordPress. Check whether your hosting provider is experiencing an outage or whether there are warnings in your hosting account.
Also check that:
- your domain hasn’t expired
- your hosting account is active
- your SSL certificate is valid
- DNS hasn’t recently been changed
An expired domain or DNS problem can make the entire website inaccessible even when WordPress itself is perfectly healthy. If your hosting provider confirms a server-wide outage, changing WordPress plugins won’t solve the problem.
5. Be Careful Before Restoring a Backup
Restoring a recent working backup can sometimes be the quickest route to recovery. But don’t automatically restore an old backup without considering what will be overwritten.
This is particularly important for:
- WooCommerce stores
- membership websites
- booking systems
- websites receiving frequent form submissions
- websites where content or customer information changes regularly
Anything created after the backup may be lost when an older database is restored. If you’re unsure what the restore will overwrite, get technical help before proceeding.
Could the WordPress Website Have Been Hacked?
A website going down doesn’t automatically mean it has been hacked. Plugin conflicts, failed updates, PHP errors and hosting problems are all common causes of WordPress failures.
However, investigate a possible security breach if you also notice things such as:
- unfamiliar WordPress administrators
- unexpected files
- malicious redirects
- spam pages
- security or malware warnings
- unexplained website changes
If there are signs of compromise, simply restoring the website may not solve the underlying security problem. Swart Digital also provides WordPress malware removal where a site has been compromised.
When Should You Stop Troubleshooting It Yourself?
If you’ve identified something simple and know how to safely reverse it, you may be able to restore the website yourself.
But stop experimenting if:
- the website generates enquiries or sales and downtime is costing the business money
- WooCommerce checkout or payments are affected
- you don’t have a reliable backup
- you can’t access WordPress admin
- the website keeps going down again
- you suspect malware or hacking
- you’re unsure what an error means
- you’re about to start changing database or server files
The objective is to get the website working again without creating additional problems or losing data.
What Information Should You Give an Emergency WordPress Developer?
You can speed up troubleshooting by providing:
Your website URL
The developer needs to see the problem.
When it stopped working
Even an approximate time can help.
The exact error
Send a screenshot if possible.
What changed recently
Mention plugin updates, development work, hosting changes or anything else that happened shortly before the failure.
Available access
WordPress, hosting and server access may be required depending on the cause.
The more clearly the problem can be reproduced, the easier it is to start diagnosing it.
WordPress Website Still Down?
A WordPress website can stop working for many reasons. The safest approach is to identify whether the problem is local, hosting-related, WordPress-related or potentially a security incident before making major changes.
If it’s a business-critical website, spending hours trying random fixes can cost more than getting the problem diagnosed properly.
Get Emergency WordPress Support
Swart Digital provides emergency WordPress troubleshooting, repair and website recovery for businesses experiencing urgent website problems.
Whether your website is down, showing a critical error, broken after an update or experiencing another WordPress failure, we can investigate the cause and work on getting it operational again.
Get Emergency WordPress Support →
Frequently Asked Questions (FAQ)
Why is my WordPress website suddenly down?
A WordPress website can go down because of failed updates, plugin or theme conflicts, hosting problems, database errors, expired domains or security incidents. The exact error message and any recent website changes can help identify the cause.
How do I fix the WordPress critical error?
Start by checking the administrator email for a WordPress Recovery Mode notification. If available, it may help identify the plugin, theme or code responsible. Avoid making further changes without a reliable backup.
Can a WordPress website be recovered after a failed update?
Often, yes. Depending on the cause, recovery may involve resolving a plugin conflict, correcting a compatibility issue or restoring affected files. Restoring an older database backup should be approached carefully to avoid losing recent information.
Can I get emergency WordPress support if I cannot access wp-admin?
Yes. WordPress problems can often be investigated through hosting or server access when the WordPress dashboard is unavailable. The access required depends on the nature of the failure.
Will I lose website data when restoring a backup?
Potentially. Restoring an older database backup can overwrite orders, enquiries, bookings or other information created after the backup was taken. This should be assessed before proceeding.
