Logs and Troubleshooting FAQ
Interpret Clash configuration, client, and network errors; choose info, warning, or debug logging; and share logs safely while tracing the stage that failed.
Use log keywords to narrow the scope
First find the stage where the error occurs, then decide whether to inspect DNS, the connection, handshake, rules, or control interface.
How Should I Read Common Errors in Clash Logs?Read the log by stage: DNS, TCP connection, TLS or protocol handshake, rule match, and control interface. Find the first failure, then use keywords such as lookup, dial, and handshake to locate the stage.How Can I Tell Whether the Problem Is the Configuration, Client, or Network?Isolate Clash failures by changing one variable at a time: client, configuration, or network. Record when the error occurs to identify the responsible layer.Should the Log Level Be info, warning, or debug?Use info or warning for everyday operation. Enable debug only briefly while reproducing an issue, then return to a lower log level when troubleshooting is complete.