"Clash is on and nothing loads" is the most common and the vaguest complaint. Instead of poking randomly, walk the layers below - each step halves the search space, and five minutes usually finds the fault.

Layer 0: does the local network work at all?

Switch to Direct mode on the General page (or turn System Proxy off) and open a domestic site:

  • Fails → the problem is your network itself (Wi-Fi, router, ISP), not Clash.
  • Loads → next layer.

Layer 1: is traffic reaching Clash?

Restore Rule mode and System Proxy, refresh a page, and watch the Connections page:

  • No connections at all → traffic never enters Clash. Check: is System Proxy really on; is another proxy tool fighting over the system proxy; does a browser proxy extension (SwitchyOmega etc.) point at a wrong port.
  • Connections appear → next layer.

Layer 2: are the nodes alive?

Benchmark the group you are using on the Proxies page:

  • All timeouts → node-side problem; follow All Nodes Timing Out (expired subscription, unpaid account, blocked entry IPs are the big three).
  • Some alive → switch to a green low-latency node and retry.

Layer 3: are the rules routing correctly?

Nodes fine but one site fails: search its domain on the Connections page and read Rule and Chains:

  • Hit DIRECT but it is a foreign site → rules missed it; add a custom rule.
  • Hit REJECT → a blocklist false positive; see the REJECT guide.
  • Through a node yet failing → try another node (the site may block that IP); or verify via Global mode.

Layer 4: is DNS healthy?

Symptoms like "some sites crawl or land in the wrong region" usually mean DNS pollution or leaks - enable fake-ip plus fallback per the DNS guide.

The quick-reset combo

Skipping diagnosis? Run through: System Proxy off → quit CFW → relaunch → System Proxy on → update subscription → benchmark and pick a node. This sequence clears a remarkable share of "mystery" failures; if not, return to the layers above.

Tip: keep the Logs page visible throughout - most faults leave an explicit trace there.