Rule-Based Routing
To use different connection paths for different destinations, choose Config in Global Routing, then open the active configuration in Config and review Rule in order. A matched rule can apply PROXY, DIRECT, or REJECT; connections that do not match a preceding rule are handled by FINAL. A broad rule near the top may match before a rule for a specific destination. If the result differs from what you expect, check the destination, rule order, and fallback action before changing the configuration. Retest just one destination after making a change to identify which change took effect.
- Global Routing
- DOMAIN-SUFFIX
- FINAL
On Demand
To connect automatically under specific network conditions, check On Demand in Settings. First complete a manual connection, then configure the automatic trigger conditions. After saving, test on networks that do and do not meet those conditions, and note the connection state before and after changing networks. On Demand determines when to attempt a connection; it does not replace routing rules after the connection is established. If the connection starts again after you turn it off, check whether a trigger condition is still met. If automatic connection does not start, check whether the system VPN configuration is still present. Troubleshoot these issues separately.
Multiple Protocols
The Type selected in Add Server determines which fields to enter. Shadowsocks, VMess, VLESS, Trojan, and Hysteria2 use different settings; the same address and port do not indicate the protocol or authentication method. Choose the type that matches your existing server details, then check the address, port, and relevant authentication fields one by one. For additional transport or TLS options, use the values provided in your server details. If a field is missing, confirm the settings rather than disabling verification to test. After saving, select the entry you just added and run a connection test.
Import Subscriptions
Use Subscribe to manage a group of servers from the same source when you have an existing subscription link. After importing, confirm that the group appears and the expected entries are listed, then select a server to test. When you receive an update, update the original subscription group first. If the server you use has been removed, select another one rather than assuming a successful refresh restored the connection. If an update fails, check that the link was not truncated and that your current network can reach the subscription address. Subscription links may contain personal access credentials; when reporting an issue, describe only the import and update results.
Configuration Files
In Config, distinguish saved files from the file currently in use. Before changing Rule or Hosts, keep a recoverable copy, then edit and select the new file. This avoids editing a configuration that is not active. Before syncing your own devices through iCloud, check the account and sync status. A file appearing on another device does not mean it has been selected there, and system VPN permission does not transfer with it. After changing devices, check the active configuration, Global Routing, and server selection separately, then retest with a familiar destination.
Diagnostic Tools
Check three results separately: Connectivity Test tests the selected server; Data shows traffic recorded by the client, so check the reporting range first; and Diagnostics in Settings can help locate an issue. Traffic statistics do not replace testing access to a destination, and a single connection test cannot confirm that every rule is correct. During retesting, change just one condition, such as the network or routing mode. Before sharing diagnostic information, remove server details, subscription links, and private access records. Keep only the observations and steps needed to reproduce the issue.
- Connectivity Test
- Data
- Diagnostics