Step 1: Add Server and import a subscription
Open Shadowrocket and go to Home. First, identify which type of information you have: a subscription link that returns a server list, or details for a single server, including its address, port, protocol, and authentication parameters. These require different input methods. Do not enter a subscription link in the server address field or use the share details for a single server as a Subscribe URL. You can leave the connection switch off while you check the parameters to avoid changing the device's network before setup is complete.
For an existing subscription link: choose Subscribe
From Home, tap the plus button in the upper-right corner to open Add Server. Open Type, choose Subscribe, then return to the form and paste your complete subscription link into URL. Add a recognizable remark and save. Query parameters in the link may be needed to identify the subscription, so do not delete anything after the question mark. Check both ends of the link when copying to make sure it does not include chat notes, line breaks, or spaces.
After saving and updating the subscription, return to Home and check the server list. The expected result is a subscription group with server entries, not just a name. Tap one of the servers to select it. If you see a group but no servers, first check whether the subscription update reported a failure. Repeatedly toggling the connection switch will not populate the list; resolve the subscription loading issue first.
Subscription links are sensitive information. Do not share a complete link publicly or send a screenshot containing it to unrelated people. When the subscription contents change, update the corresponding subscription. Manually edited entries created from a subscription may be overwritten during the next update, so do not treat a temporary change as a permanent saved configuration.
For a single server: choose the matching protocol
If you have parameters for a single server, use the plus button on Home to open Add Server, but choose the protocol specified in your information under Type, such as Shadowsocks, VMess, VLESS, or Trojan. Enter the address, port, and authentication fields as provided. If TLS, a transport type, or other additional parameters are required, enter each one in the matching field. Do not infer the protocol from the port number alone or substitute authentication fields from another protocol.
If you have a QR code, use Scan QR Code to read the existing server details. After importing, open the entry and check that the protocol, address, and port are complete. Scanning a QR code does not guarantee that the server can connect. Save, return to Home, and select the entry you just added. At this point, you should be able to identify the selected server before moving on to choose which requests use it.
A subscription and individual entries can coexist, but for an initial setup, use one confirmed set of valid details to complete verification. Do not import a large number of entries at once and then switch between them at random to diagnose the result. For more about subscription updates, duplicate groups, and parameter fields, see Questions & Answers.
Step 2: Choose Global Routing
The server entry determines which connection path is available; Global Routing determines how requests choose a path. Tap Global Routing on Home and check the current mode. This guide uses Config, Proxy, and Direct, matching the interface labels. After switching modes, return to Home and confirm that the selected mode is displayed. This helps avoid relying on a remembered setting that does not match the current state.
Config: follow the active configuration's rules
Config is useful for directing requests according to rules. Before using it, open Config and confirm that the selected configuration is the one you intend to use, rather than merely confirming that a file with the expected name exists in the list. A server subscription and a rules configuration are separate: importing a server list does not mean that complete rules have been imported, nor does it mean that all websites will automatically use the selected server.
Rules are usually matched in order, and an earlier match can affect how later rules are handled. PROXY, DIRECT, and REJECT are different actions; do not judge a rule only by whether it contains a particular domain. When starting out, keep a configuration whose purpose you understand, and make changes only after confirming that access works. If you are not sure what the rules in Config do, do not try to fix the connection by stacking multiple configurations.
Proxy: test the selected server connection
Proxy can temporarily reduce differences between rules, helping you check whether the selected server can complete an actual request. Use it to isolate a problem; it does not have to be the mode you use long term. If a target page opens in Proxy but fails in Config, check the active configuration and its rules first instead of immediately re-entering the server password. After testing, switch to the mode you intend to use.
Direct: check the device's underlying network
Direct checks network behavior without going through the proxy server. Selecting it does not test whether the server is available; even with the app's switch on, requests may be handled as direct connections. If you are testing the proxy connection, do not leave the mode on Direct and draw a conclusion based only on the switch color.
For an initial check, test the underlying network first, use Proxy to test the server, then return to Config to check the rules. This sequence separates the issue into three layers and changes only one condition at a time. Read the troubleshooting guide for details about rule order, FINAL, and DNS after the basic connection works. There is no need to adjust each setting before your first connection.
Step 3: Turn on the switch and authorize the connection
Return to Home and confirm in order that a server entry is selected, Global Routing matches your test, and there are no subscription errors waiting to be addressed. Then turn on the connection switch at the top of Home. On the first connection, the system may prompt you to add a VPN configuration. Review the prompt, confirm that it was triggered by your current action, tap Allow, and complete the device verification required by the system.
System authorization allows the app to establish a network connection configuration; it is not where you enter subscription account details. Do not enter your server password as device unlock verification, and do not repeatedly delete and reinstall the app because a system prompt appeared. After authorization, return to Shadowrocket and wait for the connection status to stabilize. If you cancel the system prompt, the app may return to a disconnected state. Start the connection again and complete authorization to continue.
An enabled switch only indicates that the connection process has reached a particular state; it does not mean every destination is accessible. A VPN indicator in the status bar does not replace testing in a browser, and its position may vary with the device layout. In the next step, check both the server test and actual requests rather than treating a single indicator as proof that setup is complete.
If the switch turns off immediately after you enable it, first confirm that system authorization was completed. Then check for another active VPN configuration or device management restrictions. Temporarily stop other connections and test again to avoid multiple configurations attempting to control the network. If a managed device restricts adding VPN configurations, follow the device management requirements instead of repeatedly retrying.
Before your first manual connection is verified, do not adjust On Demand at the same time. Automatic connection conditions add more variables to observe; for example, an automatic reconnection after disconnecting can look like a faulty switch. First verify a manual connection and disconnection, then set up On Demand if needed. The steps are the same on iPad. Landscape orientation and split view affect only how the page is displayed, not the order: confirm the entry, choose a mode, then connect.
Step 4: Verify the connection and routing results
After connecting, run Connectivity Test on Home and check whether the selected server returns a result. The test provides a clue about reachability; it is not a guarantee of connection quality. A failed test may be related to the test destination or server settings, and a response does not prove that every website works. Continue by opening a browser and visiting a page you actually need to use, then check whether new content loads.
Check the underlying network first, then the server
If the result is unclear, disconnect the app and visit a page that normally opens over a direct connection. If the underlying network is unavailable, resolve Wi-Fi sign-in, cellular connectivity, or the router connection before returning to the app. If the underlying network works, select the original server again, connect using Proxy, and revisit the target page. Keep the network environment unchanged while testing; do not switch Wi-Fi, server, and mode at the same time.
A page already open in the browser may come from the cache, and existing app connections may continue using the path selected before the change. Reload the page when testing again, or close and reopen it if needed, to make sure a new request is sent. Do not assume the new configuration is active just because a page remains on screen, or that every connection has failed just because one app briefly shows a loading indicator.
Return to Config to verify routing
After confirming access in Proxy, switch to Config and test the same target with the same server. If it fails only in Config, open Config and check the selected configuration and rule order. Where connection records are available, check the matching action and actual route for the target domain. Confirm whether the request used PROXY or DIRECT as expected instead of checking only whether the rule text contains the target name.
If only one domain fails, distinguish between domain resolution, the rule action, and the remote connection. For an initial check, note the domain, current mode, and symptoms rather than immediately rewriting all DNS settings. Server reachability, domain resolution, and the target service's availability are separate conditions; verifying one does not replace checking the others. See DNS troubleshooting for more detailed checks.
Finish with one final check: keep the server and mode you plan to use, disconnect and reconnect, and confirm that the result is repeatable. Record the working combination as a baseline for comparison when you next update a subscription or change Config. Do not include a complete subscription link, password, or other authentication information in your notes.
Step 5: Check common failures based on symptoms
When something fails, first identify where it stopped: information did not import, the server test failed, the switch will not stay on, or a specific page fails after connecting. Change one item per test, check the same destination again, and keep the original error message. Clearing all settings removes useful comparison data and can make it harder to tell whether the problem is with the subscription, rules, or device network.
Subscribe update failed or the list is empty
Return to the subscription edit screen and check that the URL is complete. Make sure you have not used a webpage address, copied an expired link, or omitted authentication parameters. Then confirm that the device is online. The returned subscription content must also be in a format the app can recognize; a webpage description or error page cannot be imported as a server list. For link expiration, access permissions, or an unexpected server response, check with the service provider you already use. Do not post your personal subscription link publicly when asking for help.
Connectivity Test timed out
First check basic access on the current network, then verify the server address, port, protocol, and authentication parameters. For a manually added entry, compare each field with the original details, paying particular attention to TLS and transport parameters. You can compare it with another existing entry in the same subscription, but do not change the network and configuration at the same time for each test. If only the test times out while the actual page is accessible, check the test destination instead of deleting the server based on a single test.
The switch is on, but pages will not load
First check whether Global Routing is set to Direct, then confirm that the expected server entry is selected. If Proxy works but Config does not, check the rules and active Config first. If both modes fail, continue checking the server connection and network. If only some domains fail, check DNS and the records for the target requests. Do not change every setting at the outset, and do not treat a successful subscription import as proof that the server is available.
Issues after changing networks or returning to the foreground
After switching from Wi-Fi to cellular, confirm that the new network can access the internet on its own, then disconnect and reconnect. If behavior changes after the device wakes from sleep, check whether an On Demand condition triggered another connection and whether the same server is still selected. On iPad, you can place the browser and app side by side in split view, but record the order of each change to avoid mistaking a cached page for a new connection result.
If you still cannot identify the cause, note the device type, system version, current network, Global Routing mode, whether all servers fail, and the error message with sensitive details removed. Do not share a complete subscription, password, or QR code. For conceptual questions, see Questions & Answers. To check symptoms such as the switch, subscriptions, timeouts, DNS, or battery use step by step, consult the troubleshooting guide. This guide covers the process through one stable, reproducible connection; adjust rules and automatic connection conditions afterward, one at a time.