CLASH TROUBLE LABEL
Clash FAQ and Troubleshooting
Find a solution by where the problem occurs. Check the basic network and subscription status first, then inspect the client configuration, system proxy, TUN, DNS, and local security policies instead of repeatedly reinstalling the client without identifying the cause.
BASIC NOTES
Fundamentals
Start by distinguishing the client, subscription, nodes, and operating modes. Confusing these concepts often leads to subscription issues being misdiagnosed as client failures.
How are the Clash client and a proxy subscription related?
The Clash client reads configuration, matches rules, and forwards network requests to the selected node; it does not provide proxy servers itself. A subscription URL is usually generated by the service provider and contains nodes, proxy groups, and rules. After installing the client, you still need to import a valid subscription or create a complete configuration file to establish a working connection.
What is the difference between Rule, Global, and Direct mode?
Rule mode evaluates traffic from top to bottom against the rules in the configuration file and is suitable for everyday use. Global mode sends most traffic to a selected proxy group and is useful for temporarily testing nodes. Direct mode bypasses proxy nodes and can help determine whether Clash is causing the problem. Switching modes will not repair an unavailable node, so troubleshooting should also include logs and latency tests.
Can configuration files, subscriptions, and nodes be used together?
Yes, but make sure you understand where each item is updated from. A remote subscription update may overwrite nodes or rules edited directly in the client, so persistent changes should go in an override configuration or a separately maintained YAML file. After importing multiple subscriptions, check that proxy groups reference the correct node names to avoid empty groups when names change.
Why do free Clash nodes so often fail to connect?
Public nodes often have limited capacity, frequently changing addresses, and unpredictable uptime. A successful latency test does not guarantee stable access. When a connection fails, update the source first, then test several nodes individually and verify the system clock, DNS, and local network. Never use control ports or credentials from a public configuration in important environments.
SETUP LABEL
Setup
Focus on the subscription response, configuration structure, system authorization, and state restoration after startup.
Why are no nodes shown after importing a subscription?
First review the subscription update log and confirm that the response is Clash-compatible YAML rather than a login page, expiration notice, or empty file. Then check that the subscription URL is complete, the device clock is correct, and the provider does not restrict the request method. If the configuration downloads but the node list is empty, inspect the proxies and proxy-groups fields and the YAML indentation.
What should I do if a subscription expires or fails to update?
First confirm the plan status and subscription URL on the provider’s website, then return to the client and update it manually. If the request times out, temporarily disable the system proxy and try again, or switch networks to rule out local blocking. For a parse error, note the reported line number and inspect the returned file; repeatedly reinstalling the client usually will not restore an invalid subscription.
Why does TUN mode require administrator privileges?
TUN mode creates a virtual network adapter, adjusts routes, and takes over some system traffic, so Windows, macOS, and Linux may all require administrator authorization. If authorization is denied, quit the client and restart it with the appropriate permissions. Also check whether system network extensions, drivers, or services are allowed. Corporate devices may be restricted by local security policies.
Why does Clash start with the computer but fail to connect automatically?
Starting at boot only launches the client process; it does not necessarily select a configuration, restore the system proxy, or enable TUN. Check the startup configuration, the previous proxy-group selection, and the proxy toggle separately, and make sure the operating system is not delaying or blocking background startup. If the configuration file is on a removable drive or sync folder, ensure the path is readable when the client starts.
OPERATION NOTES
Usage Tips
After a request enters the client, it still passes through port interception, rule matching, policy selection, and DNS resolution.
Why does my browser still connect directly after enabling the system proxy?
First verify that the HTTP or mixed-port shown by the client matches the system proxy port. Then check whether the browser uses its own proxy settings, extensions, or security software. Some applications ignore the system proxy and require TUN mode or an in-app proxy setting. During troubleshooting, inspect Connections or the logs to confirm that requests are actually reaching Clash.
How do I fix UWP loopback when a Windows app cannot connect?
Some sandboxed Windows apps cannot access a local loopback proxy by default, so a browser may work while a Store app fails. In the client’s UWP loopback tool, select the affected app, save the change, and restart the app. If it uses a system-level network service, also check the system proxy, TUN, and firewall rules.
Why don’t Clash rule changes take effect immediately?
After changing rules, save and reload the configuration; existing connections may continue using the previous policy. Close the target program’s existing connections, or terminate the relevant sessions in the client’s connection list, then test again. Also confirm that the new rule appears before MATCH and that domain rules, IP rules, and proxy-group names exactly match their definitions in the configuration.
What should I do if Clash GeoIP or rule-set updates fail?
First confirm that the rule-set URL is reachable and that the configured path is writable, then check the logs for HTTP status codes or file-read errors. Do not let multiple clients write to the same directory during an update. If you replace a GeoIP or rule-set file, verify the filename and format referenced by the configuration and reload it; existing connections will not be rematched automatically under the new rules.
FAULT FINDING
Troubleshooting
Work down from the common failure points: the basic network, subscription, nodes, DNS, routes, virtual adapters, and configuration syntax.
Where should I start when every Clash node times out?
Disable Clash first and verify that the basic network works, then check the system clock, subscription validity, and local DNS. Test nodes from different protocols and regions separately rather than judging by a single latency result. If every node fails at once, prioritize checking the current network, firewall, proxy-port conflicts, and provider status instead of deleting nodes one by one.
Why is the node latency normal but the website will not open?
A latency test usually verifies only whether a specified test address is reachable; it does not confirm that DNS resolution, the destination site’s route, or actual data transfer is working. Check the current proxy-group selection, matched rule, and DNS logs, then terminate old connections and try again. If only certain sites fail, check whether they were incorrectly routed to DIRECT or resolved to an unreachable address.
What should I do if TUN mode breaks the connection or conflicts with another VPN?
Multiple VPNs, virtual adapters, or security tools may modify the default route and DNS at the same time, causing traffic loops or loss of the egress path. Disable other network interception tools and test with only Clash TUN enabled. If the connection still fails, restore the system DNS, restart the virtual adapter, and inspect the routes. Once Clash works alone, enable the other tools one at a time to identify the conflict.
How can I locate a YAML parsing error in a configuration file?
Start near the line number shown in the error. Common causes include inconsistent indentation, a missing space after a colon, misplaced list markers, and text containing special characters that was not quoted correctly. Do not edit the entire file at once: restore the original configuration, add changes section by section, and reload after each change. Use spaces for indentation and do not mix tabs and spaces in the same file.