Skip to content
Hosting Operations6 min read

Website Down? 7 Fixes That Work in 2026

Fix a website down issue fast. Check DNS, disk space, and services. This guide lists 7 practical steps to restore uptime and prevent outages.

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 if the domain resolves correctly using a public DNS lookup tool before touching server settings.
  • A full disk partition is the most common cause of sudden website outages on shared hosting.
  • Restarting the web server service often resolves temporary memory leaks or hung processes.
  • Always create a backup of configuration files before making changes to resolve a down site.
  • If the server is unresponsive, contact your hosting provider immediately as it may be a hardware failure.

When a website goes down, every minute of downtime costs money and trust. The cause is rarely mysterious; it is usually one of a handful of common infrastructure failures.

This guide walks through the most frequent reasons a site becomes inaccessible and how to fix them quickly. We focus on practical steps you can take immediately, whether you are a site owner or a support engineer.

Is the Server Actually Down?

Before diving into logs, confirm the server is reachable. Ping the server IP address from a different network. If you get no response, the server might be offline or the network is blocked.

If the ping succeeds but the website is still down, the issue is likely at the application or web server level. This distinction saves time. A dead server requires a hardware or provider intervention. A live server with a down site is a configuration or resource problem.

  • Ping the server IP from a mobile data network to bypass local ISP issues.
  • Check if the SSH port (22) is open. If SSH works, the OS is up.
  • Use a port checker to verify ports 80 and 443 are listening.

Check Disk Space and Inodes

In support tickets I handled, the usual culprit was a full disk. When the partition hits 100% capacity, the web server cannot write logs or temporary files, causing immediate failures.

Run `df -h` to check disk usage. Also check inodes with `df -i`. A full inode count can crash services even if there is free space. Look for large log files, old backups, or uncleaned temp directories.

Delete or rotate large log files carefully. Never delete a log file while the web server is actively writing to it. Use `logrotate` or truncate the file with `> /var/log/apache2/error.log` to free space safely.

  • Run `du -sh *` in the web root to find large directories.
  • Check `/tmp` and `/var/tmp` for leftover files from failed uploads.
  • Clear old cron job outputs if they are accumulating.

Restart Web Server and PHP Services

Sometimes the web server process hangs due to a memory leak or a stuck worker. Restarting the service often resolves this without code changes.

For Apache, use `systemctl restart apache2`. For Nginx, use `systemctl restart nginx`. If you use PHP-FPM, restart that service too: `systemctl restart php-fpm`.

Monitor the service status after restart. If it fails to start, check the service logs immediately. A syntax error in the configuration file will prevent the service from starting.

  • Use `systemctl status apache2` to check if the service is active.
  • Check `journalctl -xe` for recent errors related to the service.
  • Ensure the configuration file syntax is valid before restarting.

Inspect Error Logs for Specific Causes

If the site is down but the server is running, the error log tells the real story. Look for 500 Internal Server Error or 503 Service Unavailable messages.

For Apache, check `/var/log/apache2/error.log`. For Nginx, check `/var/log/nginx/error.log`. The last few lines usually contain the specific error, such as a missing file, permission denied, or PHP fatal error.

Common log entries include 'Permission denied' for file access issues, 'No such file or directory' for missing includes, or 'Segmentation fault' for PHP crashes. Address the specific error rather than guessing.

  • Tail the log file with `tail -f /var/log/apache2/error.log` to see real-time errors.
  • Look for timestamps that match when the site went down.
  • Search for 'PHP Fatal error' to identify code-level crashes.

Verify DNS and SSL Certificates

If the site was working yesterday and is down today, check if the DNS records changed. A typo in the A record or an expired SSL certificate can make the site inaccessible.

Use `dig +short yourdomain.com` to verify the IP address. If the IP is wrong, update it in your DNS provider. For SSL, check the expiration date with `openssl s_client -connect yourdomain.com:443 | openssl x509 -noout -dates`.

An expired SSL certificate does not always take the site down, but it triggers browser warnings that users interpret as a down site. Renew the certificate if it is close to expiration.

  • Check DNS propagation with a global DNS checker tool.
  • Verify SSL certificate validity period and issuer.
  • Ensure the domain is correctly pointed to the hosting server IP.

Check for Resource Limits and DDoS

Shared hosting environments have resource limits. If your site exceeds CPU, RAM, or entry process limits, the server will suspend access to protect other users.

Check your hosting control panel for resource usage graphs. If you are hitting the limit, optimize your code, cache static assets, or upgrade your plan.

A sudden spike in traffic can also trigger a DDoS mitigation. If you see a high number of concurrent connections, consider enabling rate limiting or using a CDN to absorb the traffic.

  • Monitor CPU and RAM usage in real-time with `top` or `htop`.
  • Check the number of active PHP processes with `ps aux | grep php`.
  • Enable caching plugins or server-side caching to reduce load.

When to Contact Your Hosting Provider

If the server is unresponsive to ping, SSH, or control panel access, the issue is likely at the infrastructure level. This could be a hardware failure, network outage, or provider-side maintenance.

Contact your hosting provider immediately. Provide them with the server IP, the time the issue started, and any error messages you have seen. They can check the hardware status and network connectivity.

Do not attempt to reboot the server yourself if you do not have root access. This could cause data loss or extend the downtime. Wait for the provider to confirm the server is healthy before making changes.

  • Gather all error logs and screenshots before contacting support.
  • Provide the exact time the site went down in UTC.
  • Ask if there is any scheduled maintenance or known outage.

Quick troubleshooting checklist

  • Verify domain DNS records point to the correct IP address.
  • Check server disk usage and clear logs or temp files if over 90%.
  • Restart the web server (Apache/Nginx) and PHP-FPM services.
  • Review error logs for specific 5xx errors or permission issues.
  • Test the site from a different network or device to rule out local cache.

FAQ

Why is my website down but the server is online?

The web server process may have crashed or hung. Check the service status and restart Apache or Nginx. Also verify that the document root permissions allow the web server user to read files.

What does a 503 Service Unavailable error mean?

It means the web server is running but cannot handle the request. Common causes include too many concurrent connections, a full disk, or a misconfigured .htaccess file. Check the error log for the specific reason.

How do I fix a website down due to DNS issues?

Update the A record or CNAME in your DNS provider to point to the correct server IP. Wait for propagation, which can take up to 48 hours, though it is often faster. Use a DNS checker tool to verify global resolution.