Client says "connected" but pages won't load? Debug it in four layers

A green “connected” badge only means one stage of the handshake succeeded. When pages still won’t open, stop toggling settings at random and test each layer on its own:

1. Local network. Disable the client and open a normal site. If that fails too, the problem is your Wi-Fi, router or DNS, not the client.
2. Local port. With the client on, run curl -x http://127.0.0.1:<port> -I https://example.com. “Connection refused” means the client is not listening where you think, or another app owns the port.
3. Exit node. If the port answers but requests time out, the upstream server is unreachable or overloaded. Try a different node and compare latency tests with real requests - a good ping does not guarantee working TCP.
4. Target site. If most sites work but one does not, the site itself may be down, blocking your exit region, or hit by a rule that sends it the wrong way. Check the client’s connection log for which rule matched.

Write down the result of each layer; the first one that fails is where to spend your time.

Full layered checklist with example commands: https://roxi.cc/netdiag26.html

Written by the small team behind Roxi.