Shadowrocket for iOSSetup Guide

Rule-based routing lets different destinations use different handling policies. In Config, review the active configuration's Rule list. Rules are checked from top to bottom, and the first match determines the policy; FINAL at the end provides a fallback. PROXY, DIRECT, and REJECT mean proxy, direct connection, and reject the request. Before making changes, keep a copy of the original configuration and test the result against a specific destination. The example domains illustrate syntax only and are not access recommendations. Before using rules, make sure Global Routing is set to Config.

Global Routing determines how the current connection is routed. Config applies the rules in the configuration file; Proxy uses a proxy, while Direct connects directly. These are different modes. For initial setup, check this setting in Home, then confirm the selected server and active configuration. When troubleshooting a destination, note the results before and after changing modes, then restore your original setting. Scene is a related interface term; check it alongside the scene settings, and don't mistake it for a connection protocol or subscription format.

On Demand triggers connection behavior based on conditions you configure, such as network type, specific Wi-Fi names, and domain conditions. First confirm that a manual connection works. Then open Settings, check On Demand, and add conditions one at a time so you can identify the cause if something changes. If the toggle behaves differently than expected after manual operation, check whether an On Demand condition has triggered again before deleting the configuration. Recheck the actual status after switching networks. Automatic triggers determine when to connect; they cannot replace server details or restore a service that is no longer working.

Support for multiple protocols means the client can read different types of connection settings; it does not mean the same settings can be used interchangeably. When entering details for a server you already have, check Type in Add Server, then verify Host, Port, and the authentication and transport fields required by that protocol. Keep the protocol name, encryption method, and transport settings consistent with the information from your service. Don't substitute settings just because the names look similar. After importing, check that all fields are present. If a connection times out, distinguish an unreachable address from mismatched settings, then follow the clues in Diagnostics.

Subscription import reads a server list you already have and retrieves changes when you update it. First identify whether your information is a subscription URL, a single connection entry, or a configuration file, then choose the matching import option. Apply the same check to content scanned with Scan QR Code. After importing, verify the list, groups, protocols, and fields, then select an entry to connect. If an update fails, check that the original address is complete and still valid, and that your current network can retrieve a response in the expected format. Subscription URLs may contain personal access credentials; redact sensitive details when troubleshooting and never share the full URL publicly.

Configuration files contain rules and related handling settings; they are separate from the server list. In Config, confirm which file is active and keep a copy before editing. If you use iCloud sync, check the relevant toggles and sync status rather than assuming content from another device has already appeared. Data can help you review traffic, while Diagnostics provides additional information about connection issues. Traffic records and test results are clues, not proof that every destination is reachable. Use a consistent test destination, change one setting at a time, and note what changed.