Skip to content
Hosting Operations5 min read

Website Down: 7 Fixes That Actually Work (2026)

Fix a website down issue fast. Compare DNS, server, and code causes. Use this 7-step checklist to restore uptime in minutes.

Written by Abdul AbrorTechnical Hosting Support Engineer
A blue laptop displaying the WordPress logo on a speckled blue surface
On this page

TL;DR — Key takeaways

  • Check DNS propagation and server status before touching code; 40% of 'down' reports are client-side or DNS issues.
  • A 500 error usually points to PHP syntax errors or permission issues, not server hardware failure.
  • Always create a database and file backup before attempting manual code fixes or database repairs.
  • If the site is down due to resource exhaustion, restart the web server or PHP-FPM pool rather than rebooting the entire VPS.

When a website goes down, the first 10 minutes determine whether you lose customers or just a few minutes of revenue. Panic leads to bad decisions. Calm, structured troubleshooting saves time.

This guide compares the three main causes of downtime: DNS issues, server resource exhaustion, and application errors. You will learn how to diagnose each one and apply the correct fix without breaking things further.

Step 1: Verify DNS and Domain Status

Before touching the server, confirm the domain is actually pointing to the right place. In support tickets I handled, the usual culprit was a expired domain or a misconfigured A record.

Use a command-line tool to check the current DNS resolution. If the IP address returned does not match your server's IP, the issue is DNS-related, not server-related.

  • Run `dig +short A yourdomain.com` to check the resolved IP.
  • Verify the domain registration status in your registrar's control panel.
  • Check if the DNS TTL is set too high, which delays propagation of fixes.

Step 2: Check Server Resource Usage

If DNS is correct, the problem is likely on the server. High CPU or RAM usage can cause the web server to stop responding. This is common during traffic spikes or after a poorly optimized query.

Log into your hosting control panel or SSH into the server. Look for processes consuming excessive resources. If the server is unresponsive, you may need to use the control panel's 'Restart Server' function.

  • Check CPU and RAM usage in the hosting dashboard.
  • Identify the top processes using `top` or `htop` via SSH.
  • Restart the web server (Apache/Nginx) or PHP-FPM if resources are high.

Step 3: Analyze Error Logs

So what if the server is running fine but the site still shows an error? The logs will tell you exactly what failed. PHP errors, database connection issues, and file permission problems all leave traces in the error log.

Locate the error log file. For Apache, it is often in `/var/log/apache2/error.log`. For Nginx, check `/var/log/nginx/error.log`. Look for the most recent entries matching the time the site went down.

  • Search for 'Fatal error', 'Warning', or 'Database error' in the logs.
  • Note the specific file and line number mentioned in the error.
  • Check if the error occurred after a recent code deployment or plugin update.

Step 4: Compare Application vs. Infrastructure Failures

This is where the comparison matters. Infrastructure failures (server crash, disk full) affect all sites on the server. Application failures (code bug, plugin conflict) affect only your specific website.

If other sites on the same server are also down, it is an infrastructure issue. Contact your hosting provider immediately. If only your site is down, the problem is in your code or configuration.

  • Infrastructure failure: Server unresponsive, all sites affected, high resource usage.
  • Application failure: Server responsive, only your site affected, specific error codes (500, 503).
  • DNS failure: Server and app fine, but domain does not resolve.

Step 5: Safe Fixes and Rollback Procedures

Before making changes, create a backup. This is non-negotiable. A bad fix can make the situation worse. A backup allows you to roll back to a known good state.

For code issues, revert to the previous version of the file. For database issues, restore from a recent backup. For resource issues, restart the service or scale up resources.

  • Backup files and database before making any changes.
  • Revert recent code changes if the error started after a deployment.
  • Restore database from backup if data corruption is suspected.
  • Restart services only after identifying the root cause.

Step 6: Prevent Future Downtime

Fixing the issue is only half the job. Preventing recurrence saves you from the same panic next time. Implement monitoring, automated backups, and code review processes.

Set up uptime monitoring to alert you before customers notice. Use version control for all code changes. Schedule regular database backups and test restore procedures.

  • Implement uptime monitoring with alerts (e.g., UptimeRobot, Pingdom).
  • Use version control (Git) for all code changes.
  • Schedule automated daily backups of files and database.
  • Test backup restore procedures quarterly.

Quick troubleshooting checklist

  • Verify the domain is active and DNS records point to the correct IP address.
  • Check the hosting control panel for server status and resource usage (CPU, RAM, Disk).
  • Review error logs (access.log, error.log) for specific PHP or database errors.
  • Test the site in a private browser window to rule out local cache issues.
  • Check for recent code deployments or plugin updates that may have introduced conflicts.
  • Restart the web server or PHP-FPM service if resources are high but the server is responsive.
  • Restore from a known good backup if the issue persists after basic fixes.

FAQ

Why is my website down but the hosting panel shows 'Online'?

The server is running, but the application layer is failing. Check PHP error logs for syntax errors or database connection failures. A 500 Internal Server Error is the most common symptom in this scenario.

How long does DNS propagation take after fixing a record?

Typically 24-48 hours globally, but often 5-30 minutes for most users. Use a global DNS checker tool to verify propagation status before assuming the fix failed.

Should I restart the server if the website is down?

Only if resource usage is high or the web server process is unresponsive. A restart clears memory and resets connections. Avoid restarting if the issue is a code error, as it will not fix the underlying problem.