Troubleshooting

How to Troubleshoot Website Connection Problems (Step-by-Step)

Connection problems span four layers: network, DNS, transport (SSL), and application. Diagnose them in that order — every time — and you'll fix issues in minutes instead of hours.

The four-layer diagnostic order

Network reachability — can packets reach the server at all? Use ping.
DNS — does the domain resolve to the IP you expect?
Transport / SSL — does TLS handshake succeed? Is the cert valid?
Application — does the HTTP service return a real response?

Interpreting each result

Ping fails entirely: server is offline, blocked by firewall, or behind a load balancer that drops ICMP. Try TCP ping or move to step 2.

DNS returns wrong IP: someone changed the record, propagation isn't complete, or local cache is stale. Flush DNS, query a public resolver.

SSL handshake fails: expired cert, broken chain, or protocol mismatch. Test with a different browser to rule out client-side issues.

HTTP returns 5xx: server is up but the application is broken. Check logs and recent deploys.

HTTP returns 4xx: request is reaching the server but being rejected. Often auth, rate limiting, or routing config.

When to suspect your own network

If only you can't reach the site, the diagnostic order shifts: try a different DNS resolver, restart your router, test from mobile data, and check that your firewall or VPN isn't blocking the destination. Two minutes of testing from outside your network beats two hours of guessing inside it.

Recommended next steps

Diagnostic workflow

1
Ping the host
Confirm basic network reachability and measure round-trip time.
Run Ping Test
2
Lookup DNS
Verify the domain resolves to the expected IP.
DNS Lookup
3
Check server response
Confirm the web service answers, not just the network layer.
Server Status
4
Verify SSL
Catch certificate-level failures that look like connection problems.
SSL guide
5
Set up monitoring
Catch the next outage before users do.
Configure alerts

Frequently asked questions

What's the right order for troubleshooting?

Bottom-up: network reachability (ping) → DNS resolution → server response (HTTP) → SSL/TLS → application. Skipping a layer means you'll waste time chasing symptoms.

What if ping works but the website doesn't load?

The server is reachable at the network layer but the web service (port 80/443) is down or refusing connections. Check the server status and firewall rules.

How do I know if it's a local network problem?

Test from a different network (mobile data is easiest). If it works there, the issue is local — your ISP, DNS resolver, router, or local firewall.

What does 'connection refused' actually mean?

The server is reachable but actively rejecting connections on that port. The web server process likely crashed or isn't listening on the expected port.

What does 'connection timed out' mean?

Packets are reaching the server but no response is coming back, often because of a firewall dropping packets silently or a fully overloaded server.