Routing Rules: Why a Site Goes Direct or Through a Proxy
Routing rules decide how a client handles a destination. A rule may match a domain, IP range, process or other attribute, then send the traffic to a direct connection, a proxy group or a specific outbound. The available match types depend on the client and core.
Read the rule order
Many rule engines test rules in order and use the first matching rule. A broad rule placed too early can override a more specific rule later in the list. Before adding a new rule, check whether an existing one already matches the destination.
Debug one destination at a time
Pick a site with a clear expected result. Check the connection log or rule-matching view, if available, and identify the rule that selected the route. Then adjust one rule and test again. Avoid importing a large rule pack to fix one domain unless you understand what else it changes.
Keep a fallback
Save a copy of the last working configuration before editing. If the result becomes worse, restore it instead of stacking more overrides on top. In shared profiles, some settings may be overwritten during subscription updates, so check whether local changes persist.
For context, read proxy modes and nodes and proxy groups.