Website Down Not Working: 7 Fixes That Actually Work
Fix a website down not working error by checking DNS, disk space, and PHP limits. Stop downtime fast with these 7 practical hosting troubleshooting steps.

On this page
TL;DR — Key takeaways
- Check DNS propagation and local host file overrides before assuming server failure.
- Verify disk usage and inode counts, as full storage is a common cause of sudden downtime.
- Review PHP memory limits and max_execution_time to prevent script timeouts.
- Inspect web server error logs for specific 500 or 502 error codes to isolate the bottleneck.
- Monitor resource usage trends to identify performance degradation before it causes an outage.
When a website goes down, the immediate reaction is panic. But in support tickets I handled, the usual culprit was rarely a catastrophic hardware failure. It was almost always a configuration drift, a full disk, or a DNS propagation delay.
This guide walks through the most common reasons a website appears down and how to resolve them. We focus on practical steps you can take immediately, without needing to rebuild your entire infrastructure.
Verify DNS Resolution and Local Caching
Before blaming the server, check if the problem is on your end. A stale DNS cache or a local hosts file override can make a site appear down even when it is fully operational.
Run `dig +short yourdomain.com` or `nslookup yourdomain.com` to see if the domain resolves to the correct IP address. If it returns nothing or an old IP, the issue is DNS-related. Clear your local DNS cache with `ipconfig /flushdns` on Windows or `sudo dscacheutil -flushcache` on macOS.
Check your `/etc/hosts` file for any manual entries pointing to the domain. These entries override DNS and can cause unexpected behavior. Remove any test entries that are no longer needed.
- Use `dig` or `nslookup` to verify DNS resolution.
- Clear local DNS cache if resolution is stale.
- Check `/etc/hosts` for manual overrides.
Check Disk Space and Inode Limits
A full disk is one of the most common causes of sudden downtime. When the filesystem runs out of space, the web server cannot write logs, sessions, or temporary files. This leads to 500 errors or complete unresponsiveness.
Run `df -h` to check disk usage. If any partition is above 90% capacity, you need to free up space immediately. Look for large log files, old backups, or unused temporary files.
Also check inode usage with `df -i`. Even if you have free space, running out of inodes (file system metadata) can prevent new files from being created. This is common on systems with many small files, like email directories or cache folders.
- Run `df -h` to check disk usage percentage.
- Run `df -i` to check inode usage.
- Identify and remove large log files or old backups.
Inspect Web Server Error Logs
The error log is your best friend when troubleshooting a down site. It tells you exactly what failed and when. For Apache, check `/var/log/apache2/error.log` or `/var/log/httpd/error_log`. For Nginx, check `/var/log/nginx/error.log`.
Look for recent entries with 5xx status codes. A 500 Internal Server Error often points to a PHP fatal error or a misconfigured .htaccess file. A 502 Bad Gateway usually means the backend PHP-FPM service is down or overloaded.
If the logs are full of permission denied errors, check file ownership and permissions. The web server user (usually `www-data` or `nginx`) needs read access to your web root and write access to log and cache directories.
- Check Apache or Nginx error logs for recent 5xx errors.
- Look for PHP fatal errors or permission denied messages.
- Verify file ownership and permissions on web root.
Tune PHP Memory and Execution Limits
If your site uses a resource-heavy CMS or application, default PHP settings might not be enough. When a script exceeds the memory limit, it crashes with a fatal error. This is a common cause of intermittent downtime.
Check your current PHP settings with `php -i | grep -E 'memory_limit|max_execution_time'`. If you see `memory_limit = 128M` and your application needs more, increase it in your `php.ini` or `.htaccess` file.
Be careful not to set these values too high. Excessive memory allocation can lead to resource exhaustion on shared hosting environments. Start with a modest increase and monitor the impact.
- Check current PHP memory_limit and max_execution_time.
- Increase memory_limit if scripts are crashing.
- Monitor resource usage after changes to avoid exhaustion.
Verify Database Connectivity and Performance
A down website often means the database is unreachable or too slow to respond. If the application cannot connect to the database, it will return a 500 error or a blank page.
Test database connectivity from the server command line. For MySQL, use `mysql -u username -p -h hostname` to verify you can connect. Check the database status with `SHOW STATUS LIKE 'Threads_connected';` to see if the connection pool is saturated.
If the database is responding slowly, check for long-running queries. Use `SHOW PROCESSLIST;` to identify any queries that have been running for an unusually long time. Kill any stuck queries and optimize your slow queries.
- Test database connectivity from the server.
- Check for saturated connection pools.
- Identify and kill long-running queries.
Check Firewall and Security Group Rules
Sometimes the server is fine, but traffic is being blocked before it reaches the web server. A misconfigured firewall or security group can prevent external users from accessing your site.
Check your firewall rules with `iptables -L -n` or `ufw status`. Ensure that ports 80 (HTTP) and 443 (HTTPS) are open for incoming traffic. If you are using a cloud provider, check the security group rules in the console.
Test external connectivity with `curl -I https://yourdomain.com` from a different machine. If the request times out, the issue is likely network-level. If you get a response, the server is reachable and the problem is application-level.
- Check firewall rules for ports 80 and 443.
- Verify security group rules in cloud consoles.
- Test external connectivity with curl from a different machine.
Monitor Resource Usage for Early Warnings
Preventing downtime is better than fixing it. Set up monitoring to alert you when resource usage starts to climb. This gives you time to act before the server becomes unresponsive.
Use tools like `htop` or `top` to monitor CPU and RAM usage in real time. Set up alerts for when CPU usage exceeds 80% or RAM usage exceeds 90% for more than 5 minutes.
Consider using a monitoring service like Prometheus, Grafana, or a cloud-native solution. These tools provide historical data and can help you identify trends that lead to performance degradation.
- Monitor CPU and RAM usage in real time.
- Set up alerts for high resource usage.
- Use historical data to identify performance trends.
Quick troubleshooting checklist
- Verify DNS records resolve correctly using dig or nslookup.
- Check server disk usage and inode availability.
- Review web server error logs for recent 5xx errors.
- Validate PHP configuration limits (memory, execution time).
- Test database connectivity and query performance.
- Check for firewall or security group blocking traffic.
- Monitor CPU and RAM usage for resource exhaustion.
FAQ
Why does my website show 'down' but the server is online?
This usually indicates a DNS resolution issue, a misconfigured web server virtual host, or a PHP fatal error preventing the application from responding. Check the error logs for specific error codes.
How do I fix a 502 Bad Gateway error?
A 502 error typically means the web server cannot communicate with the backend application server. Restart the PHP-FPM service, check for memory exhaustion, and verify the socket or port configuration.
What are the first steps when a website is not working?
First, verify DNS resolution and check if the issue is local or global. Then, check server disk space and review the web server error logs for specific error messages.
Related articles
- Hosting OperationsWebsite Down? 7 Fixes That Actually Work in 2026Fix a website down issue fast. Check DNS, PHP, and disk space. Stop downtime with these 7 practical performance tuning steps and monitoring tips.
- 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: 7 Fixes That Actually WorkFix a website down not working error fast. Check DNS, server status, and code errors with these 7 practical steps for hosting owners.
- 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? 5 Fixes to Restore Uptime FastFix a website down issue by checking disk space, PHP limits, and DNS. Follow these 5 steps to restore service and prevent future outages.
- Hosting OperationsWebsite Down Not Working: 7 Fixes & Security ChecksFix website down not working errors fast. Check DNS, disk space, and security logs. Secure your server with these 7 practical steps.