Website Not Loading But Server Is Up: How to Fix It

This is a confusing situation — your monitoring tool is showing green, your server responds to a ping, but when you or your users try to open the site in a browser, nothing loads. What's going on?

The server being "up" and the website being "accessible" are actually two different things. Here's how to figure out which layer is broken.

Why Your Server Can Be Up But the Site Not Load

A server can be running and responding to basic network requests while still having problems that prevent a browser from loading a web page. The web server software might be fine but the application behind it is broken. DNS might be pointing somewhere unexpected. A CDN might be serving stale or broken content.

Let's work through the most common causes.

1. DNS Issues

DNS is often the first thing to check when a site is reachable from some places but not others.

DNS propagation delays: If you recently changed DNS records (moved hosts, updated A records, etc.) those changes can take time to spread across the internet. Your server is fine — some users just aren't reaching it yet because their DNS cache still has old information.

Expired domain: If your domain registration has lapsed, DNS stops resolving entirely. Check your domain's expiry date immediately — domain expiry monitoring can prevent this from catching you off guard.

Wrong DNS records: A typo in an A record or CNAME pointing to the wrong IP means traffic never arrives at your server.

How to check:

dig yourdomain.com
nslookup yourdomain.com

Compare the IP in the DNS result against your actual server IP.

2. CDN or Proxy Caching Problems

If you're using Cloudflare, a CDN, or a reverse proxy, the "server up" check might be hitting the proxy layer — not your actual origin server.

The CDN reports healthy, but:

• It's serving a cached error page
• It can't reach your origin and is serving stale content
• A misconfigured cache rule is returning incorrect responses

Try bypassing the CDN by accessing your server's IP address directly (if your hosting allows it) or temporarily pausing Cloudflare to rule it out.

3. The Application Layer Is Broken

Your web server (Nginx, Apache) is running and accepting connections, but the application behind it — PHP, Node.js, Python — has crashed or is returning errors.

From the outside, this can look like the site is "up" (the server responds) but "broken" (it returns a 500-level error or a blank page).

Check your application logs:

sudo tail -f /var/log/nginx/error.log
sudo journalctl -u your-app-service -f

Restart your application process if it's crashed.

4. SSL Certificate Problems

If your SSL certificate has expired or is misconfigured, modern browsers will refuse to load the site and show a security warning instead.

Your server is technically up — it's just serving a certificate that browsers won't accept. Check your certificate expiry date and whether the certificate matches your domain. SSL monitoring can alert you before this becomes a problem.

5. Browser Cache or DNS Cache

Sometimes the problem is entirely on the client side. A corrupted cache entry can prevent a specific browser or device from loading a site that works fine everywhere else.

Try:

• Hard refresh: Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac)
• Incognito/private window: bypasses browser cache
• Different browser or device: rules out device-specific issues
• Flush DNS cache: sudo dscacheutil -flushcache on macOS, ipconfig /flushdns on Windows

If other devices can load the site fine, the problem is local to that browser or machine.

6. Firewall Blocking Specific Ports

A server-level firewall might be blocking port 80 or 443 for web traffic while still responding to ICMP ping requests. This means the server "pings" as up but can't actually serve web pages.

sudo ufw status
sudo ss -tlnp | grep -E ':80|:443'

Make sure port 80 and 443 are open and that your web server is actively listening on them.

7. Resource Exhaustion

The server is up but has run out of memory, file descriptors, or database connections. It's technically alive but can't handle new requests.

Check:

free -h          # Memory
df -h            # Disk space
ulimit -n        # Open file limit

A server with full disk space is a common culprit — many Linux systems refuse to write logs or process requests when the disk is 100% full.

How to Narrow It Down Quickly

Work through this checklist:

1. Can you load it on another device/network? → If yes, client-side issue
2. Does curl http://yourdomain.com from the server itself work? → If no, app-layer issue
3. Does dig yourdomain.com return your correct IP? → If no, DNS issue
4. Is your SSL cert valid? → Check with browser or SSL checker
5. Are there any errors in nginx/apache logs? → Almost always a clue there

Stop Relying on Gut Feel — Monitor Properly

The fact that your basic ping check said "up" while your site wasn't loading highlights a key limitation of simple monitors. A proper website monitoring setup checks for an actual valid HTTP response — not just a network ping.

Domain Monitor checks your site returns a real response code, monitors SSL expiry, and can alert you via email, SMS, or Slack if anything is wrong.

Related Articles

• 500 Internal Server Error - Causes and How to Fix It
• DNS_PROBE_FINISHED_NXDOMAIN - What It Means and How to Fix It
• ERR_CONNECTION_REFUSED - What It Means and How to Fix It