For everyday use, Shadowrocket (Shadowrocket) is usually set to Config, which routes traffic according to the active configuration’s rules. If you suspect a rule is sending a request the wrong way, temporarily compare with Proxy. To check whether your local network can connect directly, use Direct. This guide assumes you already have your own service provider and subscription. It explains what each option affects, how to switch between them, and how to interpret the results. It also distinguishes Global Routing from Scene and On Demand, so you don’t mistake a routing choice for a connection toggle.
Choosing Config, Proxy, or Direct
Global Routing is a routing policy setting, not a proxy protocol. It determines how Shadowrocket routes requests it handles; it won’t turn Shadowsocks into VMess or supply connection details missing from the server. The recommendations below assume your active configuration is usable and its rules have been checked.
Config: Follow the configuration
RecommendedRoutes requests according to the rules and policies in the active configuration. A match can result in DIRECT, PROXY, REJECT, or a policy group defined in the configuration. A final rule such as FINAL handles requests that don’t match an earlier rule.
Best for: Everyday use when you need direct, proxy, and reject rules to work together.
Proxy: Use the proxy policy for all requests
Routes ordinary requests within Shadowrocket’s handling scope through a proxy, rather than relying on standard routing rules to choose a destination for each one. A working proxy server is still required, and this does not mean all system traffic uses the same route.
Best for: Briefly testing the proxy path or checking whether standard routing rules are affecting access.
Direct: Connect directly
Connects ordinary requests within Shadowrocket’s handling scope directly to their destinations, without using a proxy server as the exit. This is a routing choice, not the same as turning off the connection switch at the top of Home.
Best for: Checking direct access between your local network and a destination as a troubleshooting comparison.
“Global mode” can sound like “send everything through the proxy,” but Global Routing is simply the name of this setting. Selecting Config doesn’t mean everything goes direct, and selecting Proxy doesn’t guarantee a successful connection. First check which mode is selected, then verify how the request is actually routed.
How to switch modes from Home
These steps use the iPhone / iPad interface labels. Before switching, note the current mode, selected server, and active configuration. During troubleshooting, change only one variable at a time. Get your subscription from your service provider. If your server list isn’t ready, import it before testing Proxy.
-
Note the current state
On Home, check the connection status at the top, the current Global Routing value, and the selected item in the SERVER list. Then open Config and confirm which configuration is active. Record names only; don’t share configuration contents that may include credentials.
-
Select a routing mode
Go to Home → Global Routing and select Config, Proxy, or Direct for your test. Return to Home and confirm the displayed value. Don’t replace the server and configuration file at the same time.
-
Connect for the test
Use the switch at the top of Home to connect. If prompted to add a VPN configuration for the first time, follow the system prompts to authorize it. After changing modes while connected, make a new request to the destination rather than relying on a page that’s already open.
-
Retry the same destination
On the same network and with the same server selected, open the same destination again. Note whether you see a DNS resolution error, connection timeout, or incomplete page load. A browser may reuse an existing connection, so close the page and retry if needed.
-
Restore your everyday settings
When the comparison is complete, go to Home → Global Routing → Config and check your usual destinations again. If you paused On Demand, also go to Settings → On Demand and restore its previous settings.
Check connection status and routing separatelyA connected status on Home means the tunnel is established; it doesn’t mean the remote server can reach every destination. Conversely, selecting Proxy in Global Routing without connecting doesn’t show that requests are going through the proxy.
How Config determines where requests go
Config works by matching rules. In general, put more specific rules first and the final fallback last. The first matching rule determines the policy for a request. “Rule-based” doesn’t mean the client automatically decides how every website should be routed; the actual result depends on the active configuration.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY
This example explains rule order only; it is not a complete configuration to replace your current settings. example.com is an example domain, and 192.168.0.0/16 is an example private address range that does not cover every LAN address. Before using similar rules, check that the policies are defined in your configuration and that the intended proxy is selected.
| Rule keyword | What the example does | What to check |
|---|---|---|
DOMAIN-SUFFIX | Matches example.com and its subdomains, then sends them to PROXY. | A page may also request resources from other domains, so don’t check only the domain in the address bar. |
IP-CIDR | Uses DIRECT for destinations in 192.168.0.0/16. | no-resolve means this rule won’t trigger an additional DNS lookup for matching. |
GEOIP | Uses DIRECT for destinations classified as CN in the IP geolocation database. | A database classification does not identify where a website’s content or operator is based. |
FINAL | Uses PROXY when no preceding rule matches. | FINAL can specify a different policy; don’t assume every configuration defaults to proxy or direct. |
If the active configuration ends with FINAL,DIRECT, requests that don’t match an earlier rule connect directly. In that case, if a destination works in Proxy but fails in Config, a relevant domain may be missing, or the destination may match an earlier direct or reject rule. Check which rule matched instead of replacing the entire configuration.
Troubleshoot with Proxy and Direct comparisons
For a useful comparison, keep the local network, destination, selected server, and test period the same; change only Global Routing. The observations below suggest troubleshooting directions—they aren’t fabricated speed-test results, and one successful or failed attempt doesn’t identify the cause on its own.
Compare two modes for the same destination
Compare Config with Proxy
- Config fails but Proxy works: Check matching rules, policy group selections, and the final policy first.
- Both fail: Check server availability, DNS, the destination itself, and your local network.
- Config works but Proxy fails: Check whether the successful request used DIRECT and whether the current proxy exit can reach the destination.
Compare Direct with Proxy
- Direct works but Proxy fails: Check the proxy connection details, exit status, and how the destination responds to that exit.
- Direct fails but Proxy works: The two routes produce different results; that alone doesn’t point to a DNS problem.
- Both work but speeds differ: Check connection reuse, caching, and server load. Don’t draw conclusions from a single page load.
After each switch, make a new request and check the connection logs for the destination, matched rule, and policy. Identify the difference first, then change the relevant setting.
Connectivity Test on Home can help with basic checks, but its result is not the same as loading a full website. A page may use multiple domains, ports, and transport methods. If the homepage opens but images don’t load, check the failed requests individually instead of treating the homepage as proof that the entire route is working.
Modes don’t automatically fix DNS, protocols, or ports
Global Routing changes policy selection; DNS settings handle name resolution. They can affect each other, but they are not the same thing. Proxy doesn’t necessarily send all DNS queries to a remote resolver, and Direct doesn’t automatically restore system-default DNS. The actual DNS path also depends on the active DNS, tunnel, and related settings.
- Check the stage where the error occurs: If the domain can’t be resolved, check DNS first. If it resolves to an IP address but the connection times out, check routing, the exit, and the destination port.
- Then check the server details: Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard are different protocol types with different requirements. Switching to Proxy won’t correct the address, port, key, or TLS settings.
- Distinguish the destination port from the server port: HTTPS websites commonly use destination port 443. Use the proxy server port provided by your service provider; don’t change every server port to 443.
- Keep records you can review: Note the network type, mode, error message, and when it occurred. Before sharing a screenshot, hide subscription URLs, passwords, keys, and other sensitive information.
If you recently updated your subscription, first check whether the server list changed and whether the selected server is still valid. Subscription updates primarily provide connection details from your service provider; they should not be assumed to fix local Config rules. Check the updated contents separately.
What Scene and On Demand do
In addition to the three options compared here, Global Routing may also use Scene. Scene applies routing choices according to configured scenarios; it is not a fourth proxy protocol. When troubleshooting, check the active scene and the settings it applies. Otherwise, you may think you’re testing Config while a scene condition is affecting the result.
| Setting or option | What it does | How to handle it when troubleshooting |
|---|---|---|
| Home → Global Routing | Select a routing mode such as Config, Proxy, or Direct. | Set one mode manually, test it, then switch to the next. |
| Global Routing → Scene | Applies routing choices according to configured scenes. | Check the scene conditions and results. For a manual comparison, confirm which mode is selected. |
| Settings → On Demand | Controls connection behavior based on On Demand conditions. | If the connection starts again after you turn it off, first check whether On Demand is enabled and review its conditions. |
| Config | Manages configuration files and their rules and other settings. | Confirm which file is active; don’t edit a copy that isn’t in use. |
On Demand controls when a connection is established; Config rules control which policy a request uses. They are not interchangeable. To test the system’s direct connection with Shadowrocket disconnected, turn off the switch at the top of Home and check whether On Demand will reconnect. Don’t mistake an automatic reconnection for Direct not working.
Restore and check settings after testing
For everyday use, return to a configuration state you can understand and verify instead of leaving Proxy selected as a temporary troubleshooting measure. If a destination works only with Proxy, fix the specific rule causing the difference. If the proxy server itself is unavailable, check the connection details from your service provider; don’t mask a connection problem by changing rules at random.
- Home → Global Routing is back to the expected mode. If using Config, make sure Config has the verified configuration file enabled.
- The selected item in SERVER is valid. If you need to update your subscription, get it from your service provider and check the updated server list.
- Make a new test request to a LAN destination, a destination that normally connects directly, and one that requires a proxy.
- Restore the intended state in Settings → On Demand and confirm that changing networks won’t trigger an unexpected connection.
- Keep a copy of the configuration from before your changes and modify only one rule type at a time. For more syntax details, see the rule reference.