Why does Rule mode not route as expected?
Rules may need review because of order, wrong policy group names, DNS resolution timing, unsupported rule types, stale GEOSITE/GEOIP data or a broader rule matching before the intended one.
Read answerDetailed notes about YAML syntax, domain rules, fake-ip, redir-host, GEOIP/GEOSITE, DNS privacy notes, IPv6, TUN and local routing.
Troubleshoot YAML rules, Fake-IP, DNS privacy, GEO data, IPv6, TUN permissions and custom routing behavior.
Rules may need review because of order, wrong policy group names, DNS resolution timing, unsupported rule types, stale GEOSITE/GEOIP data or a broader rule matching before the intended one.
Read answerYAML status messages usually come from indentation, tabs, missing commas in rules, duplicated names or unsupported fields. Fix the first parser status message shown in the log before editing later lines.
Read answerDNS privacy checks help confirm whether domain queries use the intended resolver path. Use the client DNS feature consistently, avoid mixed system resolvers and test after enabling TUN or fake-ip.
Read answerfake-ip maps a domain to a reserved synthetic IP so Clash can recover the original domain later. redir-host resolves real addresses directly, which can be simpler but may reduce domain-aware routing accuracy in intercepted traffic.
Read answerGEOSITE and GEOIP data should be updated when rule behavior becomes stale, regional services change, or the profile depends heavily on domain and country-code matching.
Read answerTo force one website through proxy or direct routing, add a domain rule above broader catch-all rules and point it to the intended policy group. Rule order matters more than the visual position in a GUI.
Read answerRule Provider subscription update prompts usually come from unreachable URLs, wrong behavior type, unsupported format, file permission issues or a provider returning an HTML status message page instead of rules.
Read answerTUN mode needs administrator or system permission because it creates a virtual network interface and modifies routing. Without permission, the client may start without capturing traffic.
Read answerIf TUN causes connection settings, disable it first, confirm normal system proxy works, then check route auto-detection, DNS mode, administrator permission, IPv6 and conflicts with other VPN software.
Read answermixed-port accepts both HTTP and SOCKS traffic on one local port, while separate HTTP and SOCKS ports split those protocols. Use the port that your browser, app or extension is configured to use.
Read answerIPv6 traffic needs rules and DNS behavior that can match IPv6 addresses. If only IPv4 ranges are covered, some traffic may use a different policy under TUN.
Read answerYAML depends on spaces, indentation and list markers. Use spaces instead of tabs, keep comments outside values, and validate after every manual edit.
Read answerSeparate nameserver, fallback, fake-ip, redir-host and fake-ip-filter checks.
Read guideDisable TUN first, then check adapter, DNS hijack, routes and permission.
Read guideUse DOMAIN, GEOIP, Rule Provider and MATCH examples with clear order.
Read guide