Skip to content
Hosting Operations5 min read

Website Down Not Working: 7 Fixes [Solved]

Stop guessing. Fix website down not working errors by checking DNS, disk space, and firewall rules. Secure your server with this audit checklist.

Written by Abdul AbrorTechnical Hosting Support Engineer
a computer screen with the words nothing great is made alone
On this page

TL;DR — Key takeaways

  • Check disk space first; a full partition is the most common cause of sudden site failure.
  • Verify DNS records match the server IP before assuming the web server is broken.
  • Review firewall rules to ensure port 80 and 443 are open for inbound traffic.
  • Inspect web server error logs for specific PHP or module crashes before restarting services.
  • Harden the server by disabling unused modules and restricting file permissions to prevent future outages.

When a site goes dark, panic sets in. But the fix is usually mechanical, not mystical. In support tickets I handled, the usual culprit was a full disk or a misconfigured firewall rule.

This guide walks through the exact steps to diagnose and fix a down site. We focus on security hardening to prevent the next outage from happening.

Threat Model: Why Sites Go Down

Outages rarely happen in a vacuum. They are symptoms of resource exhaustion, configuration drift, or external attacks. A DDoS attack can saturate bandwidth, causing the server to drop legitimate requests. A runaway cron job can fill the disk with logs, triggering a 503 error.

The threat model here is simple: if the server cannot process requests, the site is down. This could be due to CPU spikes, memory leaks, or I/O bottlenecks. Understanding the root cause prevents you from just restarting the service and hoping for the best.

  • Resource exhaustion: CPU, RAM, or disk space limits reached.
  • Configuration errors: Bad DNS, firewall rules, or web server config.
  • External attacks: DDoS, brute force, or malware injection.
  • Application bugs: PHP errors, database locks, or script timeouts.

Audit Checklist: Diagnose the Failure

Start with the basics. Check disk space first. A full disk is the most common cause of sudden failure. Run `df -h` to see usage. If the root partition is over 90%, clear old logs or backups immediately.

Next, verify DNS. Use `dig +short yourdomain.com` to check the IP. If the IP does not match your server, update the DNS record. Wait for propagation if you recently changed it. This step isolates network issues from server issues.

  • Run `df -h` to check disk usage on all partitions.
  • Use `dig +short yourdomain.com` to verify DNS resolution.
  • Check server load with `uptime` to see if CPU is maxed out.
  • Review recent changes to DNS or server configuration.

Hardening Steps: Secure the Server

Once the site is back up, harden the server to prevent recurrence. Disable unused web server modules. Each module increases the attack surface. If you do not use PHP, remove the PHP module from Apache or Nginx.

Restrict file permissions. The web root should be readable by the web user but not writable. Use `chmod 755` for directories and `644` for files. This prevents attackers from uploading malicious scripts if they gain limited access.

  • Disable unused web server modules to reduce attack surface.
  • Set strict file permissions: 755 for directories, 644 for files.
  • Enable fail2ban to block brute force attempts on SSH and FTP.
  • Keep the server OS and web server software updated with security patches.

Verify Configuration: Test the Fix

Do not assume the fix works. Test it. Use `curl -I yourdomain.com` from a different machine to check the HTTP response code. You should see a 200 OK. If you see a 503 or 403, the issue is not resolved.

Check the web server error logs for new entries. If the logs show permission denied errors, correct the ownership. If they show module errors, disable the problematic module. Verification is the only way to confirm the site is truly secure and stable.

  • Run `curl -I yourdomain.com` to check the HTTP status code.
  • Review web server error logs for new errors after the fix.
  • Test the site from a different network to rule out local cache issues.
  • Monitor server load for 24 hours to ensure stability.

Rollback Plan: If Things Get Worse

Before making changes, always have a rollback plan. Back up your configuration files. Copy the current `httpd.conf` or `nginx.conf` to a safe location. If a change breaks the site, you can restore the previous config quickly.

If the site is still down after applying fixes, revert to the last known good state. Restart the web service. If the issue persists, contact your hosting provider for deeper infrastructure support. Do not guess. Data is safer than downtime.

  • Back up configuration files before making changes.
  • Keep a copy of the last known good config for quick rollback.
  • Restart the web service after restoring the config.
  • Contact hosting support if the issue persists after rollback.

Quick troubleshooting checklist

  • Check disk usage with `df -h` and clear logs if usage exceeds 90%.
  • Verify DNS A record points to the correct server IP using `dig` or `nslookup`.
  • Test local connectivity with `curl -I localhost` to isolate network vs. server issues.
  • Review web server error logs for recent crashes or permission denials.
  • Ensure firewall allows inbound traffic on ports 80 and 443.
  • Restart the web service only after backing up current configuration files.
  • Audit file permissions to ensure web root is readable but not writable by the web user.

FAQ

Why is my website showing a 503 Service Unavailable error?

A 503 error usually means the web server is overloaded, under maintenance, or the disk is full. Check your disk space and server load first. If the disk is full, clear old logs or backups to restore service.

How do I check if my DNS is pointing to the correct server?

Use the `dig +short yourdomain.com` command to see the current IP address. Compare this IP with your hosting provider's server IP. If they do not match, update your DNS A record to point to the correct server.

What should I do if the server is running but the site is still down?

Check the web server error logs for specific errors like PHP crashes or module failures. Verify that the firewall is not blocking port 80 or 443. If logs show permission issues, correct file ownership and permissions on the web root directory.