Shadowrocket Features and Settings
First decide how traffic should be handled, then choose a server and rules. After connecting, check the results in Data and Diagnostics.
- Config Choose a policy based on rules
- Proxy Use the current server
- Direct Connect without a proxy
Global Routing: Choose How Traffic Is Handled
Open Global Routing from Home and choose Config, Proxy, or Direct. These options determine how traffic is handled after the client takes it over; they do not toggle the connection or replace server details. Return to Home to check the selected mode. To verify the proxy route, also confirm the selected server and connection status.
| Interface option | How it works | When to use it | What to check first |
|---|---|---|---|
| Config | Selects a policy using the rules in the active configuration. | When different requests need different routes. | The active configuration, rule order, and fallback behavior. |
| Proxy | Sends intercepted traffic through the current proxy server. | To check whether the server route can complete a request. | Whether the server selected on Home is correct. |
| Direct | Sends intercepted traffic without using a proxy server. | To compare a direct connection and see whether the issue is specific to the proxy route. | Whether the current network is available; this option does not turn off the connection. |
For troubleshooting, test the same request on the same network in each mode. If Proxy works but Config does not, check which rule matches and the policy it selects. If Direct also fails, check the network and destination service first. Switch back to your usual mode when testing is done.
Config and Rule: Route Traffic by Destination
Each rule has matching conditions and a policy to apply when it matches. In Config, find the active configuration and make a copy you can restore before editing its Rule section. Use DOMAIN for an exact domain and DOMAIN-SUFFIX for a domain suffix when appropriate. DOMAIN-KEYWORD matches domains containing a specified string, so it covers a broader range and should not replace a precise domain condition.
For address-based matching, IP-CIDR and IP-CIDR6 match IPv4 and IPv6 ranges, respectively. GEOIP matches based on an address's geographic classification; it does not verify the server's physical location. USER-AGENT relies on information visible in the request and is not a universal way to identify traffic from every app. A successful test for one domain also does not mean other domains used by the same service will match the same rule.
Policies and Match Order
PROXY sends matching traffic through a proxy, DIRECT connects directly, and REJECT denies matching requests. Rules are evaluated in order, and the first applicable match determines the policy. FINAL applies only when no earlier rule matches. In the example below, a specific host connects directly, other matching requests under the same suffix go through the proxy, and remaining requests connect directly. The example domains are for syntax illustration only.
[Rule]
DOMAIN,assets.example.com,DIRECT
DOMAIN-SUFFIX,example.com,PROXY
FINAL,DIRECT
Save the changes and confirm the updated configuration is active. Then select Config under Global Routing and test both the exception and fallback with new requests. If the suffix rule comes before the exact domain, it may override the exception. Avoid changing DNS, the current server, and multiple rules at once; otherwise, even if the issue disappears, it will be hard to tell which change helped. See the configuration reference for more fields.
Home: Servers and Subscribe
A server entry describes how to connect to a single endpoint; a subscription imports and maintains a set of existing entries. Both require you to already have your own subscription or server details. This site does not provide, sell, or recommend servers or subscriptions. Verify the source before importing, and do not post links, QR codes, or authentication details publicly.
Add Server: Enter a Single Server
From Home, open Add Server, select the protocol specified in your details, then enter the address, port, authentication, and applicable transport parameters exactly as provided. Fields differ by protocol and cannot be interchanged; check the original details if anything is unclear. After saving, return to Home and confirm the new entry is selected under SERVER. Run Connectivity Test, then verify with an actual request. A successful test only means that particular probe received a response; it does not mean every destination is accessible.
Subscribe: Import and Update a List
In the type selector under Add Server, choose Subscribe, enter your own subscription URL, and save. Return to Home to confirm the entries were imported. To refresh them, use the update action for that subscription. Check your current selection afterward, since the source list may remove entries or change their names. Do not treat a remote list as a local backup or assume entries are identical based on their display names alone. See the setup guide for first-time instructions.
On Demand: Start a Connection Based on Network Conditions
On Demand starts or adjusts the connection when the system detects matching network conditions; it does not select a policy for each request. Open On Demand in Settings and configure Wi-Fi or cellular behavior using the available options. After saving, check the connection when joining Wi-Fi, leaving Wi-Fi, and returning to the original network. If the system displays a permission prompt, read it carefully and complete the required confirmation.
If you want to use the client only on certain networks, start with the fewest conditions and test them before adding exceptions. The connection may need to be re-established when networks change; a brief status change alone does not indicate a server problem. To troubleshoot unexpected reconnections, temporarily turn off On Demand and connect manually for comparison. Also check whether another system connection profile is set to start automatically. Restore your original automatic connection settings after testing.
Data: Check Whether Traffic Uses the Expected Route
Data displays traffic recorded by the client. First check which stats view is open, then review upload, download, and total values. In the server view, readings show traffic attributed to the selected server; in the app view, they show records the client can attribute to the relevant app. These views are not separate additional usage, so do not add their totals together.
To verify traffic, note the current readings and network type, perform an easy-to-identify action such as reloading an uncached page, then return to the same view and compare the change. Background requests, caching, and delayed stats updates can affect the result. Client stats also differ from carrier billing in scope and billing period, so they are not a substitute for your bill. Before comparing across time periods, check whether stats were reset or the view changed.
Settings: DNS, Tests, Components, and Diagnostics
This guide uses the iPhone / iPad interface as a reference. If an option is in a different place on your device, follow the current interface. Note the original settings, change one thing at a time, and retest on the same network with the same request.
DNS: Check How Domains Are Resolved
Look for DNS options in Settings, and check in Config whether the active configuration specifies its own resolution settings. Note the original values, change one setting as needed for your network or service, then make a new request to the same domain after the change takes effect. If only local hostnames fail, check first whether they depend on the current network's resolver. DNS handles name resolution; it does not replace Global Routing or rules for routing traffic to a destination domain.
Test Method: Compare Results Consistently
Open Test Method in Settings, choose one of the available test methods, then return to Home and run Connectivity Test. Some tests only indicate whether a connection was established; others also depend on a response from the probe destination. When comparing results, keep the test method, probe destination, and network conditions the same. Even a low latency result should be confirmed with an actual request; it does not prove download speed or long-term reliability.
Today Widget: Check What the Shortcut Does
Check the Today Widget settings in Settings, then use the system widget editor to see whether the option is available on your device. After adding it, run an action from the widget and return to Home to check the connection status and Global Routing mode. The widget is a shortcut, not a separate routing setting. If its display differs from Home, rely on the status shown on Home and your test results first.
iCloud: Check Account and Sync Scope
Check the iCloud options in Settings and confirm that the system allows Shadowrocket to use iCloud. To sync between two devices, first make sure they use the same iCloud account and keep a copy of the current configuration. Then enable sync as prompted and check the result. Do not assume subscriptions, configurations, or every device-specific setting will be restored; check the active configuration and selected server on the other device as well.
Diagnostics: Keep Troubleshooting Details You Can Reproduce
Look for Diagnostics in Settings. When an issue occurs, note the network type, Global Routing mode, active configuration, and test results. Reproduce the issue with a request you can repeat, then compare the available DNS, connection, and rule details. Before sharing diagnostics, remove subscription URLs, server authentication details, and access records that should not be public. If the evidence points to one specific area, check the relevant topic in Troubleshooting first; there is no need to reset everything.