Shadowrocket’s Global Routing setting determines how connections handled by the app are routed. This guide is for users who have already added their own connection details but aren’t sure which mode to choose. Compare Config, Proxy, and Direct, then use rule examples and tests against the same URL to narrow down a problem. Start with Config for everyday use; switch to Proxy or Direct temporarily for a specific reason, then restore your original setting when you’re done.
1. Global Routing selects an outbound route; it doesn’t turn the connection on or off
Open Global Routing on Home to choose how traffic is handled. The connection toggle on Home starts or stops the client connection; Global Routing determines how traffic is handled while the connection is active. Selecting Proxy does not establish a connection, and selecting Direct does not turn off the system VPN connection. Check these controls separately.
This guide compares the three basic modes: Config, Proxy, and Direct. You may also see Scene in the menu. Scene applies handling based on configured conditions and is separate from the three basic modes. When troubleshooting, note your current Scene setting, then select one basic mode to avoid automatic switching affecting the results.
“Via proxy” and “direct” below refer to connections handled by Shadowrocket. They don’t mean every network packet on the device necessarily follows the same route. Tunnel exclusions, system routing, and DNS settings can also affect the outcome. Don’t rely on the VPN icon alone to determine which route a website is using.
2. When to use Config, Proxy, or Direct
Config: Follow the active configuration
RecommendedUses the rules in the active configuration to choose a policy. Rules can specify DIRECT, a proxy policy, or REJECT. If no earlier rule matches, a fallback such as FINAL determines the route; traffic does not automatically go direct.
Best for: everyday use when you’ve checked the rules and want different destinations to use different routes.
Proxy: Use a proxy route for all traffic
Applies proxy handling to regular connections managed by the client instead of routing each one according to the rules in Config. Check the currently selected proxy and relevant policy settings to see which route will actually be used.
Best for: temporarily routing all traffic through a proxy, or checking whether a problem is related to your configuration rules.
Direct: Connect directly
Uses direct connections for regular traffic managed by the client, without forwarding it through a remote proxy. The client may remain active, and Direct alone does not rule out effects from settings such as DNS.
Best for: checking access on your local network or temporarily reaching resources that require a local route.
Config is the best everyday choice when the active configuration meets your needs. It routes different destinations according to explicit rules; it doesn’t guarantee that every website will be reachable. If FINAL points to a proxy, most connections that aren’t matched by an earlier rule will use that proxy. If FINAL points to DIRECT, unmatched connections will connect directly.
Proxy isn’t a “speed boost” switch, and Direct isn’t a “battery saver” switch. Speed and battery use depend on factors such as network quality, remote response times, and connection duration. Switching modes changes the route selection logic; it doesn’t guarantee lower latency or a successful connection.
3. How Config matches rules: specific conditions first, FINAL last
In Config, confirm which configuration file is active, then check its [Rule] section. Rules are evaluated in order, and the first match determines the policy for that connection. Put specific conditions before broader ones, and place FINAL at the end as a fallback. If FINAL appears earlier, subsequent rules won’t get a chance to match.
[Rule]
DOMAIN-SUFFIX,example.com,DIRECT
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY
This snippet illustrates rule order; it is not a complete configuration file. PROXY must refer to a proxy policy that is valid in your current setup. If your configuration uses a different policy name, check its definition first. Copying the last line alone does not make a proxy available. example.com is a sample domain, not a recommendation to use a particular route for any real service.
DOMAIN-SUFFIX,example.com,DIRECT: Matches the domain and its subdomains, such aswww.example.com. It does not search webpage paths or arbitrary text.IP-CIDR,192.168.0.0/16,DIRECT,no-resolve: Matches the specified IPv4 range.no-resolvemeans this IP rule won’t trigger an additional domain lookup; it does not disable DNS altogether.GEOIP,CN,DIRECT: Matches based on the destination IP’s location in a geolocation database, not the language displayed by a website. The database’s result may not match the region where the website’s content is hosted.FINAL,PROXY: If none of the preceding rules match, this sends the connection to the policy namedPROXY. No domain or IP condition is specified here.
For example, when connecting to a local network service at the known IP 192.168.1.10, the second rule can route it to DIRECT. When visiting www.example.com, the first rule matches before FINAL is reached. To route a specific domain through a proxy, adjust its domain rule or policy instead of leaving Proxy on to bypass all routing rules.
4. How to switch modes and compare results
Before testing, choose a local destination you know is reachable and a remote destination you want to check. Use your existing connection details and subscription throughout. Don’t change the proxy, DNS, configuration file, and network at the same time. Change only Global Routing so you can interpret the results.
- On Home, note the selected proxy and Global Routing mode; in Config, note which file is active. If you’re using Scene, record the relevant scene too so you can restore it after testing.
- Make sure the connection toggle is on. Select Config, open the URL you want to check, and note the exact result—for example, “connection timed out,” “certificate error,” or “page loads, but some resources fail.”
- Change only Global Routing to Proxy, then reconnect to the same destination. If needed, close and reopen the page to prevent the browser from reusing an existing connection.
- Next, switch to Direct and test the same destination the same way. Note whether you’re on Wi-Fi or cellular data, and don’t compare results from different networks.
- When you’re done comparing, restore Config or your original Scene. If you edited a configuration file, confirm that the updated file is active.
Compare results with the destination and network unchanged; switch modes only
Config fails; Proxy works
- Check whether the active configuration routes the destination to DIRECT, REJECT, or another unavailable policy.
- Check whether an earlier DOMAIN-SUFFIX, GEOIP, or IP-CIDR rule matches first.
- Check FINAL and the policy group’s actual selection, not just the name at the end of the rules.
Proxy fails; Direct works
- Check the selected proxy’s connection details, availability, and reachability from the remote end.
- Check whether the destination requires a local network route, such as a device on your LAN.
- Fix the proxy or add a rule for the destination instead of assuming Config itself is the problem.
Comparing modes can narrow down where to look, but DNS, reused connections, and server-side restrictions can still affect the outcome. A single successful test doesn’t confirm the root cause.
If all three modes fail, check your local network, whether the destination service is reachable, DNS results, and your connection details. If only images or login requests on a page fail, check the other domains those requests use instead of adding a rule just for the main domain in the address bar.
5. On Demand, protocols, and subscription updates don’t replace mode selection
Settings → On Demand controls when a connection is started based on configured conditions. It serves a different purpose from Global Routing: On Demand affects when a connection starts or resumes, while Global Routing selects an outbound route once the connection is active. If the connection comes back after you turn it off manually, check On Demand and the active scene conditions rather than repeatedly switching between Proxy and Direct.
- Protocols: Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard specify connection methods and related parameters; they are not Global Routing modes. Changing protocols won’t automatically switch Config to Proxy.
- Subscriptions: Updating a subscription typically refreshes connection details you already have. A subscription containing proxy nodes is not the same thing as a full configuration file. After an update, check which item is selected and which configuration is active.
- Rules: Policy references in your rules may stop matching your expectations after the list changes. If a problem starts after an update, check the policy references and actual route instead of repeatedly importing the list.
- DNS: Resolving an address doesn’t mean a connection can be established, and selecting Direct doesn’t necessarily restore system-default DNS. Record DNS results and connection results separately when troubleshooting.
This site does not provide, sell, or recommend proxy nodes or subscriptions. You should already have your own provider and connection details before following this guide. When contacting your provider for help, don’t share your full subscription URL, access token, or private key.
6. FAQ: Proxy fixed the problem—should I leave it on?
Config can’t open the site, but Proxy can. Is my configuration broken?
Not necessarily. First, check which file is active in Config, then review the rules and policies matching the destination domain. The destination may simply be assigned to DIRECT, or a policy group may be using an unavailable route. Fix the relevant rule and retest in Config; you don’t need to replace the entire configuration right away.
Why does LAN access change after I select Proxy?
Proxy changes how the client handles connections it manages. First, test the same LAN IP with Direct. Then return to Config and check the LAN subnet rules and tunnel exclusions. For example, if your network uses 192.168.1.0/24, check that the rules cover that range instead of copying an address from another network.
Why does the VPN icon still appear when Direct is selected?
Direct is a traffic-handling mode, not a way to stop the connection. To stop the client connection, use the connection toggle on Home. If it reconnects automatically afterward, check Settings → On Demand and the scene conditions. To determine which route a request uses, check its request details instead of relying on the system icon.
Why does the same page look unchanged after switching modes?
The browser may show cached content or reuse a connection opened before you switched modes. Close the page and make a new request; if needed, disconnect and reconnect before comparing the same destination. A page displayed from cache doesn’t prove that a new connection succeeded.
Will updating a subscription automatically switch Global Routing to Config?
Don’t treat a subscription refresh as a mode reset. After an update, check Global Routing on Home and confirm the active file in Config. If you use Scene, check which scene is selected too. Check connection details, rule files, and routing mode separately.
You can reduce everyday checks to three questions: Is the connection on? Which Global Routing mode is selected? Which rule does the destination match in Config? Checking in that order makes it easier to spot differences than changing several settings at once. After a temporary test with Proxy or Direct, restore your original setting and retest the destinations you use regularly.