Shadowrocket User Guide Import Subscriptions and Rule-Based Routing

Global Routing determines how traffic is routed. Config matches requests against rules in the active configuration; Proxy uses a proxy policy, while Direct connects directly. Results also depend on the rules, connection type, and network conditions. To troubleshoot everyday routing, first check that Config has the intended file selected, then review the rules from top to bottom. DOMAIN-SUFFIX matches domain suffixes, GEOIP checks the destination IP against a geographic database, and FINAL handles requests that matched no earlier rule. Change one condition at a time so you can compare results without also switching modes or configurations.

On Demand requests a connection when specified conditions are met. Set it up only after confirming that a manual connection works. Open On Demand in Settings, decide which network conditions should trigger a connection, then save and test on the relevant network. It controls when a connection is triggered; it cannot supply missing server details or fix an expired subscription. If a connection starts after you turn the feature off, review the configured conditions instead of repeatedly deleting servers. For troubleshooting, temporarily disable automatic triggering and use manual connection as a baseline. Once it works, restore the conditions one at a time.

The protocol determines how the client and server exchange data. Shadowrocket supports protocols including Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard. When adding a server, choose Type based on your existing server details, then verify the address, port, and authentication fields. Protocols require different parameters; changing the protocol name while keeping the other fields is not enough. Check TLS, transport, and other options against the original details one by one. If an option is unclear, confirm what it means rather than switching settings at random. A protocol name alone says nothing about connection quality.

Subscribe imports and updates your existing subscription, keeping server details from the same link together. Before pasting, make sure the link is complete and check for query parameters, line breaks, and extra spaces. After saving, confirm that server entries appear, then test one. An update reads the remote content again, so names, order, or the number of entries may change. If you need to keep manual changes, back up your data first and distinguish subscription-managed entries from manually added ones. Subscription links often contain access credentials; do not include them in public screenshots, chat messages, or troubleshooting attachments.

Config manages rule configurations and is separate from the server details saved in Home. Adding a server specifies where to connect; selecting a configuration determines how requests match policies. Back up the current file before editing. Understand the roles of sections such as General, Rule, and Hosts before changing anything. iCloud sync can manage eligible data across devices; first check the sync scope in the app, your system account, and the sync status. Do not treat sync as a standalone backup. After switching devices, confirm which configuration is selected and whether Global Routing is in the intended mode.

When troubleshooting, distinguish test results from actual requests. Connectivity Test checks reachability under current conditions; Data can help you observe traffic changes, and Diagnostics in Settings can help narrow down issues. A successful test does not guarantee that every site is accessible, and a failed test needs to be interpreted in light of how it was run. Keep the current server and rules unchanged, and note the steps, destination, and network conditions that reproduce the issue. Then check address resolution, connection setup, and rule matching in turn. Before sharing diagnostics, remove subscription links, credentials, and unnecessary personal browsing records.