The Connections page is the best debugging tool in Clash for Windows: for every connection passing through the core, it shows in real time which rule matched, which node was used and how much data has flowed.
Key columns
| Column | Meaning |
|---|---|
| Host | Destination domain (or IP) and port. |
| Rule | The matched rule, e.g. DomainSuffix(google.com), GeoIP(CN), Match (the fallback). |
| Chains | The proxy chain, e.g. Select / HK 01 = through group "Select" using node "HK 01"; DIRECT = no proxy. |
| DL / UL | Bytes downloaded / uploaded on this connection. |
| Process | The originating process (visible in TUN mode and some other cases). |
Three typical debugging scenarios
- A site is not being proxied: visit the site, search its domain here, and read the Rule column. If it hit
GeoIP(CN)or some direct rule, the rules classified it as direct - add a custom rule. - Unexplained traffic usage: sort by DL and find the heaviest connections - frequently a cloud-drive or updater running in the background.
- Node switch not taking effect: old connections stay alive. Click the broom icon ("Close all connections") to force everything to reconnect under the new settings.
Small but useful
- The search box filters live by domain, process or any keyword.
- Click a row for full details (source address, inbound type, rule path).
- Single connections can be closed individually - surgical removal of one bandwidth hog.
Tip: a completely empty Connections page means traffic is not reaching Clash at all - check System Proxy / TUN first, then see the troubleshooting flow.