It is every website owner's nightmare: your website is offline and you have no idea how to fix it. While hosting outages or hardware failures can happen, many downtime issues are caused by software conflicts, local connection problems, or configuration errors.
This guide provides a checklist to help you determine the cause of the downtime and offers practical steps to resolve it.
If your website fails to load, do not panic immediately; it might just be a network issue rather than a total site failure.
The first step is to confirm whether the website is down for everyone or just for you. Your local device or internet connection could be the culprit, known as a cache issue.
To rule out local issues:
• Clear your browser cache and refresh the page.
• Try a different browser or use an incognito window to bypass stored data.
• Use a different network, such as your smartphone's mobile data instead of Wi-Fi.
• Use an online tool like "Down For Everyone Or Just Me" or GeoPeeker to check how your site appears from other locations.
If the site works through these methods, the issue is local to your computer or internet service provider (ISP).
If the site is down for everyone, the specific error message displayed in the browser will guide your troubleshooting.
• 500 Internal Server Error: This generic error often indicates a server-side problem, such as a corrupted .htaccess file or a plugin conflict.
• Error Establishing a Database Connection: This means your website files cannot communicate with the database, often due to incorrect credentials in your configuration file.
• White Screen of Death (WSOD): A completely blank screen usually indicates a PHP code error or memory exhaustion.
• Connection Timed Out (522/524): These errors often indicate that the server is overloaded or a firewall is blocking requests.
If you see a "Briefly unavailable for scheduled maintenance" message that does not go away, delete the .maintenance file from your site's root directory.
Before making changes to your site files, ensure your hosting service and domain are active.
1. Check your hosting provider's status page. If the provider is experiencing a power issue, network attack, or outage, you may just need to wait.
2. Verify your domain status. Ensure your domain has not expired. If you recently updated your DNS records, propagation can take up to 48 hours, during which the site may appear unavailable.
3. Check for suspension. In some cases, hosting accounts may be suspended due to abuse or spam, which disables email and networking services.
If the server is running but the site is broken, recent changes to themes or plugins are often the cause.
• Deactivate Plugins: If you can access your dashboard, deactivate all plugins. If you cannot access the dashboard, use a File Manager or FTP to rename the plugins folder (e.g., to plugins.disabled) to force deactivation.
• Switch Themes: If a theme update broke the site, switch to a default theme (like Twenty Twenty-One) via your database or dashboard.
• Disable .htaccess: A corrupt .htaccess file can cause 500 errors. Rename this file to .htaccess.disabled and refresh your site to see if it loads.
Always make a backup of your website files and database before troubleshooting or making any changes to prevent data loss.
If you have access to a Virtual Private Server (VPS) or a dedicated server, the machine itself might be offline or overloaded.
• Ping the Server: Use the command line to ping your server's IP address (e.g., ping 1.2.3.4). If it does not respond, the machine might be completely offline.
• Check Resources: If the server is running but slow, check if processes are consuming all CPU or memory resources using commands like top or htop.
• Reboot: A reboot can clear temporary glitches or stop processes that are consuming too many resources.
DNS Propagation The period of time it takes for updates to your domain's DNS records to spread across the internet. This can take up to 48 hours.
500 Internal Server Error A general HTTP status code indicating that the server encountered an unexpected condition that prevented it from fulfilling the request.
Time to Live (TTL) A setting that determines how long servers cache DNS record information. Shorter settings may increase propagation speed.
If your website is down, first determine if the issue is local by testing different devices and networks. If the outage is real, identify the specific error message (such as a 500 error or database connection error) to guide your repairs.
Always check your hosting provider's status page for outages before editing files, and ensure you have a valid backup before attempting to fix plugins, themes, or configuration files.
Understanding systems reduces fear of failure.