Global Routing
The control for choosing how traffic is handled. The three modes are Config, Proxy, and Direct. If changing rules has no effect, first check that Config is selected, then verify which configuration is active.
First, distinguish modes, rules, and policies: the mode determines whether a configuration is used, rules determine what matches, and policies determine what happens after a match.
01 / Interface
The control for choosing how traffic is handled. The three modes are Config, Proxy, and Direct. If changing rules has no effect, first check that Config is selected, then verify which configuration is active.
In Global Routing, Config means traffic is handled according to the current configuration; it does not mean every request goes through a proxy. Config is also the name of the separate page for viewing and managing configuration files. Changing modes and switching files are different actions.
Proxy routes traffic handled by the client through a proxy, while Direct connects the relevant traffic straight to its destination. These mixed-case terms are mode names in the interface; do not confuse them with the PROXY or DIRECT fields at the end of a rule.
On Demand controls whether the system establishes a connection when configured conditions are met. It does not determine how individual requests are routed after the connection is established. If a connection starts automatically after switching networks, check the On Demand conditions first, then Global Routing.
Connectivity Test checks whether a response can be received from a specific test target under current conditions. A successful test only confirms that the path used for that test worked. If just one site fails, check its DNS resolution, matching rule, and connection result separately.
02 / Protocols
Shadowsocks is a proxy protocol with common parameters including server address, port, encryption method, and password. The encryption method must match the server; even with the correct address and port, a mismatch prevents successful data exchange.
VMess typically identifies users with a UUID and supports different transport methods. After importing, check the UUID and transport parameters separately. If the existing configuration specifies additional fields such as a path, do not copy only the address and port.
VLESS also uses a UUID, but it is a different protocol from VMess. Similar UUID formats do not make configurations interchangeable; use the existing server details to check transport and security settings.
Trojan typically connects over TLS and uses password authentication. The password and TLS verification are separate: if the certificate name does not match, check the server name in the configuration rather than repeatedly changing the password.
Hysteria2 is a QUIC-based proxy protocol that relies on UDP. Being able to open a webpage on the current network does not mean the UDP path is reachable. If timeouts occur only after switching networks, include network differences in your troubleshooting.
WireGuard uses a key pair to create an encrypted tunnel. Its configuration typically also includes a peer address and allowed IP prefixes. The peer's public key and your private key serve different purposes and are not interchangeable. Do not show private keys in public screenshots.
03 / Rule matching
When reading rules, check the matching condition first, then the policy. To troubleshoot overlapping conditions, review the configuration from top to bottom rather than looking only at the line that seems closest to the destination name.
DOMAINMatches an exact domain name. For example, a condition set to example.com does not treat www.example.com as the same name. For a single, specific host, an exact match covers less than a suffix match.
DOMAIN-SUFFIXMatches a domain and its subdomains. For example, example.com matches www.example.com, but not notexample.com. To apply an exception policy to a subdomain, place the more specific rule before the suffix rule it overrides.
GEOIPMatches according to the destination IP's classification in a geographic database; it does not analyze page content or determine the device's location. A domain can resolve to different IPs, so the same domain may not produce the same GEOIP match on different networks.
IP-CIDR / IP-CIDR6These match IPv4 and IPv6 address prefixes, respectively; the number after the slash indicates the prefix length. Within the same address family, a longer prefix matches a smaller range. If a destination has both IPv4 and IPv6 addresses, check rules for each address family separately.
FINALSets a fallback policy for traffic that does not match any preceding rule; no destination domain is required. It is usually placed at the end of the rules. Changing the fallback policy does not affect requests already handled by earlier rules.
PROXY / DIRECT / REJECTThese keywords respectively mean route through a proxy, connect directly, and reject the request. If a rule matches REJECT, the connection failure may be exactly what the configuration specifies. Check the rule's matching scope first.
04 / Configuration
Subscribe imports a server list from an existing subscription URL and can reread that URL to update the list. Updating the list and connecting to a server in it are separate checks. Subscription URLs may contain access credentials, so do not include them in public screenshots.
Add Server lets you enter existing server details. Select a protocol first, then fill in its required fields. Saving an entry does not select it; before connecting, return to Home and check which one is selected.
A configuration file stores handling settings such as rules and DNS; it is not the same as the selectable server list. To troubleshoot routing, first confirm which file is active, then check its rule order. Updating a subscription alone does not change these rules.
05 / Network
DNS resolves domain queries to records such as IP addresses, providing destination information for subsequent connections. Resolving an address does not guarantee that the destination is reachable. If a domain does not resolve, check DNS first before investigating routing policies or server connectivity.
DNS over HTTPS (DoH) sends DNS queries and responses over an HTTPS connection. It changes how the client queries a resolver; it does not choose a route for application traffic. Before using it, make sure the resolver itself is reachable.
Latency is the time taken to receive a response in a test, usually measured in milliseconds. For a useful comparison, keep the network, test method, and destination as consistent as possible. A low latency result does not mean a higher transfer rate or predict how other destinations will perform.