Shadowrocket Global Routing: Config vs. Proxy vs. Direct

Learn how Config, Proxy, and Direct route traffic in Shadowrocket, when to use each mode, and how to compare them for everyday use and troubleshooting.

At a glance

Shadowrocket’s Global Routing setting determines how connections handled by the app are routed. For everyday use, choose Config when you have a working configuration. Use Proxy briefly to compare behavior when you suspect a rule is matching incorrectly, or Direct to check local connectivity. This guide covers where to switch modes, how rule order affects routing, and how to test systematically—so you can tell a mode selection issue from a configuration error or an unavailable proxy connection. Not every page-loading problem is caused by the proxy server.

1. What Config, Proxy, and Direct Do

Global Routing controls how traffic is routed; it is not a connection toggle or a protocol type. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard are protocols used by connections. Global Routing determines whether requests follow rules or use the proxy or direct route uniformly. Switching to Proxy does not change a configured server to another protocol or fix its address, port, or authentication details.

Config: Route Traffic by the Active Configuration

Recommended

Requests are matched against the rules in the configuration, then handled according to the policy assigned to the matching rule. The result may be PROXY, DIRECT, REJECT, or a policy group defined in the configuration. If no earlier rule matches, a fallback such as FINAL determines the outcome; unmatched traffic does not necessarily go direct.

Best for: Everyday use with a working configuration and a mix of proxy and direct traffic

Proxy: Use the Proxy Route for All Handled Traffic

Connections handled by the app and available for processing use the proxy route instead of being routed individually by regular rules. The proxy server must still be reachable. This setting alone does not determine how DNS or traffic outside the app’s control is handled.

Best for: Brief proxy tests and comparing results with Config to identify rule issues

Direct: Use the Direct Route for All Handled Traffic

Connections handled by the app use the local network without being forwarded through a proxy server. Direct does not automatically select a faster route, nor does it mean the system VPN connection has stopped.

Best for: Checking local connectivity and briefly ruling out the proxy route

“All traffic through the proxy” and “all traffic direct” are shorthand for traffic handled by the app, not guarantees about every type of system communication on the device. To check an app’s behavior, review the actual request logs rather than relying only on the connection indicator in the status bar.

2. Switch Modes from Home: Know Which Setting You’re Changing

The steps below use the iPhone and iPad interface labels. Open Global Routing from Home, select Config, Proxy, or Direct, then return to Home to confirm the selected mode. Test with a new connection after switching. Existing long-lived web and background connections may continue using their previous route, so revisiting an already-open page may not confirm the change.

Home
Global Routing: Choose the Current Routing Mode
Config
Check the active configuration and its rules
Settings
On Demand: Review Automatic Connection Conditions
  1. On Home, first confirm that the node you intend to test is selected. A node appearing in the list does not mean it is currently reachable.
  2. To route traffic by rules, check which configuration is active in Config, then return to Home → Global Routing and select Config.
  3. Change one variable at a time: keep the same node, network, and test address, and switch only between Config and Proxy.
  4. After testing, restore your usual mode and reopen the target page to establish a fresh connection.

Some versions of the interface also show Scene. It organizes routing choices around scene conditions; it is not simply another “proxy everything” button. If Scene is configured, check its conditions and behavior first. For repeatable troubleshooting, explicitly select Config, Proxy, or Direct rather than letting Scene change during the comparison.

The Config Tab and Config Mode Are Different

Opening the Config tab is for managing configurations. Selecting Config under Global Routing tells the app to route traffic according to the active configuration. Merely opening a configuration file does not prove that current requests are being routed by its rules.

3. Why Config Doesn’t Simply Mean “Proxy Overseas, Direct Everywhere Else”

Config applies specific rules; its name does not automatically create a region-based routing setup. Rules are generally checked from top to bottom, and the first matching rule determines the policy. The same node can therefore behave differently with different rules. The examples below illustrate syntax and order; they are not a complete configuration to use in place of your own.

[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY

A configuration may also contain REJECT rules, rule sets, or named policy groups. For example, if an earlier REJECT rule matches, adding a PROXY rule later will generally not override it. If a site works with Proxy but not Config, check which rule and policy matched the request instead of deleting all the rules.

DNS resolution also affects the matching results you can observe: matching by domain and matching by IP are not the same process. Record the full hostname during testing. A single page may request resources from separate hostnames for the main site, images, and login, so allowing only the main domain may not restore all functionality.

4. Use Different Approaches for Everyday Routing and Troubleshooting

Everyday settings should make each type of request follow a verified policy; troubleshooting settings should help narrow down the cause. These goals are different. Proxy is useful for comparison, but a site loading in Proxy mode does not mean keeping all traffic on the proxy route is the best long-term setup.

Setup Guide: Everyday Routing and Temporary Tests

Everyday use
  • In Config, confirm the active configuration and check the fallback policy in FINAL.
  • Go to Home → Global Routing and select Config.
  • Test one address that should use the proxy and one that should connect directly.
  • Keep only the specific rules needed for local network access; don’t broaden the match unnecessarily.
Troubleshooting
  • Keep the node and local network unchanged, then test with Proxy.
  • Test with Config next and record how the same hostname behaves.
  • Use Direct with an address that should already be reachable directly to check the local network.
  • After comparing results, restore Config and verify that any changes took effect.

Change only one setting per test. Changing the node, network, and rules at the same time makes results difficult to compare.

When accessing a router or local network device, distinguish between hostnames and private IP addresses. For example, 192.168.1.1 is within the 192.168.0.0/16 range above, while 10.0.0.1 is not. Adding a rule for one range does not automatically cover all private addresses. Use the range that matches your network, and don’t route all requests through Direct just to fix access to one address.

5. Diagnose the Mode, Rules, or Connection Settings

Record test conditions alongside the results. “Doesn’t load” needs more detail: note the mode, network, hostname, and whether the failure is a DNS lookup error, connection timeout, or missing page resources. The table below suggests what to check; one test alone is not conclusive.

Observed resultCheck firstNext step
The same address works in Proxy but fails in Config Rule match, REJECT, policy group selection, or DNS differences Check the request log for that hostname and verify the applied policy and rule order.
Proxy fails, but Direct opens an address that should be reachable directly Proxy server connectivity, authentication, or protocol settings Check the server address, actual port, and provider-supplied settings; then test connectivity to the node.
Neither Proxy nor Direct opens an address that should be reachable directly Local network, DNS, or the destination service Check Wi-Fi or mobile data, then compare with another known-direct address.
The main page loads, but images or login fail Related hostnames may use different policies, or their connections or DNS lookups may be failing separately Check image and login requests separately; don’t test only the main page hostname.

The server port must match the actual settings provided by your service provider. Websites commonly use HTTPS on port 443, but that does not mean a proxy server must use 443. Changing an unknown port to 443 will not fix authentication or protocol errors. You also can’t determine whether a node uses Trojan or VLESS from its port number. Get the settings from your service provider and verify them one by one.

  1. On the same network, choose one node and record the test address and current mode.
  2. Start with a new request using Proxy. If it fails, check the connection settings before editing rules.
  3. If Proxy works, switch to Config. If it fails only there, check the matched policy and active configuration.
  4. Use Direct with an address known to work without a proxy as a local network check. Don’t use an address that requires a proxy to decide whether direct access is working.
  5. Change only the identified problem setting, restore Config, and repeat the same tests.

6. FAQs: Connection Indicator, On Demand, and Subscription Updates

The VPN indicator is on. Why does it still seem like the proxy isn’t working?

The system connection indicator shows that the tunnel is connected; it does not mean every request is using the proxy. First, go to Home → Global Routing and check whether Direct is selected. If Config is selected, check whether the target request matches a DIRECT policy. Finally, confirm that the node can connect; don’t judge the route by the icon alone.

Proxy is selected and the latency test passes. Why do webpages still fail?

A latency test checks only a specific test operation; it does not verify full access to the target website. Open the same address in a new tab and check DNS, the destination port, TLS, and server status. If there’s an error, note its type. A single test result does not establish webpage throughput or availability for every destination.

Why does it still connect automatically after I switch to Direct?

Direct is a routing mode, not a way to stop automatic connections. Go to Settings → On Demand and check for conditions that trigger a connection. To stop the connection, use the connection toggle and review On Demand as well. Don’t repeatedly switch Global Routing modes to manage automatic connection settings.

I refreshed the subscription. Why is the website still using the wrong route?

Updating a node with Subscribe and changing routing rules in Config are separate operations. First check whether you updated a node subscription or a configuration, then confirm which configuration is active. Get subscription URLs from your service provider, and don’t expose the full address, token, or authentication details in screenshots or public logs.

Proxy works. Does that mean I can stop using Config?

One successful test is not enough to make a permanent decision. Find the specific rule causing the difference in Config, adjust it as needed, then verify local network access, everyday direct-access addresses, and addresses that require a proxy. Restore your intended settings after testing so a temporary mode does not affect later checks.

A reliable order is to check the local network first, the proxy connection second, and the rules last. Global Routing helps you test these layers separately; it is not a switch that fixes every problem. Keeping test conditions, request hostnames, and matched policies is more useful for troubleshooting than repeatedly importing configurations.

Get Shadowrocket and Read the Getting Started Guide

Get the iPhone / iPad version from the App Store for a one-time payment of $2.99. The developer is Shadow Launch Technology Limited; check the App Store listing for system requirements. The Mac (Apple silicon / Intel), Windows, Android, and Linux versions are free. The app does not include proxy services; get subscription links from your service provider.

Download Shadowrocket