smart-routing

Routing

Routing rules live in the saved Xray template, and every rule tool (add_routing_rule, update_routing_rule, remove_routing_rule) rewrites that whole template read-modify-write. Two consequences: back up before a session of edits, and do not interleave rule edits with update_xray_template, which replaces the document outright and will discard rules added in between.

Before anything else

Sniffing must be enabled on the inbound. Without it the router sees only IP addresses and every domain rule misses — silently, with no error anywhere. The default sniffing this server sends on create_inbound has it on; an inbound created elsewhere may not. Check get_inbound first when domain rules "do nothing".

Rule order is the whole game

get_routing_rules

Rules are evaluated top to bottom and the first match wins. The classic failure is a broad rule above a narrow one — geosite:category-ads above a specific domain:ads.example.com exception means the exception never runs. add_routing_rule appends by default; pass index to place a rule where it will actually be reached.

get_routing_rules also returns the balancer definitions, because a rule's balancerTag is meaningless without them.

Validate geo tokens before saving

geosite: and geoip: tokens that do not exist do not error — they just never match:

validate_geodata_tokens tokens="geosite:category-ads-all,geoip:private" kind="domain"

list_geodata_files, list_geodata_categories and list_geodata_entries browse what the server's databases actually contain, which is the reliable way to find the right category name rather than guessing from a blog post. update_geofile refreshes the databases; stale geo data is a common cause of rules that used to work.

Common shapes

Direct for local traffic, so it never leaves through the proxy:

add_routing_rule rule={"type":"field","outboundTag":"direct","ip":["geoip:private"]} index=0

Block a category: