Practical notes for system proxy, VPN/TUN, Allow LAN, logs, startup behavior, browser extensions and daily client operation.
Covers system proxy, TUN, start-on-boot, tray states, LAN access, browser extension conflicts, restarts and log reading.
System proxy affects apps that respect OS proxy settings, VPN mode captures more mobile traffic through the platform VPN API, and TUN captures network-layer traffic when the client and OS support it.
Read answerIf the browser uses the proxy but another app does not, the other app may ignore system proxy settings, use its own proxy configuration, require TUN/VPN capture, or connect through a protocol Clash is not currently intercepting.
Read answerStart-on-boot launches the client automatically, but auto proxy still depends on whether the client enables system proxy, VPN or TUN after startup. Configure both settings if you need hands-off use.
Read answerTray icon colors are client-specific status indicators. They usually reflect running state, system proxy status, profile status messages or selected mode, so read the client legend or log for exact meaning.
Read answerAllow LAN lets other devices on the same local network connect to your Clash proxy port. Enable it only when you deliberately want a phone, tablet or another computer to use this machine as a proxy gateway.
Read answerEnable TUN only when system proxy is not enough, such as apps that ignore proxy settings, UDP traffic, games or full-device routing. Keep it off for first-time testing until normal proxy works.
Read answerLocal websites, private IP ranges and LAN devices should usually go DIRECT. Sending LAN traffic through a remote proxy can break printers, routers, captive portals, local dashboards and domestic services.
Read answerBrowser proxy extensions can override Clash system proxy settings. Disable extensions while testing, or make sure the extension points to the same local port that Clash is listening on.
Read answerRestarting or clearing cache is useful after changing DNS, rules, providers or TUN settings because clients and operating systems may keep old DNS answers, stale processes or previous proxy ports alive.
Read answerClash logs show whether connection symptoms come from subscription updates, YAML parsing, DNS, port binding, rule matching or node connection. Read the first relevant status message near the time of the connection symptom instead of only the final symptom.
Read answer