Skip to content
Hosting Operations6 min read

Website Down Not Working: 6 Fixes That Actually Work

Fix a website down not working issue by comparing DNS, server, and code causes. Use this side-by-side guide to identify the root cause fast.

Written by Abdul AbrorTechnical Hosting Support Engineer
Server rack with blinking status lights and a network cable connected to a laptop
On this page

TL;DR — Key takeaways

  • Check DNS propagation and domain expiration before assuming server failure, as these are the most common non-technical causes.
  • Use `ping` and `traceroute` to distinguish between local network issues and remote server unavailability.
  • Inspect HTTP status codes (500, 502, 503) to determine if the issue is application-level or infrastructure-level.
  • Verify disk space and memory limits on the hosting server, as resource exhaustion is a frequent cause of sudden outages.
  • Review recent code deployments or configuration changes, as regressions often trigger immediate site failures.

When a website goes down, the first instinct is to panic. But in support tickets I’ve handled, the culprit is rarely mysterious. It’s usually a broken DNS record, a full disk, or a bad code deployment.

This guide compares the main causes of website downtime and provides practical steps to diagnose and fix them. You’ll learn how to distinguish between network, server, and application issues, and when to escalate to your hosting provider.

DNS and Domain Issues: The Most Common Culprit

Before touching server logs, check the domain. If the domain has expired, DNS records are misconfigured, or propagation is incomplete, the site will be unreachable. This is the fastest issue to rule out.

Use `dig` or `nslookup` to verify the A record points to the correct IP address. If the IP is wrong or missing, update the DNS records in your domain registrar’s control panel. Propagation can take up to 48 hours, but often resolves within minutes.

  • Check domain expiration date in your registrar’s control panel.
  • Verify A record points to the correct server IP.
  • Use `dig +short example.com` to test DNS resolution from your local machine.

Server Resource Exhaustion: Disk, Memory, and CPU

When a server runs out of disk space, memory, or CPU, it can’t serve requests. This is a frequent cause of sudden outages, especially on shared hosting plans. In support tickets, the usual culprit is a full disk from unrotated logs or large file uploads.

Check resource usage via your hosting control panel or SSH. If disk usage is above 90%, clear logs, delete unnecessary files, or upgrade your plan. For memory issues, check for runaway processes using `top` or `htop`.

  • Check disk usage with `df -h` via SSH.
  • Monitor memory and CPU with `top` or `htop`.
  • Clear web server logs if they exceed 1GB.
  • Consider upgrading hosting plan if resources are consistently maxed out.

Application and Code Errors: 500, 502, and 503 Status Codes

If the server is up but the site returns an error, the issue is likely in the application layer. A 500 Internal Server Error indicates a problem with the code or configuration. A 502 Bad Gateway suggests the web server can’t communicate with the application server. A 503 Service Unavailable often means the server is overloaded or under maintenance.

Review web server error logs (e.g., `/var/log/apache2/error.log` or `/var/log/nginx/error.log`) for specific error messages. Check recent code deployments or database migrations. If you made changes, roll back to the last stable version.

  • Check HTTP status code using `curl -I https://example.com`.
  • Review web server error logs for stack traces or error messages.
  • Verify recent code deployments or configuration changes.
  • Roll back to the last stable version if a recent change caused the issue.

Network and Connectivity Issues: Local vs. Remote

Sometimes the site is down for you but not for others. This could be a local network issue, ISP problem, or DNS cache on your device. Use `ping` and `traceroute` to test connectivity to the server’s IP address.

If `ping` fails but the site works for others, the issue is likely local. Restart your router, flush DNS cache (`ipconfig /flushdns` on Windows, `sudo dscacheutil -flushcache` on macOS), or test from a mobile network. If `ping` succeeds but the site is still down, the issue is likely server-side.

  • Test connectivity with `ping <server-ip>`.
  • Use `traceroute <server-ip>` to identify where the connection fails.
  • Flush local DNS cache and restart network hardware.
  • Test site accessibility from multiple networks or mobile data.

SSL and Certificate Issues: HTTPS Failures

If the site loads over HTTP but fails over HTTPS, the issue is likely with the SSL certificate. An expired, misconfigured, or missing certificate will cause browsers to block the connection. This is a common oversight after server migrations or certificate renewals.

Check the certificate’s expiration date and validity using `openssl s_client -connect example.com:443` or an online SSL checker. If the certificate is expired, renew it via your hosting provider or certificate authority. If it’s misconfigured, verify the certificate chain and private key match.

  • Check SSL certificate expiration date.
  • Verify certificate chain and private key match.
  • Renew expired certificates via your hosting provider or CA.
  • Test HTTPS connection using `curl -v https://example.com`.

When to Escalate: Hosting Provider and Infrastructure Issues

If you’ve ruled out DNS, resource exhaustion, application errors, and local network issues, the problem is likely infrastructure-level. This includes server hardware failure, network outages, or data center issues. These require your hosting provider’s intervention.

Contact your hosting provider’s support team with specific details: error codes, timestamps, and steps you’ve already taken. Ask for server status updates and estimated resolution times. If the provider confirms an outage, monitor their status page for updates.

  • Contact hosting provider with specific error details and timestamps.
  • Ask for server status updates and estimated resolution times.
  • Monitor provider’s status page for outage announcements.
  • Consider failover or backup solutions if outages are frequent.

Quick troubleshooting checklist

  • Verify domain registration status and DNS records using `dig` or `nslookup`.
  • Check server resource usage (CPU, RAM, Disk) via hosting control panel or SSH.
  • Review web server error logs for specific error codes or stack traces.
  • Test site accessibility from multiple networks or mobile data to rule out local ISP issues.
  • Confirm SSL certificate validity and expiration dates.
  • Check for recent code deployments or database migrations that may have introduced errors.

FAQ

What is the first step when a website is down?

Verify the domain's DNS records and registration status. If the domain has expired or DNS propagation is incomplete, the site will be unreachable regardless of server health. Use `dig` or an online DNS checker to confirm the A record points to the correct IP address.

How do I tell if the issue is with my hosting provider or my code?

Check the HTTP status code. A 500 Internal Server Error or 502 Bad Gateway often points to application or server configuration issues. A 503 Service Unavailable may indicate resource exhaustion or maintenance. If the server is unreachable via `ping` or `traceroute`, the issue is likely infrastructure-level, such as network downtime or server failure.

Can I fix a website down issue without contacting support?

Yes, for many common issues. Check DNS, verify SSL certificates, review recent code changes, and ensure disk space is available. If the server is unresponsive or you see infrastructure-level errors (e.g., 503 due to resource limits), contact your hosting provider, as these issues require server-level access.