ShadowrocketSetup & Rule-Based Routing

Rules determine how requests are handled. Before you begin, select Config under Global Routing on Home, then open Config to check which file is active. Rules are generally evaluated in order, so place specific domains before broader conditions. DOMAIN-SUFFIX matches a domain suffix, while IP-CIDR matches an address range. PROXY, DIRECT, and REJECT specify different actions; FINAL handles requests that did not match earlier rules. After making changes, verify the results with actual requests and logs. Server latency alone cannot confirm that routing is correct.

Config applies the rules in the active file. Proxy and Direct are useful for comparison when troubleshooting. When testing is complete, check whether you need to switch back to Config so a temporary test mode does not become your long-term setting.

On Demand manages connections according to conditions you set; find it in Settings. First, use the manual switch to establish a normal connection and confirm that your existing server and Config work. Then review the On Demand conditions. Distinguish between Wi-Fi, cellular, and specific network conditions, and do not confuse connection triggers with request-routing rules. If the connection starts again after you turn it off, check the On Demand conditions and the VPN status in system settings. Test network changes and reopening the app separately. Change one setting at a time so you can identify the cause.

On Demand controls when to connect; Rules control how requests are handled after connection. The rule example on the right routes local network addresses through DIRECT. It does not mean automatic connection has been configured for a particular Wi-Fi network.

Shadowrocket supports protocols including Shadowsocks, VMess, VLESS, Trojan, and WireGuard. To add a server manually, start with Type under Add Server, then check the address, port, authentication details, and transport settings against your existing server information. Fields are not interchangeable across protocols. If TLS is enabled, make sure the server name matches your details. If a connection fails, first confirm that the fields match the selected protocol, then review the connection logs. Changing only the protocol name will not make incompatible details work. Available options may vary by app version; PROXY in a rule does not specify a particular protocol.

A protocol describes how the client connects to a server; a policy determines where a request goes. First make sure the server details work, then check whether the request matches PROXY. Changing DIRECT to PROXY will not fill in missing authentication details.

Use Subscribe to manage subscription details you already have. Before importing, make sure the link comes from your own service provider and copy it in full. Do not use the URL of an information page as a subscription link. After importing, review the groups and server entries, then select one to test. Updating a subscription fetches its contents again; it does not necessarily update the rules in the active Config. Give multiple subscriptions clear names. Before removing duplicate entries, verify where they came from, and keep a separate backup of any details you saved manually. Subscription links may contain personal credentials, so redact the full URL and authentication details when reporting a problem.

After updating server entries, confirm which one is selected. Config controls rules and related settings. The example on the right shows rule file contents, not a subscription link, and cannot be used to generate server details.

Config manages rules and related settings. First check which file is active, then open the editor and review sections such as General and Rule. Keep a copy of the original before making changes so you can restore working settings. If you use iCloud sync, check your iCloud status and the app's sync settings, then verify that the content actually appears on another device. Sync does not guarantee a successful connection. Server details, configuration files, and purchase records are separate; restoring one does not restore the others. To isolate a problem, return to a known-working configuration and add changes one at a time.

After editing, confirm that the changes were saved, then return and check which Config is selected. A file appearing in the list does not mean it is handling current requests; also make sure Global Routing is set to Config.

Connectivity Test checks how a server connection performs. Diagnostics in Settings can help pinpoint problems, and Data shows traffic recorded by the app. A successful test does not mean every website request will work; check DNS, rule matches, and the destination connection separately. Note the network, Global Routing mode, and selected server when a problem occurs, then reproduce the request. Keep other conditions consistent when comparing logs. Data's reporting scope is described in the app and should not be treated as a substitute for your service provider's usage records. Remove personal domains, addresses, and credentials before sharing logs.

First check the device's network, then review server fields, DNS, and rules. The snippet on the right illustrates the difference between a specific domain and the final policy. Do not overwrite your existing configuration before identifying the problem.