Clash FAQ and Troubleshooting Steps

mihomo is the core that reads configuration, matches rules, and forwards traffic. GUI clients such as Clash Verge Rev and FlClash handle subscription management, toggles, settings, and logs. Desktop and mobile clients usually include a usable core, so most users do not need to launch a separate command-line program.

Use Rule mode for everyday traffic so each connection follows the configured proxy or direct rule. Global mode sends most manageable traffic through the current policy group and is useful for temporarily testing a node. Direct mode bypasses the proxy and is useful for troubleshooting or restoring local connectivity.

A subscription is an updateable remote configuration that may contain nodes, policy groups, and rules. A node describes a specific connection endpoint, while a policy group selects one option from several nodes or actions. Switching policy groups does not change the subscription URL, while updating a subscription may reset the group structure defined by its provider.

Existing installations may continue to run, but an unmaintained client will no longer receive compatibility fixes or bug fixes. Export or save your subscription URL first, then migrate to a maintained client. Do not overwrite the original directory immediately; complete import, node selection, and connectivity checks in parallel before removing the old client.

A system proxy relies on applications reading the operating system's proxy settings; browsers and most desktop apps support this. TUN mode uses a virtual network interface to capture more traffic at the IP layer, including some programs that ignore system proxy settings. It requires higher privileges and is more susceptible to firewalls, virtual adapters, and security software.

The right frequency depends on how often the configuration provider makes changes. If nodes stop working, policy groups disappear, or rules remain unchanged for too long, try a manual update first. Avoid setting automatic updates too frequently; an hourly interval supported by the client is usually sufficient. After updating, verify that it succeeded and that the current policy group still points to the intended option.

Prefer the client's override, merge, or scripting features, and keep custom rules in a separate configuration instead of editing a subscription file that will be replaced on the next update. Rules are matched from top to bottom, so specific domain rules should come before broad rules. After editing, validate the configuration, reload it, and check the matching results in the logs.

Automatic selection usually follows the test URL, interval, and tolerance configured in the policy group; it does not necessarily choose the fastest node for every situation. Results are also affected by your local network and the target site. Select a stable node manually first. For a lasting change, adjust the policy group's test parameters or preserve the setting with a configuration override.

In most cases, a working TUN mode can capture the main traffic without relying on the system proxy. Whether both should be enabled depends on the client implementation and your use case. When troubleshooting, enable only one capture method at a time: verify the system proxy first, then test TUN separately. This makes it easier to tell whether the problem comes from an app's proxy settings or the virtual adapter.

info is usually enough for everyday use, while warning is suitable when you only want to see problems. debug records more detail about rule matching and connection handling, making it useful for short troubleshooting sessions involving rules, DNS, or connectivity, but logs grow quickly. Switch to debug before reproducing an issue, note the key timestamps, then return to info when finished.