Official Manual · First Connection

Shadowrocket Setup Guide

First add your existing connection details to Home, then choose whether requests are handled by rules, sent through a proxy, or accessed directly. After turning on the switch, check the result with a server test and an actual page visit. Do not treat the switch state alone as proof of connectivity.

Before you start: Make sure Shadowrocket is installed and that you already have your own subscription link or server details. The iPhone / iPad version is available from the App Store product page for a one-time payment of $2.99; check the App Store page for system requirements. Mac / Windows / Android / Linux versions are free and can be installed from the download page. This guide uses the iPhone / iPad interface.

A one-time client purchase is separate from a service plan. This site does not provide, sell, or recommend proxy servers or subscriptions. Subscription links may contain access credentials; enter them only in the client and do not post the full link publicly or include it in troubleshooting records.

01 / Import

Add Server or Subscribe: Import existing connection details

Open Shadowrocket, tap Home at the bottom, then tap the plus sign in the upper-right corner to open Add Server. If you have a single set of server parameters, add it as an individual server. If you have a subscription link that syncs a server list, use Subscribe. Choose one method; there is no need to import the same connection details both ways.

Enter a single server in Add Server

First select the protocol that matches your existing parameters, then enter the server address, port, and authentication details required by that protocol. The fields vary by protocol, so do not reuse authentication details from one protocol for another. If the parameters specify transport or TLS settings, match them to the supplied details as well. When entering the address and port separately, do not include the colon between them in the address field. Before saving, check that copying did not add spaces, line breaks, or quotation marks.

After saving, return to Home and find the new entry in the SERVER list. If there are older entries with similar names, inspect them first and confirm that the address and protocol match the one you just added. Then select the correct entry. Seeing an entry means its details have been saved; it does not verify that the remote server is reachable.

Import an existing subscription in Subscribe

In the type options under Add Server, choose Subscribe, paste the full subscription link into the link field, and save. Preserve any query parameters in the link as provided; do not copy only the domain or enter the link as a server address in an individual entry. Return to Home and wait for retrieval to finish. Check that selectable server entries appear under the subscription instead of only checking whether a subscription name was added. If the same subscription is already present, update the existing entry rather than creating another with the same name.

Whichever method you use, select a server in Home for testing before continuing. Keep that selection while changing Global Routing or checking access, so you can tell whether a changed result is due to the mode or the server itself.

02 / Routing

Global Routing: Choose how traffic is handled

Tap Global Routing in Home and choose a mode based on what you want to test. This setting determines how requests are routed; it does not change the server details you just saved. For an initial proxy-path test, temporarily use Proxy to reduce rule-related variables. For everyday routing based on individual request policies, use Config. Direct can serve as a comparison, but it does not demonstrate that the proxy server works.

Config
Handle requests according to the active configuration's rules. First open Config at the bottom and confirm that the configuration you intend to use is active; seeing a file in the list is not enough. When testing a domain, check from the beginning of the rules for a condition that may match first. If none applies, check the default policy specified by FINAL.
Proxy
Route requests handled by the client through the proxy instead of applying the active configuration's rules individually. This is useful for checking whether the selected server can handle actual access. After a successful test, if you switch back to Config, test a representative page again because the request path may differ between modes.
Direct
Send requests directly to their destination without using the selected proxy server. If a page will not load, use this mode to check basic access over the current Wi-Fi or cellular network. A successful direct connection shows that this request has a direct route; it does not show that routing rules are correct.

After choosing a mode, return to Home and check the current value under Global Routing. Note that Config at the bottom is where configuration files are managed, while Config under Global Routing is the mode that enables rule-based handling. Opening the configuration list alone does not change how traffic is handled.

03 / Connect

Home: Turn on the connection

In Home, check the selected server and Global Routing, then turn on the connection switch. The first time you enable it, the system may ask to add a VPN configuration. This allows Shadowrocket to handle device traffic according to the selected mode. Confirm that the request was triggered by the action you just took, tap “Allow” in the system prompt, and complete device authentication as instructed. If authorization was already granted, the prompt may not appear again.

When setup is complete, return to Home and check whether the switch stays on after a short wait. If it immediately switches off, do not keep tapping it or delete the subscription right away. Check for a dismissed system prompt or another VPN connection running on the device. If the device is managed by an organization or school, confirm that network configuration changes are allowed; do not remove the management profile yourself. If the switch still turns off, go to Common failure points to check authorization and connection status.

A switch that stays on means the system connection is established, but it does not mean the server is responding, every website is reachable, or every rule is matching the intended policy. Keep the network, server, and mode unchanged for the next verification step. If On Demand is enabled, note whether it automatically reconnects when the network changes, so results from different conditions are not mistaken for a single test.

04 / Verification

Connectivity Test: Check the server and actual access

First, find Connectivity Test in Home and run it. Wait for the result to refresh, then check whether the selected server returned a result. The response time describes the conditions at the time of testing; it is not the same as real-world browsing speed. A single timeout is not enough to conclude that a server is permanently unavailable. Note whether it responded or timed out; there is no need to share the server address, authentication fields, or subscription link.

Next, open a browser and reload a page that you previously confirmed was accessible. Do not rely on a tab that was already open; it may still show content loaded before the connection. Use the same network and address before and after testing whenever possible. If the page reloads successfully in Proxy mode, actual access worked for this test. If Connectivity Test responds but the page fails to load, check the destination site, domain resolution, or current request path separately rather than treating the two results as contradictory.

To verify routing in Config mode, first choose a domain expected to use DIRECT according to the configuration, then choose one expected to use a proxy policy, and reload each. If client diagnostics are available, check the policy used for each domain and request time. A page opening does not by itself prove that a specific rule matched. A webpage may also request other domains, so check individual requests rather than only the main domain in the address bar.

Completion criteria: The connection switch stays on, the selected server responds under the test conditions, and an actual page reloads. To verify routing, also confirm that representative requests use the expected policies. After comparing results, switch Global Routing back to the mode you need for everyday use and visit the test page once more.

05 / Troubleshooting

Common failure points: Start with the first step that fails

First identify where the problem occurs: no entry in the list, the switch will not stay on, Connectivity Test times out, or only certain pages fail to load. Start at the earliest failure and do not change the network, server, and configuration all at once. After each change, repeat the same test. Otherwise, even if access is restored, it will be difficult to tell which change helped.

Subscription saved, but no selectable servers appear

Return to Home and check whether the subscription has been retrieved and expanded. Update the existing subscription once. If no entries appear, check whether the device currently has internet access, whether the link was copied in full or has expired, and whether its contents are intended for Subscribe. If you cannot find a single server after saving it, return to Add Server and check the required fields instead of pasting the same parameters into Subscribe. Once a selectable entry appears in the SERVER list, continue to How traffic is handled.

The switch turns off, or the expected authorization prompt does not appear

First check whether the system prompt was dismissed or another VPN is already connected. On the device, check VPN status under “Settings → General → VPN & Device Management”; the system menu may vary slightly by version, and you can also search for VPN in Settings. After confirming there is no conflict, return to Shadowrocket and try enabling it again. If the device is managed and settings cannot be changed, ask the device administrator about the restriction rather than clearing client data to address a system-side issue.

The switch turns on, but the server test always times out

Turn off the connection and check that the device can access common pages over the current network. If basic access fails—for example, if you have not completed sign-in on public Wi-Fi—restore network access before testing again. If the network is working, check the server protocol, address, port, and related settings. If another usable entry is available, test it on the same network while leaving the other settings unchanged. This can narrow down the issue, but a single comparison does not prove a server-side failure.

Proxy test succeeds, but some pages fail in Config mode

On the same network, test the same pages in Proxy and Config. If the failure occurs only in Config, first check which configuration is active, then see whether an earlier rule matches the failing domain. If no rule matches, check FINAL. A page may load images or send login requests from separate domains. If the main content appears but some elements fail, check those requests separately rather than changing the entire configuration based only on the main domain's policy.

Troubleshooting notes only need to include the step where the problem occurred, the current mode, whether you used Wi-Fi or cellular, and whether the issue is reproducible. For questions about system versions, store availability, or restoring on a new device, see the Getting the App guide; reimporting a subscription is not necessary to resolve a purchase or installation issue.