Shadowrocket User Guide
Start with an existing subscription or server details, then import them, choose Global Routing, connect, verify access, and identify any issues. Allow about ten minutes for a first setup. If an error appears, check the relevant step rather than resetting everything.
Keep a copy of the original subscription or settings before you begin. Subscription links often contain credentials: do not share them publicly or post screenshots that show the full link.
01 · Add Server: Add a server or import a subscription
Open Shadowrocket and go to Home. First, identify the type of information you have. A subscription link usually returns multiple server entries; manual settings include a protocol, server address, port, and authentication fields. These are different input types: do not enter an entire subscription link as a server address or use a service account webpage as a subscription URL.
Import an existing subscription with Subscribe
On Home, tap the add button in the upper-right corner to open Add Server. Tap Type, choose Subscribe, and enter the complete subscription link from your service provider in URL. You can add a note to help identify it, such as “Personal subscription,” then tap the button in the upper-right corner to save. When copying the link, check for leading or trailing spaces, line breaks, or truncation. Query parameters are part of the URL; do not remove them to shorten what is displayed.
After saving, return to Home and wait for the subscription to load. Confirm that server entries appear under the subscription group; seeing only a name does not mean the import is complete. If the current interface offers a subscription update action, run it and check for errors. If the import fails, keep a record of the message and check that the link is still valid and that the response uses a subscription format the app can recognize. A regular webpage, sign-in page, or error page is not a valid server list.
Enter settings manually with Add Server
If you have settings for a single server, use the add button on Home to open Add Server, then choose the corresponding protocol in Type. Enter the address, port, and authentication details as provided. Different protocols may use different fields, such as a password or UUID. Match any TLS, Server Name, transport, or path settings to the original details. Do not fill in fields that the interface does not require based on guesswork, and do not substitute one protocol for another just because both accept an address and port.
After saving, return to Home, tap the server you want to use, and confirm that its selection indicator appears. For your first test, stick with one server rather than switching entries while changing settings. A server appearing in the list means its details were saved; it does not guarantee that the remote server is reachable or that the account is still valid. If you are unsure about a protocol field, read the quick reference, then ask your service provider to clarify the setting.
This step is complete when: A server entry appears on Home and one server is selected. Next, choose how traffic should be handled before turning on the connection.
02 · Global Routing: Choose how traffic is handled
Find and open Global Routing on Home. This setting determines the overall handling mode for the connection; it is not a subscription update button or a server selector. The three modes in this guide are Config / Proxy / Direct. Even after selecting a server, check this setting. Otherwise, turning on the connection may still produce results you did not expect.
Config: Route traffic using the current Config
To handle requests according to rules, choose Config, then open the Config page and confirm which configuration is selected. Rules in the configuration determine which requests use policies such as PROXY, DIRECT, or REJECT. Importing a subscription and configuring rules are separate tasks: successfully updating the server list does not mean that a rules file has been installed. Do not import an unfamiliar remote configuration just to make the page look complete. Check the purpose of an existing configuration before applying it.
To diagnose an issue in Config, consider the specific destination. For example, if a domain is routed DIRECT by the rules but you expect it to use the selected server, the issue may be with the rule or policy selection rather than server availability. When starting out, focus on identifying the current configuration and the policy expected for the destination; you do not need to rewrite all the rules. Read the user guide for more on rule order and policy references.
Proxy: Check the proxy path
Proxy can reduce variables introduced by rule-based routing and help check whether the current proxy path can complete a request. If a destination works under Proxy but not Config, check the current configuration's rules and policies first instead of immediately deleting the subscription. Proxy test results still depend on server status, service permissions, the destination website, and network conditions. Switching modes is not a fix for every issue.
Direct: Check your existing network
Direct sends requests directly and can help you compare whether your existing network can reach the same destination. If the connection status remains visible under Direct, that does not mean requests are passing through a proxy server. After comparing results, return to the mode you actually need. Note the current server and Global Routing combination to keep the next steps clear.
03 · Home: Connect and confirm system permissions
Return to Home, check the selected server and Global Routing mode once more, then turn on the connection switch at the top. When using the app for the first time, the system may ask to add a VPN configuration. Read the system prompt, confirm that the configuration is being added for Shadowrocket, and have the device owner authorize it using the device passcode or another authentication method provided by the system. Do not enter a server password or subscription credentials in the device unlock prompt.
After authorization, return to Shadowrocket and check whether the switch and connection status remain on. VPN status may appear in different places across systems, so use both the app status and the results of an actual access test rather than relying only on the status bar icon. System requirements and compatibility are as shown on the App Store page. If a menu item has moved from the location shown here, check its English label before continuing.
If the switch immediately turns off or an error appears, note the exact message first. Return to system settings and check for a pending VPN authorization or device restrictions imposed by an organization. If another VPN connection is active, disconnect it and test Shadowrocket on its own to avoid interference. On managed devices, follow the applicable management requirements; do not try to resolve the issue by removing management settings.
At this point, avoid enabling or changing On Demand at the same time. First establish a connection that you can repeat manually, then consider automatic connection settings. On Demand determines when to connect; Global Routing determines how requests are handled after connecting. They serve different purposes. Setting them up separately makes connection issues easier to diagnose.
This step is complete when: After system authorization, the connection status on Home remains active without recurring errors. This only confirms that the connection process has started; verify that the server can handle requests and that the rules behave as expected in the next step.
04 · Connectivity Test: Verify the connection and access
First, run Connectivity Test on Home and check whether the selected server returns a result. If the test fails, you can run it once more to rule out a temporary interruption, but avoid rapidly switching through every setting. The reported time reflects the test destination and method at that moment. It is not the same as webpage load time or file transfer speed, and it does not prove that all apps are following the rules.
Next, open a browser and visit the specific destination you need to use, then complete an actual action, such as opening a page and navigating to an inner page. Seeing a previously cached home page is not enough to confirm that the connection works. Refresh the page or repeat the test in a new browser tab. If the browser works but another app does not, check that app's destination domain, account status, and error message separately; do not assume the entire connection has failed.
Compare modes using the same destination
If the result is unclear, keep the server unchanged and compare the same destination under Direct, Proxy, and Config, in that order. Start a new request after each switch. If needed, close the old page before reopening it to avoid reusing an existing connection. If the destination already works under Direct, a successful page load alone does not prove that the proxy path is active. If Proxy works but Config does not, check the current configuration.
In the request records provided by the app, find the request you just made and check the policy used and the rule it matched. If you see DIRECT, check whether that is what the configuration requires. If you see REJECT, look for a rule that actively blocks the destination. If you see PROXY but the request still fails, check the selected server, the remote response, and the destination's status. Records show what happened; not every DIRECT result is an error.
Changes in traffic shown in Data can provide additional context, but increased traffic may come from background requests and is not, by itself, evidence that a specific destination is accessible. A complete verification should confirm all three points: the connection stays active, the request to the destination completes, and the handling policy matches your expectations. Once these are confirmed, restore the Config you need for daily use and keep the working settings as a reference for future troubleshooting.
05 · Common issues: Check each stage
Start by identifying the step where the process stops, then adjust the relevant setting. Change one condition at a time and retest the same destination. Reinstalling right away may erase information that has not been backed up and useful evidence from the issue. Usually, record the error and check the settings and current configuration before deciding whether to import again.
The subscription is saved, but no servers appear
Return to the subscription entry and check that the URL is complete, that you copied the subscription address rather than an account webpage, and that the link has not expired or been reset by the service. After updating, identify whether the error occurred before the content was downloaded or while it was being parsed. For the former, check the current network and whether the link is reachable. For the latter, check the subscription format. If you need help from your service provider, share the error text and the stage where it occurred, but do not disclose the full URL.
The server is listed, but the test times out
Turn off the connection first and confirm that the device can access the internet over its existing Wi-Fi or cellular network. If the network requires a webpage sign-in, complete that first. Then check the address, port, protocol, authentication, and TLS-related fields for missing or incorrect entries. If your existing subscription has another known working entry, test it without changing the rules to distinguish an individual server issue from a local network issue. A timeout alone does not identify which setting is wrong.
Proxy works, but Config does not behave as expected
Check which file is actually selected on the Config page; do not rely only on whether a file with a particular name appears in the list. Then use the request record to check the matched rule and policy, and see whether an earlier rule matched the destination first. Back up the configuration before editing it. If you are unsure, do not replace all DNS, rule, and policy settings at once. Read the user guide by section for details on DOMAIN-SUFFIX, IP-CIDR, and FINAL.
Some destinations fail after connecting, or the connection drops when the network changes
Note whether the issue occurs on Wi-Fi, cellular, or both. After each network switch, reconnect and make a new request to the destination. If only some destinations fail, check the destination's status, rule handling, and any DNS-related errors separately. Do not change all DNS settings based on a single timeout. If you use On Demand, switch back to a manual connection test first. Restore connection conditions one at a time after confirming the basic path works.
If you still cannot identify the issue, gather four details: the selected server type, the Global Routing mode, the failed destination and exact error message, and the individual comparisons you have already made. Hide subscription URLs, passwords, UUIDs, and private server addresses before sharing. See the FAQ for more on permissions, accounts, and connection issues, or the quick reference for interface terms.
After confirming the connection: Keep a working configuration
After completing the first verification, note the selected Config and server, and back up the configuration using your usual method. Before updating a subscription, changing rules, or adjusting On Demand, save the existing settings and test each change separately. A subscription update may change the server list, so confirm the selected server again afterward rather than assuming a similar name means it is the same connection.
This guide covered a manual connection you can verify. To continue configuring Shadowrocket, read the Shadowrocket user guide sections on Config, On Demand, Data, and routine maintenance as needed.