Rule-based Routing FAQ
Troubleshoot inactive Clash rules, wrong policy matches, rule-provider updates, and GeoIP or GeoSite behavior by checking rule order, policy groups, and rule sets.
Start with the rule that actually matched
The match shown in the connection list is more reliable than guessing. Use it before deciding whether to adjust rule order or a rule set.
Why Did a Website Match the Wrong DIRECT or PROXY Rule?Clash evaluates rules from top to bottom. Once an earlier rule matches, later rules are not checked. Find the rule that actually matched in the connection log, then adjust the order of the specific rule and MATCH.What If rule-provider Fails to Update or the Rule Set Is Empty?Common causes include an unreachable URL, a format mismatch, insufficient path permissions, stale cache, or a provider response that does not contain rules.What If GeoIP, GeoSite, or Geographic Rules Behave Unexpectedly?Geo rules depend on database versions, DNS results, and rule order; locations and categories have edge cases. Update the data, then use connection logs to find earlier matches.