Shadowrocket User Guide and Rule Configuration

Global Routing determines how connections are routed. Config applies the rules in the active configuration, while Proxy and Direct select the corresponding global routing modes. To route traffic based on domains or addresses, first make sure Config is selected, then check the rule order and policy names. Rules are generally matched in order, so place more specific conditions before fallback rules. After making changes, verify the result with real requests and connection records. One successful test does not mean every rule is working.

On Demand triggers connections based on specified conditions. It does not determine which routing rule handles an individual request. Go to On Demand in Settings, identify the network conditions you want to cover, then check each condition and action. For your first setup, add just one condition that you can verify clearly. Test whether it triggers as expected when you switch networks before adding more. If the connection starts again after you turn it off manually, check whether the On Demand conditions are still met. Review these settings if you want to stop automatic connections.

Shadowrocket supports multiple protocols. The server details you already have must match the Type selected in Add Server. Shadowsocks, VMess, VLESS, Trojan, and WireGuard each require different fields; changing only the protocol name while keeping other fields from a different protocol will not work. When entering details manually, check the Host, Port, and authentication information against your server records, then review transport and security options. If you import a link or scan a QR code, open the details to make sure all fields are present. A protocol name alone says nothing about connection quality, which also depends on the server and your current network.

Subscribe imports and updates your existing server list. Before adding a link, make sure it is complete and has no extra spaces, line breaks, or explanatory text. After saving, check that the expected groups and server entries appear. A successful update only means the list was retrieved and processed; it does not mean every server can connect. If an update fails, check link access, authentication, and content parsing separately, then review your network conditions. Subscription URLs may contain access credentials, so do not share them in screenshots, logs, or public discussions.

Config files organize rules and related network settings. After importing a file, review its rules, policy references, and DNS settings, then confirm it is selected as the active configuration. A file appearing in the list does not mean it is in use. Keep a recoverable copy before making changes, and adjust one category of settings at a time, noting the reason for each change. If you use iCloud sync, check the sync scope and results in the app. Do not assume that syncing a file restores all connection states, permissions, or existing server details on your devices.

To troubleshoot a connection, start with Connectivity Test to check an existing server, then make a real request to confirm that the target service is available. Data shows traffic recorded by the app; it is not the same as usage data from the server. Before comparing figures, check the time period and what each measure includes. To investigate further, review Diagnostics in Settings and the relevant connection records to distinguish DNS resolution, connection establishment, and rule selection issues. Before sharing records, remove subscription URLs, authentication details, and personal browsing data; include only what is needed to troubleshoot.