Shadowrocket’s Global Routing setting determines how connections handled by the app are routed. If you already have a provider configuration, Config is a good starting point for everyday use; then check the rules. For troubleshooting, compare Proxy and Direct. This guide explains how the three modes differ, how to switch between them, how rule order works, and why Scene and On Demand are separate features.
Three routing modes: understand routing before testing connectivity
Global Routing is neither a protocol selector nor a list of provider servers. It determines which strategy handles a connection. The proxy selected on Home determines which server is used when a connection needs a proxy. Rules on the Config screen determine which strategies apply to which destinations. These settings work together, but none can replace the others.
Config mode
RecommendedConnections are handled according to the rules in the currently active configuration. Rules can specify DIRECT, PROXY, or another strategy defined in the configuration. If no earlier rule matches, FINAL determines the fallback strategy.
Best for: everyday split routing, with different strategies for different destinations.
Proxy mode
Routes app-handled connections through the proxy without selecting an outbound route by matching each connection against the configuration’s domain and IP rules. It does not fix errors in the server address, authentication details, or transport settings.
Best for: temporarily routing everything through the proxy or checking split-routing rules.
Direct mode
Sends app-handled connections directly through the local network, without forwarding them through a proxy server. Whether a direct connection succeeds depends on whether the destination is reachable from your current network.
Best for: establishing a baseline for your local network or temporarily checking direct access.
“All through the proxy” and “all direct” refer to app-handled connections in Shadowrocket’s scope. They do not mean every system request on the device follows the same route. Check tunnel route exclusions, LAN settings, and DNS settings separately. The mode name alone does not tell you whether DNS queries are sent through the proxy.
Switch modes on Home and verify with a new connection
The steps below use the iPhone / iPad interface. Before switching modes, make sure you already have a provider and a valid configuration; Shadowrocket’s routing modes do not provide proxy servers. First, confirm that a proxy entry is visible on Home.
-
Check the proxy
Go to Home and select one of your available proxy entries. Check the server address, port, and authentication details. Selecting an entry does not confirm that the connection works.
-
Check the configuration
Go to Config and make sure the expected configuration file is active. Check its rules and strategy names. Downloading a file without activating it will not produce the expected routing results.
-
Choose a routing mode
Go to Home → Global Routing and select Config. To compare behavior, select Proxy or Direct separately.
-
Start a new connection
Make sure the connection switch on Home is on, then reopen the page you want to test or send the request again. Existing long-lived connections may keep using their previous route, so they are not a reliable way to check the result of a recent mode change.
-
Restore your everyday settings
After comparing modes, go to Home → Global Routing → Config. Reopen the same destination and check which rule matched and what the result was.
How Config works: from the first matching rule to FINAL
Config does not mean “some websites always use the proxy and everything else always connects directly.” Rules are checked in order, and the first match determines the strategy. Put specific domain rules before broad IP rules, and place FINAL at the end of the rule list. Different rules can route the same destination differently.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY
This is a rule syntax example, not a complete configuration. example.com is a sample domain; 192.168.0.0/16 is a private network range and does not cover every LAN address range. Before adding this snippet to your configuration, back up the original file and confirm what PROXY points to in your configuration.
| Rule keyword | What it does in this example | What to check |
|---|---|---|
DOMAIN-SUFFIX (domain suffix) | Routes example.com and its subdomains through PROXY. | An earlier matching rule prevents later rules from being checked. |
IP-CIDR (IP address range) | Routes 192.168.0.0/16 through DIRECT. | no-resolve means the rule will not actively resolve a domain name to check for a match. |
GEOIP (IP geolocation) | Routes destination IPs classified as CN by the geolocation database through DIRECT. | This is based on the destination IP and the database, not the language of the website. |
FINAL (fallback rule) | Routes connections that did not match an earlier rule through PROXY. | The fallback strategy can vary; unmatched connections are not necessarily routed directly. |
A website may use multiple domains for sign-in, images, video, and other content. Adding a rule for the main domain alone may not cover every request. If the page loads but images do not, check the actual destination domains in the connection log instead of switching the entire configuration to Direct. Likewise, a direct request to an IP address may not match a domain rule.
Narrow down the issue with two comparisons
Keep test conditions consistent: use the same device, network, proxy entry, and destination. Change only Global Routing, establish a new connection, and record the result each time. Do not switch modes while also refreshing a subscription or changing servers; otherwise, you will not know which change affected the result.
Troubleshooting: check rules and the local network separately
Compare Config and Proxy
- Config fails but Proxy works: first check the matching rule, the strategy it points to, and which configuration file is active.
- Both fail: check whether the proxy server is reachable, whether the authentication details are correct, and whether the destination service is working.
- Both work, but speeds differ: confirm that they use the same outbound route before comparing performance.
Compare Direct with the connection turned off
- Both fail: check the local network, destination service, and system DNS first. Do not rush to change proxy rules.
- Direct fails but the connection-off test works: check the app’s DNS settings and tunnel routing settings.
- The result does not change after switching: send the request again to rule out connection reuse and cached results.
Comparison results help determine what to check next; by themselves, they do not prove that a particular server or rule is faulty.
For example, a website opens over the same Wi-Fi in Proxy mode but fails in Config mode. This shows that the proxy route worked during that test. Next, check whether Config routes the site through DIRECT or another unavailable strategy. If the main page loads but a video does not, check the video domain’s connection separately; they are not the same connection.
Latency in a connectivity test is not a substitute for testing the actual request. A low latency value only shows that a response was received under those test conditions; it does not guarantee that website sign-in, long transfers, or UDP services will work. Retest the specific feature that is failing.
What Scene, On Demand, protocols, and subscriptions control
The Global Routing screen may also show Scene. It applies routing arrangements based on preset scene conditions; it is not a fourth fixed outbound mode. This guide focuses on Config, Proxy, and Direct. Before using Scene, check its conditions and associated settings rather than assuming where a connection will go based on its name.
- On Demand: Check Settings → On Demand. This feature primarily controls when a connection is established based on specified conditions; it does not lock traffic into Proxy mode. When troubleshooting automatic reconnections, check both On Demand and the current routing mode.
- Protocols: Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard determine the proxy connection’s protocol and parameters. Changing Global Routing will not automatically correct the protocol, server port, or authentication fields.
- Subscriptions: A subscription from a provider you already use can be used to retrieve and update proxy entries. After refreshing it, check whether the selected entry is still available and whether its address has changed. Updating a subscription does not confirm that the currently active routing rules are correct.
- Configuration files: Manage them in Config. A file may contain rules, strategies, DNS settings, and more. Switching configuration files can change routing results even if Global Routing still shows Config mode.
For example, if your provider specifies port 443, enter that port as instructed for the proxy entry. Switching to Proxy mode does not mean that any port will work. Port 443 is common, but the number alone does not indicate that the protocol uses TLS. Use the protocol and security settings from your existing configuration.
Everyday mode selection and final checks
Use Config for everyday routing when you need split routing and have verified the configuration. Temporarily use Proxy to check whether routing rules are affecting a particular request. Use Direct as a comparison when checking whether the current network can reach a destination without a proxy. Do not treat a setting that worked during one troubleshooting session as a lasting rule for every network.
- Go to Home and confirm that the selected proxy entry is the one you expect.
- Go to Config and check the active file, rule order, and strategy used by FINAL.
- Go to Home → Global Routing and restore the intended mode.
- Open one destination that should connect directly and another that should use a proxy. Start a new request for each and check the results.
- If you use On Demand, go to Settings → On Demand and check the trigger conditions.
Get Shadowrocket and continue setup
The iPhone / iPad app is a one-time $2.99 purchase on the App Store. The Mac (Apple Silicon / Intel), Windows, Android, and Linux versions are free. For iPhone / iPad system requirements, see the App Store listing. Visit the download page to choose a platform; to import your own configuration, continue to the setup guide.