Global Routing: identify the mode, then review the rules
For everyday use, select Config in Home under Global Routing so requests are matched against the active profile. Proxy sends proxy-eligible traffic through the proxy policy; Direct provides a direct-connection comparison. These modes can help isolate issues temporarily, but should not be confused with the PROXY and DIRECT policy names inside a profile. Rules are usually evaluated from top to bottom, so place specific domain rules first and FINAL last. After making changes, retest the same destination and check which rule matched rather than relying only on the connection toggle.
DOMAIN-SUFFIX,example.com,PROXY
GEOIP,CN,DIRECT
FINAL,PROXY
HomeGlobal RoutingConfig
The PROXY policy in the example must refer to a valid policy in the active profile. Valid rule syntax and an available policy are separate checks.
On Demand: check the conditions and the result
On Demand starts a connection when the configured system conditions are met. First complete a manual connection and access test, then review the conditions in Settings under On Demand and enable them as needed. Do not use automatic connections to mask incorrect server parameters. After switching between Wi-Fi and cellular, check whether the system connection status matches actual access. If connections repeat, disable On Demand and retest manually with the same server. Automatic triggers determine when to connect; Config rules below determine how to route traffic after connecting. They serve different purposes.
DOMAIN-SUFFIX,example.com,PROXY
FINAL,DIRECT
SettingsOn DemandGlobal Routing
Add Server: match Type to the server parameters
Shadowrocket supports protocols including Shadowsocks, VMess, VLESS, Trojan, HTTP, SOCKS5, WireGuard, and Hysteria2. In Add Server, first select the Type that matches your existing server, then enter Host, Port, and the corresponding authentication and transport fields. Do not infer TLS, transport settings, or server names from the port, or reuse settings across different protocols. Test one entry after importing it, then configure routing with Config rules. The protocol determines how a connection is established, not whether a domain should use PROXY or DIRECT.
DOMAIN,example.com,PROXY
GEOIP,CN,DIRECT
FINAL,PROXY
Add ServerTypeHostPort
Subscribe: import a URL and keep it up to date
An existing subscription is an update URL for a group of servers, not a share link for a single server. In Add Server, select Subscribe, enter your full subscription URL, and save. Then check Home for the corresponding group. To update it, keep the original subscription entry and refresh it instead of repeatedly importing duplicates. If an update fails, check that the URL is complete, the network is reachable, and the subscription is still valid before deleting any existing servers. Subscription URLs may contain access credentials; avoid sharing screenshots that expose them. See the server management manual for management and backup guidance.
DOMAIN-SUFFIX,example.com,PROXY
FINAL,PROXY
Add ServerSubscribeURLHome
The rule snippet illustrates routing after import and is unrelated to subscription URL formats.
Config: rules apply only when the profile is selected
Config manages profiles, with sections such as General, Rule, and Hosts serving different purposes. Back up the working profile before editing a copy. After saving, confirm that the intended file is selected and that Global Routing is set to Config. Adding a file without enabling it will not change current routing. For iCloud sync, check the same account and sync status on a supported device, then verify the file contents. Do not assume that syncing a profile automatically transfers all server credentials. Change one rule at a time to make it easier to compare results and revert changes.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
GEOIP,CN,DIRECT
FINAL,PROXY
ConfigGeneralRuleHosts
Connectivity Test: interpret results in context
Connectivity Test can help check connection status. The Test Method in Settings affects how tests run, so results from different methods are not directly comparable. After a successful test, try accessing the actual destination and use logs to identify whether the issue lies with DNS, the connection, or rule matching. Data shows traffic recorded by the client and does not replace usage records from your service provider. During troubleshooting, keep the server and destination fixed and change one condition at a time. If Proxy works but Config does not, focus on rule order and policy references rather than re-entering all credentials.
DOMAIN,example.com,PROXY
FINAL,DIRECT
Connectivity TestTest MethodDiagnosticsData