Your WordPress website was working perfectly yesterday, but today it suddenly stopped working. Maybe you are seeing a blank white screen, a critical error message, a 500 Internal Server Error, or a website that refuses to load.
This situation can be stressful, especially if your website generates leads, publishes content, or sells products.
The good news is that many WordPress problems can be diagnosed without rebuilding the entire website. The key is to identify what changed, protect your existing data, and troubleshoot the problem in the right order.
In this guide, you will learn what to check first when your WordPress website suddenly stops working, how to identify common causes, and how to restore your website safely.
1. Check Whether Your Website Is Down for Everyone
Before changing WordPress settings, determine whether the problem affects everyone or only you.
Sometimes a website appears broken because of a local internet connection, browser cache, DNS issue, or temporary network problem.
What to check first:
- Open your website in a private or incognito browser window.
- Try accessing it from another device or network.
- Check whether both the homepage and individual pages are affected.
- Test your website using a service such as Down for Everyone or Just Me.
- Check your hosting provider’s status page for reported outages.
If the website works on another device, the issue may be related to your browser, network, or DNS cache rather than WordPress itself.
If it is unavailable everywhere, continue with the next steps.
2. Look for a WordPress Critical Error
One common problem is the WordPress message:
“There has been a critical error on this website.”
This often indicates a PHP error caused by a plugin, theme, custom code, or an incompatible software update.
In some cases, WordPress sends an administrative recovery email containing details about the error and a special recovery-mode link.
How to troubleshoot it:
- Check the administrator email address associated with your WordPress website.
- Look for a critical error notification from WordPress.
- If a recovery-mode link is provided, use it to access the dashboard safely.
- Identify the plugin or theme mentioned in the notification.
- Deactivate or update the suspected component after creating a backup, where possible.
If you cannot access the dashboard, you may need to deactivate a plugin through your hosting file manager or SFTP.
Avoid deleting WordPress core files or reinstalling everything before identifying the cause.
3. Check Whether a Plugin or Theme Update Broke the Website
A website can stop working immediately after a plugin update, theme change, or WordPress core update.
This may happen when two plugins conflict, a theme uses incompatible code, or a component is not compatible with the current PHP version.
What you should do:
- Think about which plugins or themes were updated most recently.
- Check whether the problem started immediately after an update.
- If possible, reproduce the issue on a staging website.
- Deactivate the suspected plugin and check whether the website recovers.
- Update or replace the incompatible component after confirming the cause.
If the dashboard is inaccessible, plugins can sometimes be deactivated by renaming their individual folders through your hosting file manager or SFTP.
Be careful when changing plugin folders, especially on an online store or membership website. Disabling a plugin can affect checkout, forms, or other important functionality.
4. Investigate a 500 Internal Server Error
A 500 Internal Server Error indicates that the server encountered a problem it could not handle. The message alone does not identify the exact cause.
Possible causes include:
- A plugin or theme triggering a fatal PHP error.
- Incorrect server or rewrite configuration.
- PHP memory exhaustion.
- File permission problems.
- Hosting resource limits.
- A server-side configuration issue.
How to fix it:
Start by checking your hosting error logs. They may identify the PHP file, plugin, or server component responsible.
If the problem started after a configuration change, review that change first. You can also ask your hosting provider to investigate server errors and resource limits.
Do not immediately replace your .htaccess file or change file permissions without a backup. These actions can introduce additional problems.
5. Fix the White Screen of Death
Sometimes a WordPress website displays a completely blank page without any useful error message. This is commonly known as the White Screen of Death.
Possible causes include PHP fatal errors, plugin conflicts, theme issues, or exhausted server resources.
Try these troubleshooting steps:
- Check whether the WordPress dashboard still works.
- Review your hosting error logs.
- Disable the suspected plugin or switch to a default WordPress theme if you can do so safely.
- Check whether your hosting account has reached its PHP memory or resource limits.
- Test the website again after each change.
If you need more technical information, WordPress debugging can help identify the error. However, debug logs may contain sensitive information, so keep them private and disable public error display on a live website.
6. Check Your Hosting Account and Server Resources
Sometimes the issue has nothing to do with your WordPress theme or plugins.
Your hosting account may have run out of disk space, reached CPU or memory limits, or experienced a server outage.
This is especially common on websites experiencing sudden traffic increases or running resource-intensive applications.
Check the following in your hosting control panel:
- Available disk space and inode limits.
- CPU and memory usage.
- PHP version and configuration.
- Database service status.
- Server error logs.
- Hosting provider notifications.
If resources are exhausted or the server is experiencing an outage, contact your hosting provider before making major changes to WordPress.
Upgrading your hosting plan may help if the website consistently exceeds its allocated resources, but first confirm that resource limits are actually causing the problem.
7. Make Sure Your Website Database Is Working
WordPress relies on a database to store posts, pages, user accounts, settings, and other information.
If WordPress cannot connect to the database, your website may display an error such as:
“Error establishing a database connection.”
Common causes include incorrect database credentials, an unavailable database server, exhausted database resources, or database configuration problems.
How to troubleshoot it:
- Check whether your hosting provider reports a database outage.
- Verify the database settings in
wp-config.phpwithout exposing the file publicly. - Check whether the database user still has the correct permissions.
- Review hosting logs for database connection errors.
- Ask your hosting provider to investigate if the database server is unavailable.
Do not run database repair commands or edit database tables without a backup. A database problem can affect important website content and customer information.
8. Check Whether Your SSL Certificate or Domain Has Expired
Sometimes the website itself is still running, but visitors cannot access it normally because of a domain or HTTPS issue.
For example, an expired SSL certificate may trigger a browser security warning. An expired domain, DNS configuration change, or nameserver problem may also make a website unreachable.
What to check:
- Confirm that your domain registration is active.
- Check whether your SSL certificate is valid.
- Verify your domain’s DNS records and nameservers.
- Confirm that the website’s HTTPS configuration is correct.
- Check whether recent DNS changes have propagated.
If the domain or certificate has expired, renew or reconfigure it through the appropriate provider.
Avoid disabling HTTPS security warnings as a workaround. The underlying certificate or configuration issue should be fixed instead.
9. Restore Your Website From a Backup if Necessary
If your website broke after a major update, failed migration, or configuration change, restoring a known-good backup may be the fastest recovery option.
However, restoring a backup can overwrite newer content, orders, customer information, or other changes made after the backup was created.
Before restoring:
- Confirm the backup date and what it contains.
- Make a copy of the current website files and database if possible.
- Identify how much new content or transaction data could be lost.
- Restore to a staging environment first when practical.
- Test the website before making it publicly accessible again.
For WooCommerce stores and membership websites, pay special attention to recent orders, user registrations, and account changes.
A backup should be a recovery tool, not a reason to skip diagnosis. Once the website is restored, investigate the original cause to avoid repeating the same failure.
10. Enable WordPress Debugging to Find the Real Cause
If the previous steps do not reveal the cause, WordPress debugging can provide more information.
WordPress supports debugging options that can help developers identify PHP errors and warnings. These can be particularly useful when the website displays a blank screen or a generic critical error.
For a controlled troubleshooting session, the following settings can be used in wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );If these constants are already defined, edit the existing entries rather than adding duplicates. On a live website, follow your hosting provider’s security guidance and keep debug logs private.
After reproducing the problem, review the generated log file, typically wp-content/debug.log, if logging is enabled and the server permits it.
Look for the earliest relevant fatal error and the file or component mentioned in the log.
Important: Debug logs can contain sensitive paths or other information. Do not expose them publicly, and disable debugging when troubleshooting is complete.
What to Check First: Quick Troubleshooting Checklist
Use this checklist before making major changes to your website.
Recovery checklist
0 of 10 completeTest the website from another device or networkCheck the hosting provider’s status pageLook for a WordPress critical error emailReview recent plugin, theme, and WordPress updatesCheck hosting error logs and resource usageVerify database connectivityCheck domain, DNS, and SSL statusCreate a backup before modifying filesTest fixes one at a timeVerify forms, login, and checkout after recovery
Common Mistakes to Avoid When Your WordPress Website Breaks
When a website suddenly stops working, rushing into changes can make the situation worse.
Avoid these common mistakes:
- Deleting WordPress core files: This can damage the installation without fixing the original issue.
- Disabling every plugin immediately: This may remove critical functionality and make the root cause harder to isolate.
- Editing configuration files without backups: A small syntax error can prevent WordPress from loading.
- Restoring an old backup without checking new data: Recent orders, posts, and registrations may be lost.
- Ignoring security warnings: A compromised website or expired certificate needs proper investigation.
- Making multiple changes at once: You may not know which change fixed or worsened the problem.
The safest approach is to preserve your current data, identify the error, and apply the smallest change that addresses the cause.
Frequently Asked Questions
Why did my WordPress website suddenly stop working?
Common causes include plugin conflicts, failed updates, PHP errors, hosting outages, database connection problems, expired domains, and configuration changes. Check recent changes and error logs first.
Can I fix a broken WordPress website without a developer?
Many common issues can be resolved through the WordPress recovery mode, hosting control panel, or a known-good backup. However, database failures, security incidents, and complex PHP errors may require professional assistance.
What should I do if I cannot access my WordPress dashboard?
Check your hosting control panel, error logs, and administrative email. If a plugin or theme is responsible, you may be able to disable it through your hosting file manager or SFTP. Back up the site before changing files.
Will updating WordPress fix my broken website?
Sometimes an update fixes a known bug or security issue, but an update can also trigger compatibility problems. Diagnose the cause first and make a backup before updating or rolling back software.
When should I restore a backup?
Restore a backup when you have a verified, known-good version and other recovery options are unsuitable. Consider any data created after the backup before proceeding, especially for online stores.
Final Thoughts
A WordPress website that suddenly stops working does not necessarily need a complete rebuild.
Start by checking whether the website is down for everyone, then investigate critical errors, recent updates, hosting resources, database connectivity, and domain configuration. Keep a backup before making significant changes, and test each fix carefully.
If the problem involves a security breach, lost customer data, or a serious database failure, seek help from your hosting provider or a qualified WordPress developer.
The most important rule is simple: diagnose first, protect your data, and fix the root cause instead of guessing.