Website Not Loading
Your site is down. Here’s how to figure out why and fix it: DNS, server, or application.
Your website isn’t loading. Before you panic, work through this systematically. Most outages fall into three categories: DNS, server, or application.
Step 1: Is It Just You?
Check if the site is down for everyone or just your network. Run a check with the GoZen Downtime Checker - enter your domain and it’ll tell you whether the site is reachable from outside your network.
If it’s just you, the problem is on your end. Clear your DNS cache, switch browsers, or try a different network.
Step 2: Check DNS
DNS problems are the most common cause of “site not loading.”
# Check if the domain resolves
dig yourdomain.com +short
# Check which nameservers are authoritative
dig yourdomain.com NS +short
| What You See | What It Means | Fix |
|---|---|---|
| No output | Domain doesn’t resolve | Check nameservers at your registrar |
| Wrong IP | DNS points to the wrong server | Update A record to your server IP |
| Correct IP | DNS is fine, problem is elsewhere | Continue to Step 3 |
| SERVFAIL | Nameserver issue | Check nameserver configuration |
If you recently changed DNS, it might still be propagating. Run a scan at GoZen DNS Inspector to check your records across the board.
Step 3: Check the Server
Shared Hosting
If you’re on shared hosting and DNS is correct, the web server should be responding. Check:
- Is your account suspended? Log into the client area. You’ll see a notice if it is
- Is cPanel accessible? Try
yourdomain.com:2083. If cPanel loads, the server is up - Are you over resource limits? Check cPanel → Metrics → Resource Usage
VPS / Cloud
SSH into your server and check:
# Is the web server running?
sudo systemctl status nginx # or apache2
# Is the server overloaded?
uptime
free -h
df -h
If you can’t SSH in, the server may be down. Use the client area → Services → My Services to check status or trigger a reboot.
Step 4: Check the Application
DNS is fine. Server is up. The problem is in your app.
HTTP Error Codes
| Error | Meaning | Common Fix |
|---|---|---|
| 403 Forbidden | Server refuses to show the page | Check file permissions (644 for files, 755 for directories) |
| 404 Not Found | Page doesn’t exist | Check your .htaccess or Nginx config. Verify the file is in the correct directory |
| 500 Internal Server Error | Something broke in your code | Check error logs (see below) |
| 502 Bad Gateway | Reverse proxy can’t reach the app | Your backend app (Node, PHP-FPM) is crashed or not running |
| 503 Service Unavailable | Server is overloaded or in maintenance | Check resource usage and server logs |
| 504 Gateway Timeout | Backend is too slow to respond | Optimize your app or increase timeout settings |
Check Error Logs
Shared hosting (cPanel):
- Go to Metrics → Errors: shows the last 300 error log entries
- Or check the raw log: File Manager →
/home/username/logs/error.log
VPS:
# Nginx
sudo tail -50 /var/log/nginx/error.log
# Apache
sudo tail -50 /var/log/apache2/error.log
# PHP-FPM
sudo tail -50 /var/log/php-fpm/error.log
# Application-specific
tail -50 /var/www/myapp/storage/logs/laravel.log
Step 5: Check SSL
If your site loads over HTTP but not HTTPS:
# Check if SSL is valid
curl -Iv https://yourdomain.com 2>&1 | head -20
Common SSL issues:
| Problem | Fix |
|---|---|
| ERR_CERT_DATE_INVALID | Certificate expired. Run AutoSSL in cPanel or renew with certbot renew |
| ERR_SSL_PROTOCOL_ERROR | SSL not installed or port 443 blocked |
| Mixed content warnings | Some resources still loading over HTTP. Update URLs |
| Too many redirects | Conflicting HTTPS redirect rules |
Quick Diagnosis Flowchart
Site not loading
├── DNS resolves? → NO → Fix nameservers / A record
├── DNS resolves? → YES
│ ├── Server responds? → NO → Reboot via client area / check SSH
│ ├── Server responds? → YES
│ │ ├── HTTP error code?
│ │ │ ├── 403 → Fix permissions
│ │ │ ├── 500 → Check error logs
│ │ │ ├── 502 → Restart backend app
│ │ │ └── 503 → Check resources
│ │ └── SSL error? → Renew / reinstall certificate
What to Do Next
- How to Get Support: if you’ve worked through this and still can’t fix it, open a ticket
- Managing DNS Records: verify your DNS configuration
Last updated 20 Apr 2026, 00:00 +0300.