Global Routing: choose a mode, then check the rules
In Home's Global Routing, Config matches requests against the active configuration file, Proxy sends proxyable requests through the selected server, and Direct connects without a proxy. For everyday rule-based use, select Config first, then confirm the active configuration and final policy. Rules are usually matched from top to bottom, so more specific entries should precede broader ones. PROXY, DIRECT and REJECT are rule actions, not the names of the modes at the top. When troubleshooting, temporarily switch modes to compare the same destination, then restore the original setting so a temporary test does not become a permanent configuration.
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,DIRECT
On Demand: trigger connections based on network conditions
On Demand controls connection behavior according to network conditions and is available in Settings. First connect manually and verify that an existing server works. Then set the network conditions that should trigger or prevent a connection; change one item at a time and observe the results when switching between Wi-Fi and mobile data. It controls when to connect, not the Global Routing rules, and cannot fix an expired subscription or incorrect server parameters. If the connection starts again after disconnecting, check whether On Demand is still active. To stop automatic triggers, disable the relevant condition before disconnecting manually.
Settings
On Demand
Global Routing → Config
Multiple protocols: Type must match the server
Shadowrocket supports protocols including Shadowsocks, VMess, VLESS, Trojan and Hysteria2. To enter details manually, start with Type in Add Server, then use the user's existing server information to fill in Host, Port and authentication fields. Check additional parameters such as TLS and the transport method. Matching protocol names do not mean other parameters are interchangeable, and a successful import does not confirm a working connection. Prefer complete existing share information and check fields one by one if a connection fails. Do not change the encryption method based on guesswork or disable verification without a reason; values must match the server configuration.
Add Server
Type → VMess
Host → example.com
Subscribe: update existing content, not configuration
Subscribe saves a subscription address the user already has and uses it to update the server list. Before importing, check that the copied link is complete and does not contain spaces, line breaks or explanatory text. Treat authentication details in the address as private credentials. If an update fails, first check whether the current network can reach the subscription address, then verify that the link is valid; do not add the same address repeatedly. Updating a subscription changes list contents, but does not ensure that the selected server or Config meets your needs. After updating, confirm the selected entry, run Connectivity Test, and then verify an actual request.
Subscribe
Update
Connectivity Test
Config: keep routing logic separate from the server list
Config stores rules and related network settings, while the server list stores connection parameters; they serve different purposes. Before editing, keep a usable copy, then review sections such as General, Rule and Hosts and change only items related to the issue. Check new rules against match order and the final policy, and confirm that the file is enabled after saving. When using iCloud sync between iPhone and iPad, check device sign-in status and sync options, then confirm that the file has fully arrived on the destination device. Sync is not an immediate connection test and does not replace a backup before editing.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
DOMAIN-KEYWORD,ads,REJECT
FINAL,DIRECT
Diagnostics: interpret tests, logs and traffic separately
Connectivity Test shows server test results, Data displays traffic statistics, and Diagnostics and Log in Settings help locate specific requests. Test readings depend on the method and destination, so they cannot replace real-world app checks. First note the affected destination and time, then check whether the expected rule matched, which policy was used, and whether a DNS or connection error occurred. Interpret Data totals in the context of the reporting period and last reset. Before sharing troubleshooting records, hide subscription addresses, authentication fields and other personal information.
Connectivity Test
Data
Settings → Diagnostics