HOME / GLOBAL ROUTING
Three common Global Routing modes
For everyday rule-based routing, choose Config. To temporarily test the proxy route, choose Proxy. To check whether the current network can reach a destination directly, choose Direct. Open Global Routing on Home, select a mode, then return to Home and check the selected mode and connection toggle. This changes how connections are routed; it does not switch servers or turn the connection off.
| Interface option | How connections are handled | When to use it |
|---|---|---|
| Config | Uses the rules in the current configuration to choose a policy for each matching request. | Everyday routing; checking whether a domain matches the expected rule. |
| Proxy | Connections handled by the app use the proxy, rather than being individually routed by rules. | Temporarily test the proxy route without changing servers. |
| Direct | Connections handled by the app are sent without going through a proxy server. | Test direct access to a destination on the current network. |
For troubleshooting, keep the network, destination, and server the same. Change one mode at a time and make a new request after each change. If Proxy works but Config doesn’t, check which rule actually matched, especially broad rules and the fallback policy. If both Direct and Proxy fail, switching modes alone won’t identify the cause; also check the network, DNS resolution, or destination service. Restore your original mode when testing is complete so temporary settings don’t affect everyday use.
CONFIG / RULE
Rules & Routing: Match Scope and Policies
Each rule consists of a match condition and an action. Select Config on Home, then open Config and confirm which configuration is active. Before editing, keep a copy you can restore, and place more specific conditions before broader ones. Rules are generally evaluated in order: once a rule matches, a more specific rule below it won’t override the match.
Common match types
DOMAINmatches an exact domain. Use it for a single host instead of applying the rule to an entire site.DOMAIN-SUFFIXmatches a domain and its subdomains.DOMAIN-KEYWORDmatches a string anywhere in a domain and can cover more than expected.IP-CIDRandIP-CIDR6match IPv4 and IPv6 ranges, respectively.GEOIPmatches the destination IP using geolocation data, not the domain suffix.- Place
FINALat the end of the rule list to handle connections that didn’t match earlier rules. Changing it affects every destination without its own matching rule.
Policy and order example
PROXY routes matching connections through the proxy, DIRECT sends them directly, and REJECT blocks them. This example illustrates rule order only; it isn’t a general-purpose configuration. For requests under example.com, the individually specified host matches the first line, while other requests matching the suffix condition match the second.
DOMAIN,assets.example.com,DIRECT
DOMAIN-SUFFIX,example.com,PROXY
FINAL,DIRECT
A page may contact different domains for sign-in, images, and API requests. If part of the page fails to load, identify the failed request first, then check whether an earlier rule matched its domain. Don’t broaden the rule to cover an entire domain suffix without checking. After saving changes, make sure the edited configuration is active, then test with a new request. See the rule keyword guide for more on match scope.
HOME / SUBSCRIBE / ADD SERVER
Subscriptions and Server Management
Use Subscribe when multiple servers are managed through the same subscription. If you have connection details for a single server, enter them manually with Add Server. Get subscription links from your service provider. Use the relevant add option on Home, then check that the expected entries appear in the list and select the server you want to use. An entry appearing in the list confirms only that it was imported, not that the server is working.
When adding a server manually, check the protocol against the details you have, then enter the address, port, and required authentication fields. The fields vary by protocol. If a detail is missing, check the original connection information rather than entering a value from another protocol. If you use Scan QR Code to import an existing code, verify the imported entry’s protocol and name afterward.
After updating a subscription, check that the selected entry is still present, then use Connectivity Test to check whether it can be reached. Give manually added and subscription entries distinct names so you can identify the right one when updating or deleting. Test results reflect only the selected test method and network conditions at that time. Even if a test succeeds, try the service you actually plan to use. Subscription URLs may contain access credentials, so share only details with sensitive fields removed when troubleshooting. See the server management guide for step-by-step instructions.
SETTINGS / ON DEMAND
On Demand: Automatic Connections
On Demand determines when a connection starts automatically based on conditions. Global Routing determines how requests are handled after the connection is established. Check On Demand in Settings. Before enabling it, connect manually and confirm that system permissions, the server, and the current routing configuration all work. Otherwise, an automatic connection failure can be hard to distinguish from an unavailable server.
Set the conditions you need for Wi-Fi or Cellular, then switch from the current network to the other and return to Home to check the result. If the app lets you set conditions for specific Wi-Fi networks, enter the network name and test on that network; don’t assume the condition works just because it saved successfully. Check the connection status before and after switching, and make a new request. Cached pages and existing connections can’t confirm whether the network change triggered a connection.
If the connection comes back after you disconnect manually, check whether the current network still meets the On Demand conditions. To test without automatic reconnection, turn off On Demand before disconnecting manually. When you’re done, restore the original settings and test a network switch. This helps distinguish automatic triggers from manual toggle behavior.
DATA / TRAFFIC
Data: Traffic Stats
Data shows cumulative upload and download totals. It isn’t a live speed meter or your provider’s billing statement. Open Data and check the current view: by server, it shows traffic recorded under each server; by app, it shows traffic the client can attribute to each app. These views answer different questions, so their figures don’t need to match item by item.
To check the effect of an action, note the current reading and unit, open just one destination, then return to the same view and check the increase. Before clearing stats, record any readings you still need; after clearing, note the new starting point. Caching, background requests, and reused connections can all affect the totals. No noticeable change in a server’s traffic alone doesn’t prove that a request used DIRECT. To confirm the route for a specific request, also check Global Routing and any available diagnostic records. See Data traffic stats explained for details on how the figures are grouped.
SETTINGS / CHECKLIST
Common Settings
DNS: Check Where It Takes Effect
DNS resolves domain names to the addresses needed to connect. Check the DNS options in Settings, then open Config to see whether the active configuration specifies a separate resolution method. Before making a change, note the current value and change one option at a time. Test again with a new request to the same domain. Successful resolution only means an address was returned; it doesn’t guarantee the connection will work. If the issue persists, check the routing policy and server too.
Test Method: Keep Test Conditions Consistent
Test Method determines how Connectivity Test checks a connection. Find Test Method in Settings, select a method, then return to Home and test the same server again. To compare results, keep the network and test method consistent. If you change the method or destination, don’t compare the two readings directly to decide whether the server is faster or slower.
Today Widget: Check the Shortcut
Today Widget provides a shortcut in the system’s widget area, where supported. Check the Today Widget option in Settings, then add or manage the widget using the system’s controls. After using the widget, return to Home and check Shadowrocket’s connection toggle and Global Routing. The shortcut’s appearance doesn’t confirm which rule matched a request.
iCloud: Check What Syncs
Before syncing across devices with iCloud, check the sync options and which content is allowed to sync in Settings. Make sure both devices use the intended iCloud account. Keep a local copy of anything you need before enabling sync. After syncing, check each configuration file, the selected configuration, and the servers. Sync status isn’t a full backup, and connection status shouldn’t be assumed to transfer with the configuration.
Diagnostics: Capture a Reproducible Issue
Diagnostics can help determine whether an issue is related to DNS resolution, routing, or the connection. Check the available information under Diagnostics in Settings. Note the current network, Global Routing mode, server, and time of failure, then reproduce the issue once. Focus on records that match the request time; errors from before a network change may not explain the current issue. Before sharing records, remove subscription links, authentication details, and any access logs that aren’t needed.
If several settings are enabled at once, start troubleshooting from a state where you can connect manually, then restore settings one at a time. Test the same destination after each change to identify which settings affect the connection. For a first-time setup, follow the steps in the user guide.