Shadowrocket
Get, Configure, and Connect

Rules are evaluated in order

Rule determines which policy handles a request. In Config, check the active configuration, put more specific conditions first, and use FINAL to specify how unmatched requests are handled. DOMAIN-SUFFIX matches domain suffixes; IP-CIDR matches address ranges. PROXY and DIRECT specify different destinations, not server names. Rules are applied only when Global Routing is set to Config. After editing, test with a real request to confirm which rule matches. Change one group of conditions at a time to spot rules overridden by order or scopes that are too broad.

[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,DIRECT

Trigger connections based on network conditions

On Demand controls when a connection is established, while Rule controls where requests go after connection. They serve different purposes. Check On Demand in Settings and set Wi-Fi, cellular, or domain conditions to match your network. First connect manually and verify that the server works, then add one trigger condition and observe the result after switching networks. If the connection starts again after you turn it off, check for an On Demand condition that still matches. Restore automation settings after troubleshooting to avoid repeated toggling without addressing the trigger.

Match the protocol to the server

In Add Server, select the protocol already used by your server under Type, then enter its corresponding settings. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard require different fields; changing Type alone does not make all existing settings compatible. Check the address, port, password or identifier, TLS, and transport settings against the details from your service provider. After importing, make sure all fields are complete. A protocol name does not indicate connection speed, and one latency test cannot represent performance across all apps.

Import and maintain an existing subscription

Subscribe reads a user’s existing server details in a batch. Before importing, confirm the subscription URL and format with your own service provider. After importing, check the groups, entry count, and key settings, then select a server to connect. Updating a subscription reloads remote content, which may overwrite manually edited entries; record important settings separately. Subscription URLs may contain access credentials, so do not show them in public screenshots, logs, or support requests. If an update fails, check whether the URL is complete and unexpired, and whether the current network can reach the subscription endpoint.

Config controls routing; the server determines the exit

Config stores rules and related network settings, while server entries store connection details. Check each separately. Under Global Routing in Home, Config routes traffic by the selected configuration, Proxy sends requests handled by the client through the selected proxy, and Direct connects directly. For everyday use, confirm the active configuration first, then check the server. Keep necessary settings in your backup. With iCloud sync, verify the sync result and selected configuration on the other device; seeing a file does not mean connection authorization and verification are complete.

Use tests, traffic, and logs to diagnose issues

Connectivity Test provides an initial reachability check, Data shows traffic recorded by the client, and Diagnostics in Settings can help investigate further. A latency figure is the result of a specific test method; it does not predict webpage loading or video performance. When troubleshooting, note the network environment, selected server, and Global Routing setting, then reproduce the target request. Data statistics should not be treated as a service provider’s bill. Before sharing logs, remove server credentials, subscription URLs, and personal browsing records; keep only information relevant to the issue.