Website Down? 5 Fixes That Actually Work
Fix a website down error by comparing DNS, server, and code fixes. Find the fastest solution to restore uptime and prevent future outages.

On this page
TL;DR — Key takeaways
- Check DNS propagation and server status before touching code; 80% of 'down' issues are infrastructure, not application bugs.
- Use `ping` and `dig` to isolate whether the problem is local, network, or server-side.
- Restarting services or clearing cache is a safe first step, but always back up configurations before modifying system files.
- If the server is unresponsive, contact hosting support immediately; do not attempt hardware-level fixes without vendor guidance.
When a website goes down, every minute of downtime costs money and trust. The first step is not to panic, but to isolate the problem layer by layer.
This guide compares the most common causes of website outages and provides practical fixes you can apply immediately, whether you are a site owner or a support engineer.
1. DNS Resolution Issues
DNS is the phonebook of the internet. If the records are wrong, expired, or not propagating, users cannot find your server. This is the most common cause of 'website down' errors that are actually 'website not found.'
Check your domain registrar to ensure the domain is active and not expired. Then, use command-line tools to verify that the A record points to the correct IP address. If the IP is wrong, update it and wait for propagation.
- Use `dig +short A yourdomain.com` to check the current IP address.
- Compare the result with the IP address in your hosting control panel.
- If the IP is missing or wrong, update the DNS record at your registrar.
- Wait 15-30 minutes for changes to propagate globally.
2. Server Resource Exhaustion
Servers have limits. When disk space, CPU, or memory runs out, the web server stops responding. In support tickets I handled, the usual culprit was a full disk from unrotated logs or a runaway database query.
Log into your hosting control panel or SSH to check resource usage. If disk space is below 10%, clean up old logs, delete unused files, or expand your storage plan. If CPU is maxed out, identify the process consuming it and kill it if safe.
- Check disk usage with `df -h` via SSH.
- Identify large files with `du -sh * | sort -hr | head -10`.
- Check CPU usage with `top` or `htop`.
- Clear web server cache if using a caching plugin or server-side cache.
3. Web Server Process Failure
Sometimes the server is online, but the web server process (Apache, Nginx, LiteSpeed) has crashed. This happens due to misconfigured `.htaccess` files, PHP errors, or plugin conflicts.
Check the web server error logs for specific error messages. If you see a fatal error, revert recent code changes or disable problematic plugins. Restarting the web server service can also resolve stuck processes.
- Check Apache logs: `/var/log/apache2/error.log` or `/var/log/httpd/error_log`.
- Check Nginx logs: `/var/log/nginx/error.log`.
- Restart the web server: `sudo systemctl restart apache2` or `sudo systemctl restart nginx`.
- Review recent file changes using version control or file timestamps.
4. Database Connection Errors
If your website uses a database (MySQL, MariaDB, PostgreSQL), a connection failure will cause a 'database error' page or a blank screen. This often happens after a server migration, a database crash, or a credential change.
Verify that the database service is running. Check the database credentials in your configuration file (e.g., `wp-config.php` for WordPress). If the database is down, restart the service. If credentials are wrong, update them.
- Check database service status: `sudo systemctl status mysql` or `sudo systemctl status postgresql`.
- Test database connection manually: `mysql -u username -p -h localhost`.
- Verify database credentials in your application configuration file.
- Check database error logs for connection refused or authentication failures.
5. Network and Firewall Issues
If the server is online and the web server is running, but users still cannot connect, the issue might be network-related. Firewalls, security groups, or ISP outages can block traffic to your server.
Test connectivity from your local machine using `ping` and `traceroute`. If the server is reachable but the website is not, check the firewall rules on the server. Ensure that ports 80 (HTTP) and 443 (HTTPS) are open.
- Ping the server IP: `ping yourserverip`.
- Trace the route: `traceroute yourserverip`.
- Check firewall rules: `sudo ufw status` or `sudo iptables -L`.
- Ensure ports 80 and 443 are open in the firewall and cloud security group.
Comparison: Which Fix Should You Try First?
The order of troubleshooting matters. Start with the least invasive and most common issues. DNS and resource checks take minutes and require no code changes. Web server and database fixes require more caution and may need a rollback plan.
If you are a site owner, start with DNS and resource checks. If you are a support engineer, you can move directly to logs and service restarts. Always back up configurations before making changes.
- DNS issues: Fix first. Low risk, high impact.
- Resource exhaustion: Fix second. Medium risk, requires cleanup.
- Web server crashes: Fix third. Higher risk, requires log analysis.
- Database errors: Fix fourth. High risk, requires credential verification.
- Network issues: Fix last. Requires external coordination.
Quick troubleshooting checklist
- Verify the domain is active and not expired in the registrar dashboard.
- Run `dig +short A yourdomain.com` to check if DNS records resolve correctly.
- Check hosting control panel for disk space, CPU usage, or error logs.
- Test the site from a different network or device to rule out local issues.
- Review recent code deployments or plugin updates that might have caused a crash.
FAQ
Why is my website down but the server is online?
This usually indicates a DNS misconfiguration, a web server process crash (like Apache or Nginx), or a database connection failure. Check the web server logs for specific error codes.
How long does it take to fix a website down error?
Simple fixes like clearing cache or restarting services take 5-10 minutes. DNS propagation issues can take up to 48 hours, while server hardware failures may require hours or days for replacement.
Should I restart my server if the website is down?
Only if you have confirmed the server is unresponsive via SSH or console access. A restart can resolve memory leaks or stuck processes, but it will temporarily interrupt all services on that machine.
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? 5 Fixes That Actually WorkFix a website down error fast. Compare disk, DNS, and server causes. Use this checklist to restore service in minutes.
- Hosting OperationsWebsite Down Error: 7 Fixes That Actually WorkFix a website down error by comparing DNS, server, and code causes. Stop guessing and apply these 7 practical steps to restore uptime fast.
- 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 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? 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.