Website Down Not Working: 7 Fixes That Actually Work
Fix a website down not working error fast. Check DNS, server status, and code errors with these 7 practical steps for hosting owners.

On this page
TL;DR — Key takeaways
- Check if the server is actually up before blaming the code; a ping or SSH test confirms connectivity.
- DNS propagation delays can take up to 48 hours, so verify records at the registrar level before assuming a local failure.
- A 503 error usually means the web server is overloaded or restarting, not that the site is permanently deleted.
- Always create a database backup before running manual repairs or restoring files to prevent data loss.
- Clearing browser cache and testing in incognito mode rules out local client-side issues before escalating to server logs.
When a site goes dark, the first instinct is to panic. But in support tickets I handled, the usual culprit was rarely a catastrophic hardware failure. It was almost always a misconfigured DNS record, a full disk, or a broken PHP file.
This guide walks through the most common reasons a website appears down and how to fix them. We will move from client-side checks to server-side diagnostics, giving you a clear path to restore service quickly.
Is the Server Actually Down?
Before touching any code, confirm the host is reachable. If the server is offline, no amount of frontend debugging will help. Run a ping command from your local terminal. If you get no response, the issue is at the network or provider level.
If ping works but the site is still down, try SSH. A successful login proves the OS is running. From there, check if the web server process is active. Use systemctl status apache2 or systemctl status nginx to see if the service is running or crashed.
- Ping the server IP to test basic connectivity
- SSH into the host to verify OS uptime
- Check web server service status with systemctl
DNS Propagation and Record Errors
A common cause of 'site down' errors is DNS. If you recently changed hosts or updated records, the new DNS may not have propagated globally yet. This is not a server issue; it is a routing delay.
Check your A record and CNAME record at your domain registrar. Ensure the IP address matches your current server. If you just changed the IP, wait for the TTL to expire. You can force a local check using dig +short yourdomain.com to see what your local resolver is returning.
- Verify A record points to the correct server IP
- Check CNAME records for subdomains
- Use dig or nslookup to test local DNS resolution
Web Server Errors and 5xx Codes
If the server is up and DNS is correct, look at the HTTP status code. A 503 Service Unavailable often means the web server is overloaded or restarting. A 500 Internal Server Error points to a code or configuration issue.
Open the error log file. For Apache, this is usually /var/log/apache2/error.log. For Nginx, it is /var/log/nginx/error.log. Look for the most recent entries. You will often see 'Permission denied' or 'Syntax error' messages that point directly to the broken file.
- Check HTTP status code in browser developer tools
- Review /var/log/apache2/error.log for Apache
- Review /var/log/nginx/error.log for Nginx
Disk Space and Resource Limits
A full disk is a silent killer. When the filesystem fills up, the web server cannot write session files or logs, causing immediate crashes. Run df -h to check disk usage. If the root partition is at 100%, you need to free space immediately.
Also check CPU and memory usage. A runaway PHP process can consume all available RAM, triggering the OOM killer to terminate the web server. Use top or htop to identify the offending process. Kill it if it is not essential, then monitor for stability.
- Run df -h to check disk usage
- Use top or htop to monitor CPU and RAM
- Clear old logs or temp files to free space
Code and Configuration Syntax Errors
If you recently deployed code, a syntax error in a PHP file or a misconfigured .htaccess can bring the site down. This is common after manual edits. The web server tries to parse the file, fails, and returns a 500 error.
If you have access to the command line, you can validate PHP syntax using php -l filename.php. For Apache, use apachectl configtest. If a syntax error is found, revert the file to the last known good version. Always keep a backup before making manual changes to production files.
- Validate PHP files with php -l
- Test Apache config with apachectl configtest
- Revert recent code changes if errors persist
Client-Side Caching and Browser Issues
Sometimes the site is up, but your browser is showing a cached error page. This happens if you visited the site while it was down and the browser saved the 503 page. Clear your browser cache or test in incognito mode.
If the site works in incognito but not in normal mode, the issue is local. Check for browser extensions that might be blocking requests. Disable ad-blockers or privacy extensions temporarily to see if they are interfering with the connection.
- Test site in incognito or private browsing mode
- Clear browser cache and cookies
- Disable browser extensions temporarily
When to Escalate to Support
If you have checked DNS, server status, logs, and disk space, and the site is still down, the issue may be at the provider level. This could be a network outage, a hardware failure, or a security block.
Contact your hosting provider with specific details. Include the time the issue started, the error code, and any relevant log snippets. This helps them diagnose the problem faster. Do not just say 'site is down'; provide the data you have gathered.
- Provide error codes and timestamps to support
- Include relevant log snippets in your ticket
- Ask for a network status check if local tests pass
Quick troubleshooting checklist
- Verify server status via ping or SSH connection
- Check DNS records for correct A/CNAME values
- Review web server error logs for 5xx errors
- Test site in incognito mode to bypass local cache
- Check disk space and CPU usage on the host
- Validate .htaccess or nginx.conf syntax
- Restore from backup if code corruption is suspected
FAQ
Why does my website show 'down not working' even though the server is on?
This usually indicates a DNS misconfiguration, a web server process crash, or a syntax error in the site's configuration files. The server hardware is running, but the web service cannot serve the request.
How long does it take for DNS changes to fix a down site?
DNS propagation typically takes between 15 minutes and 48 hours. You can verify if the change has reached your local resolver using tools like dig or nslookup, but global propagation depends on TTL settings.
Is it safe to restart the web server when the site is down?
Yes, restarting Apache or Nginx is a safe first step if the process is hung. It clears memory leaks and reloads configuration files. Always check the error logs immediately after restarting to see if the service stays up.
Related articles
- Hosting OperationsWebsite Down Not Working: 5 Fixes That Actually WorkFix website down not working errors fast. Compare DNS, server, and code fixes to restore uptime in minutes.
- Hosting OperationsWebsite 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.
- Hosting OperationsWebsite Down Not Working: 7 Fixes That Actually WorkFix a website down not working error by checking DNS, disk space, and PHP limits. Stop downtime fast with these 7 practical hosting troubleshooting steps.
- Hosting OperationsWebsite Down? 7 Fixes That Actually Work in 2026Fix your website down issue fast. Check DNS, server status, and code errors with these 7 practical steps for hosting owners and engineers.
- Hosting OperationsWebsite Down Not Working: 6 Fixes That Actually WorkFix website down not working errors by checking DNS, disk space, and PHP limits. This guide provides 6 practical steps to restore uptime fast.
- Hosting OperationsWebsite Down Not Working: 6 Fixes That Actually WorkFix 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.