Official Guide · Features & Settings
Shadowrocket Proxy Modes and Settings
First decide how Global Routing should handle connections, then adjust rules in Config and specific options in Settings. Modes, servers, and DNS operate at different levels. Change one setting at a time to identify what caused a difference.
- Global Routing: Choose a handling mode
- Config: Set rules and policies
- Diagnostics: Find where the problem occurs
This guide uses the iPhone / iPad interface as an example. Menu locations may vary by system and app version; use the options shown on your device. If you’re new to Shadowrocket, start with the Getting Started Guide. To get the app, visit Download Shadowrocket.
Features and SettingsContents
If connections work but routing results are unexpected, start with the first two sections. If you can’t connect, check the server details first, then DNS and Diagnostics.
Config, Proxy, and Direct: A Comparison
Global Routing determines how connections are handled overall. It is not a server in the server list or the system’s connection switch.
Find Global Routing on Home and choose Config, Proxy, or Direct to suit your needs. Config applies policies from the current configuration; Proxy sends connections handled by the app through a proxy; Direct connects those connections to their destinations without a proxy. These modes apply to traffic handled by the app and do not guarantee the behavior of every system connection.
| Mode and meaning | When to use it | Check before switching | Common confusion |
|---|---|---|---|
| Config · Configuration | For everyday routing by domain, address, and other conditions. | Select the correct configuration in Config and check its rules and FINAL. | Switching to Config does not add missing rules or fix incorrect server details. |
| Proxy · Proxy | To briefly check whether the selected server can reach a destination. | Confirm that the selected server, protocol settings, and basic network connection are working. | Not a reliable way to verify rules: Proxy does not route traffic according to the same rules as everyday Config mode. |
| Direct · Direct | To check whether the basic network can reach a destination without a proxy server. | Choose a specific test destination and note the current mode before switching. | Direct does not turn off the connection switch; the app may remain enabled. |
Switch modes for the test, then restore your usual settings
For example, if a website works in Proxy but not Config, first check which rule matches the connection in Config rather than immediately changing servers. If even basic websites fail in Direct, check Wi-Fi, cellular service, or network sign-in. After each mode change, make a fresh request. If needed, close and reopen the page to avoid reusing an existing connection.
After comparing modes, restore your original Global Routing setting. Don’t change modes, switch servers, and change DNS all at once, then attribute the result to just one change. Even if access returns temporarily, that approach won’t produce a repeatable diagnosis.
Rule Matching and Policy Selection
Rules define which connections match; policies define how to handle them. Set Global Routing to Config before checking.
View or edit rules in the active configuration under Config. Common rule types include DOMAIN for an exact domain match, DOMAIN-SUFFIX for a domain and its subdomains, DOMAIN-KEYWORD for text contained in a domain, and IP-CIDR or IP-CIDR6 for address ranges. GEOIP relies on an IP database; it does not simply indicate a website’s language, company ownership, or the actual location of a server’s operator.
PROXY sends matching connections through a proxy, DIRECT connects them directly, and REJECT blocks them. Rules may also refer to policy names defined in the configuration. Make sure each referenced name exists and points to the intended policy. Similar spellings do not mean the same policy; after importing, check that the configuration loads correctly.
[Rule]
DOMAIN,example.com,PROXY
DOMAIN-SUFFIX,example.org,PROXY
IP-CIDR,192.168.0.0/16,DIRECT
FINAL,DIRECT
These are syntax examples. example.com and example.org are not recommendations for sites that need a proxy. The first line matches only the specified domain; the second covers example.org and its subdomains; the third sends private address ranges direct. FINAL goes last and handles connections that did not match an earlier rule.
Check the order, then the rule scope
Rules are generally evaluated in order, and the first match determines how a connection is handled. A broad rule near the top may prevent a more specific exception below it from taking effect. Add specific exceptions first, then broader matches, and check FINAL last. DOMAIN-KEYWORD can match more than expected: it looks for text, not a fixed set of complete domains for a particular website.
Keep a copy of the original configuration before editing. Save your changes and confirm the updated configuration is active. A webpage may also request separate domains for images, sign-in, or APIs, so loading the homepage does not mean every feature works. To route only specific sites through a proxy, see Using DOMAIN-SUFFIX and FINAL for Specific Sites.
Subscriptions and Server Management
Subscribe manages server sources that can be updated; Add Server is for entering a single server. Both require valid connection details.
On Home, use the add option to open Add Server. Choose the Type that matches your server details, then enter the address, port, and authentication information. For a subscription link, use the relevant Subscribe option to import it. For a QR code, use Scan QR Code. Get subscription links from your provider. When copying one, check for leading or trailing spaces, line breaks, or accidentally copied instructions.
Shadowsocks, VMess, VLESS, Trojan, HTTP, SOCKS5, WireGuard, and Hysteria2 are different protocols or connection types; their settings are not interchangeable just because the names look similar. Choosing the wrong Type can prevent a connection even when the address and port are correct. Match TLS, SNI, and transport settings to the original details. Don’t weaken certificate verification just to clear a warning.
Updating a Subscription vs. Editing a Server
Updating a subscription fetches its server list again. Changes made directly to subscription-generated entries may be overwritten during a later update. First check whether an entry is managed manually or by a subscription. Choose a management method that preserves personal notes and standalone test entries, and check that they remain after updating.
For multiple subscriptions, name them by source and purpose before organizing their order. Identical names don’t necessarily indicate duplicate servers; compare the address, port, protocol, and authentication details. Before deleting an entry, check whether it’s selected or referenced by a policy. After updating, confirm the selected server to avoid using the wrong one if the list has changed.
Subscription URLs may contain access credentials. Before sharing screenshots, exported files, or diagnostics, hide the full URL, passwords, and authentication details. If an import succeeds but no entries are available to select, check whether the response contains a supported subscription format and whether the source is accessible. Don’t repeatedly add the same subscription.
On Demand Connections
On Demand triggers connection behavior based on configured network conditions. It does not replace per-rule routing in Config.
In Settings, or the On Demand menu available in your version, review the available conditions first. Configure only the options actually shown, such as Wi-Fi, cellular, or a specified network. Start with one easy-to-observe condition, such as a single switch between Wi-Fi and cellular, and add more only after confirming the behavior.
Before enabling On Demand, establish a connection manually and confirm that the selected server and Config work. Otherwise, automatic triggers will simply repeat the same failure. After setting it up, leave the relevant screen, switch networks, and check the connection status. Then try a fresh request. An enabled On Demand switch does not prove that every trigger condition is working.
If the connection returns after you turn it off manually, check the trigger conditions
A connection that comes back after a network change may still be triggered by On Demand. To pause automatic behavior, check the relevant conditions rather than repeatedly using the connection switch on Home. After testing, note which conditions remain enabled so automatic reconnections aren’t mistaken for a problem later.
Networks that require web sign-in, such as hotel or public Wi-Fi, may need you to complete the sign-in first. If the connection repeatedly changes, check network authentication and signal stability before adjusting On Demand conditions. On Demand cannot restore an expired subscription, an incorrect password, or an unreachable server.
Traffic Statistics and How to Read Them
Data shows traffic recorded by the app. Check the screen for the actual measurement range and reset period.
In Data, first distinguish uploads, downloads, current speed, and total usage, then check any filters or time ranges available on the screen. Speed describes data transfer over a period of time; total usage describes the amount transferred during a measurement period. They are not interchangeable, and a single momentary reading is not enough to assess connection quality.
To track a specific action, note the current counters and time, perform that action alone, then return to Data and compare. If your version offers a reset option, decide whether you need to keep the history before resetting. Background sync, image loading, and system tasks can also use data, so minimize other activity during a test.
Local counters are not the same as server-side usage
App and server statistics may differ in time range, protocol overhead, and calculation method. Align the measurement criteria before comparing them. Don’t treat Data as the sole source for a subscription’s remaining allowance or as proof that a request matched PROXY. To check routing, consider Global Routing, the active configuration, and connection records together.
If traffic continues while the device is idle, check photo sync, system updates, ongoing audio or video, and background app activity before investigating further. Don’t assume On Demand or a rule is failing based only on the traffic graph.
DNS Settings and Domain Resolution
DNS translates domain names into addresses needed to connect. Successful resolution and an available proxy server are separate conditions that must be checked independently.
Check DNS options in the DNS section of Settings and in the active Config. Configurations may have their own DNS settings, so confirm which source is in effect before making changes. Keep working defaults when troubleshooting for the first time, and don’t enter multiple conflicting addresses at once.
Before changing DNS, record the original values, then use correctly formatted resolver addresses that are reachable on your current network. Encrypted DNS may also depend on the resolver’s own connection requirements and routing. Being able to save a configuration does not mean the resolver is reachable.
Separate DNS resolution failures from connection failures
“Server name could not be resolved,” “resolved but connection timed out,” and “certificate mismatch after connecting” happen at different stages. First use the DNS or diagnostic tools available in your version to check whether the domain resolves to a reasonable result, then test the server connection. A webpage loading or failing does not, by itself, reveal everything about DNS behavior.
After changing settings, make a fresh request and, if needed, reconnect the app to reduce interference from existing connections and cached data. Address rules and domain rules may match under different conditions; use actual connection records when troubleshooting. Don’t assume that one address returned for a domain is the permanent address for every service on that site.
Test Method, Today Widget and iCloud
These settings serve different purposes: Test Method affects test results, widgets provide quick access, and sync helps save and transfer configurations.
Test Method: Know what you’re testing
In Settings, find Test Method and check the available methods and their parameters. Then return to Home and run Connectivity Test. Different methods may only verify that a connection can be established or may also make a request to a specified destination. A successful test confirms only that the test conditions worked; it doesn’t guarantee access to every site or protocol.
When comparing servers, keep Test Method, the test destination, and the underlying network the same. Otherwise, you’re comparing results from different conditions. If Connectivity Test succeeds but a webpage fails, check the destination, matched rule, and DNS. If the test destination itself is unreachable, several servers may appear to fail at once.
Today Widget: Check the status after using a shortcut
If your system and app versions offer Today Widget, add it where the system allows and check its related option in Settings. It provides a shortcut or status information, not a separate server configuration. After using it, return to Home and check the selected server, Global Routing mode, and connection status.
The system may limit when and how widgets appear or refresh. If the widget is missing or its status hasn’t updated, check the system version, whether the widget was added, and the in-app setting. Don’t rely on widget text alone to determine whether a connection is established; check the in-app status and actual request results.
iCloud: Keep a recoverable copy before syncing
Before using iCloud sync, confirm that the expected Apple Account is signed in on your devices and that the relevant iCloud features are enabled. Review the sync options in Settings to understand what your version syncs, then check the result on another device. Sync does not copy every system permission, network state, or active connection from one device to another.
Before migrating, export any Config you need to keep and note your subscription sources separately. Editing the same configuration on two devices at once may cause conflicts or overwrites. Make changes on one device, wait for sync, and verify the result before continuing on the other. Store exports containing server details securely and remove authentication fields before sharing. For the migration steps, see Back Up and Restore a Configuration.
Diagnostics and Troubleshooting Steps
Diagnostics should identify where a failure occurs, not reset every setting.
In Settings, look for Diagnostics or the diagnostic tools available in your version, then choose one that fits the symptom. Note the network, selected server, Global Routing mode, and Config name before reproducing the issue once. If connection records are available, focus on the destination domain, matched policy, and failure stage rather than copying only the last error.
- Check the basic network. Confirm that Wi-Fi or cellular service works and whether you need to sign in to the network first.
- Verify the server details. Check Type, address, port, and authentication settings before repeatedly changing rules for incorrect details.
- Briefly compare Global Routing modes. Compare Proxy and Config for a specific test, then restore your usual mode.
- Check DNS and rules. Verify domain resolution, rule order, policy references, and FINAL separately to find configuration issues.
- Keep the test reproducible. Change one setting at a time and record the change and result. Revert changes that don’t help.
Logs and diagnostic exports may contain server addresses, visited domains, subscription links, and authentication details. Review and redact sensitive information before sending them to anyone helping with troubleshooting. Don’t post unredacted source data in public screenshots. Error types, the order of actions, and rule snippets with sensitive details removed are usually more useful for reproducing an issue.
If the issue occurs only after switching networks, check the On Demand trigger conditions. If only one site is affected, focus on its domains and policies. If all connections fail, start with the basic network, server, and authentication details. See Troubleshooting by Symptom for guided steps, or check the FAQ for quick answers.