Shadowrocket Setup Guide

Global Routing determines how connections are handled. Config applies the policies defined by the active configuration; Proxy and Direct switch the overall traffic-handling mode. Before using the app, confirm that your existing server details are valid, then choose the mode that fits your task. If your configuration includes routing rules but another mode is selected, traffic may not behave as expected. When troubleshooting, note the current selection, change one condition at a time, and use Log to check how a connection is handled. Do not rely on the toggle state alone to determine whether a setting is working.

On Demand starts connections when configured conditions are met; it does not check whether a server is available. First connect and disconnect manually to confirm permissions, subscriptions, and routing mode. Then review the relevant options in Settings. Note the original values before changing conditions, and test what happens when the network changes or you disconnect manually. If a connection starts again after you turn it off, check whether a trigger condition is still met rather than repeatedly deleting system configurations. Device sleep, network conditions, and system scheduling can also affect what you observe. Refer to the options currently shown in the app.

Subscribe is for users who already have a subscription link. In Add Server, choose the appropriate type, enter the link as instructed by its provider, and save. Then return to Home to check the groups and entries. Updating a subscription fetches its remote content; buying the app does not provide connection details. If an update fails, check that the link is complete, your current network can reach the subscription URL, and the subscription is still valid. Do not post a full link containing access credentials publicly. If you manage multiple subscriptions, use clear group names to avoid confusing entries with the same name.

DOMAIN-SUFFIX,example.com,PROXY
GEOIP,CN,DIRECT
FINAL,PROXY

Config stores rules and related settings, and rules are usually evaluated in order. This example matches a specified domain suffix first, then checks GEOIP, and uses FINAL for connections that matched none of the earlier rules. PROXY and DIRECT are rule policy keywords, not explanatory text. The example is for understanding syntax and should not replace an existing configuration. Keep a restorable copy before making changes, confirm that each referenced policy exists in the active configuration, and test rules one at a time. Also check that Global Routing is set to Config; changing a file alone does not mean its rules are being applied to connections.

The protocol type for a Proxy entry must exactly match your existing server details; do not substitute protocols based on similar names. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard have different requirements. When adding a server manually, check Type, Host, Port, and the authentication and transport parameters required by that protocol. Importing from a QR code or subscription can reduce entry errors, but you should still verify the source and parsed results. A protocol name alone does not indicate connection performance. If a connection fails, check the fields, server status, and local network first, then investigate DNS or routing rules. Avoid changing multiple groups of settings at once.

Log shows connection activity, Ping provides a response reference for a particular test method, and Data shows traffic recorded by the app. They are not interchangeable: a test response does not mean every destination is reachable, and increased traffic alone does not prove that a rule matched correctly. To troubleshoot, reproduce a specific request and compare its destination, policy, and error details in the relevant records. Remove subscription links, authentication details, and personal browsing information before sharing logs. Statistics may use a different reporting range or billing basis than your provider, so do not treat in-app figures as a bill.