This usually means the system proxy is disabled, the browser bypasses it, a rule selects DIRECT, DNS resolution is failing, or TUN is not capturing traffic correctly. Use one browser and one working node as a control, and switch to Global mode for a single test. Once you locate the failure, return to Rule mode and change only the relevant setting.
Are local ports, the system proxy, and rule matching working?
Watch the connection list while opening a test page. If no connection appears, inspect the system proxy or TUN. If a connection appears but selects DIRECT, inspect the rules. If it uses a node and still fails, inspect DNS and the handshake.
- Are the client's local HTTP/SOCKS ports running?
- Is the system proxy switch enabled?
- Does the browser use a separate proxy setting or extension?
- Does the current policy group select a working node?
- Does the requested domain match a DIRECT rule?
Make browser and app requests actually enter Clash
- Start with the client's connectivity or latency test
- After enabling the system proxy, refresh the browser's proxy settings
- Temporarily switch to Global mode to determine whether rules are responsible(See Proxy Mode FAQ)
- Check the connection list to confirm that requests enter Clash
- If requests do not enter the client, check the system proxy, TUN, or per-app proxy settings
Global mode is useful only for temporary diagnosis, not as a long-term configuration recommendation
Some apps ignore the system proxy and require TUN or an in-app proxy setting(See TUN device guide)
DNS errors can prevent pages from loading even when node latency is normal