For your first Shadowrocket setup, get the app, import a subscription or node details you already have, select a node, connect, then check Global Routing and your configuration rules. This guide is for first-time users. Screen paths focus on iPhone and iPad; Mac, Windows, Android, and Linux users can follow the same concepts, though controls may be in different places. By the end, you’ll know the difference between a subscription, a node, and Config, how to verify a connection, and how to troubleshoot update and access issues.
1. What do you need before installing, and does the price include a service?
Shadowrocket is a closed-source commercial app that handles device connections and routes them according to your settings. Getting the app and obtaining a remote server service are separate: installing the app does not provide a working server. The steps below assume you already have your own service, subscription, or node details. This site does not provide, sell, or recommend nodes or subscriptions.
- iPhone / iPad: Buy Shadowrocket on the App Store for a one-time payment of $2.99. Check that the developer is Shadow Launch Technology Limited and the app ID is
932747118. See the App Store listing for system requirements. - Mac / Windows / Android / Linux: The app is free on these platforms. Mac versions are available for Apple silicon and Intel. See the download guide for all platforms.
- Connection details: Have your existing subscription URL or the server address, port, protocol, and authentication details. Buying the app does not include a service plan; check the validity period and device limits of your existing service separately.
Don’t share a subscription URL as if it were an ordinary web address. A token in the URL may grant access to subscription details. When asking for help, hide the full link, password, UUID, and private key.
2. Where do Home, Config, and Settings fit in?
Start by distinguishing these three areas so you don’t confuse updating nodes with updating rules. Home is for connections and node selection, Config is for routing configurations, and Settings contains app preferences. After importing nodes, check which one is selected. After adding a Config, make sure it’s the active one.
| Screen | What it’s for | What to check the first time |
|---|---|---|
| Home | View nodes, subscription groups, the connection toggle, and Global Routing | Are any nodes listed, and is the intended node selected? |
| Config | Select, view, and edit routing configurations | Does the active configuration and its rules match what you expect? |
| Settings | Adjust testing, subscription, On Demand, and other settings | Keep the defaults at first; change settings one at a time after connecting successfully |
A node determines which server to connect to; Config determines which policy handles each connection. Selecting a node alone doesn’t mean all traffic will use it. The result also depends on Global Routing and the policies in your configuration.
3. How do you import an existing subscription link?
A subscription URL returns a refreshable list of nodes; it isn’t a set of server details to enter by hand. The example https://example.com/sub?token=xxxx is shown only to illustrate the format. It won’t connect, so don’t use it in the app as a real subscription test.
-
Copy the link
Copy the full subscription URL from your service’s management page. Keep the query parameters, and remove any spaces, line breaks, or extra text before or after the link.
-
Choose the type
Go to Home → “+” in the top-right corner → Type, then choose Subscribe. Don’t enter a subscription URL in a single node’s server address field.
-
Enter details and save
Paste your subscription link into URL, add a recognizable label, and save. Return to Home and check that the subscription group and nodes appear.
-
Refresh and select a node
Pull down on Home to refresh the subscription. Wait for it to finish, then select a node. If the list is empty, check the update error first; don’t add the same link repeatedly.
Seeing node names after import only confirms that the app retrieved node details; it doesn’t mean the servers are reachable. Continue by connecting and testing a webpage. If an update fails, don’t immediately delete the old group—you could lose both usable entries and clues to the problem.
4. How do you add a node manually when you only have its details?
Go to Home → “+” → Type. Choose the protocol specified in your details, then fill in the corresponding fields. Shadowsocks, VMess, VLESS, Trojan, Hysteria2, and WireGuard use different parameter formats. Changing Type while keeping authentication fields from another protocol won’t work.
- Address and port: The server address field usually takes a domain name or IP address, without a webpage path. Use the port in your existing details. For example, enter
443only if the details specify443; don’t assume that an HTTPS webpage means you should use that port. - Authentication: Check the password, UUID, encryption method, or key required by the protocol. Incorrect capitalization, extra spaces, or missing characters can cause authentication to fail.
- Transport and TLS: If your details specify a transport method, Host, path, or SNI, check each one. The server address and the name used for TLS may be different.
- Save and test: Return to Home, select the node, and connect. If you only have a subscription URL, use Subscribe instead of guessing the node protocol from how the URL looks.
5. How do you connect, and does the VPN icon mean it’s working?
Select a node on Home, then turn on the connection toggle at the top. The first time you connect on iPhone or iPad, iOS will ask for permission to add a VPN configuration. Confirm the request was initiated by Shadowrocket, then follow the system prompt. The VPN icon means the system tunnel is up; it doesn’t confirm that the remote node authenticated, DNS resolved, or the destination website loaded successfully.
- Confirm the intended node is selected and note the current value under Home → Global Routing.
- Turn on the connection toggle and wait for the status to settle. If an error appears, keep a record of its message.
- Open a browser and visit a familiar HTTPS page, then test the destination you actually need to reach.
- Check the connection log in the app to tell whether no request came in, a rule chose the wrong route, or the remote connection failed.
After changing one setting, test again. Don’t change the node, DNS, and rules all at once. If the same site won’t load with the connection off, check your local network or the site itself before blaming Shadowrocket.
6. Which Global Routing mode should you use: Config, Proxy, or Direct?
Choose how connections are handled under Home → Global Routing. If you have a working routing configuration, use Config for everyday use. For troubleshooting, compare Proxy and Direct briefly. “All” below means connections routed through the Shadowrocket tunnel and handled by the app—not every type of system traffic on the device.
Config
RecommendedMatches connections against the active Config in rule order and applies the policy specified by the matching rule. Connections that don’t match are usually handled by FINAL; don’t assume they’ll go direct.
Best for: everyday routing with rules you’ve checked
Proxy
Sends connections through the currently selected proxy. Use it to test whether a node can reach a destination without relying on regular routing rules. It can’t fix a server outage or incorrect authentication.
Best for: briefly testing the proxy route and comparing it with your rules
Direct
Handles connections directly, without using a remote proxy node. Turning on the tunnel while using Direct doesn’t make requests exit through a remote server.
Best for: checking whether your local network can reach a destination
Scene
Applies the handling mode associated with a preset scenario. Check the scenario conditions and linked settings before use; it isn’t a universal switch that automatically determines how every destination should be handled.
Best for: users with clearly defined network scenarios configured
If the same node reaches a destination in Proxy but fails in Config, check the matched rule, its policy, and any DNS differences first. This points to the configuration as something to investigate, but one test can’t rule out all network fluctuations.
7. What’s the difference between updating a subscription and updating Config?
Refreshing a subscription on Home updates node details, such as addresses, ports, or the node list. Updating a remote configuration in Config refreshes its contents. These updates are independent: a refreshed node list doesn’t mean the rules are current, and updating Config doesn’t extend the validity of your existing service.
- Update nodes: Return to Home and pull down to refresh. Check the subscription group’s update result, then confirm that your previously selected node is still there.
- Update routing rules: Go to Config and find the remote configuration you’re using. Use its action menu to update it; the action name and location may vary with the current interface.
- Local configurations: A locally edited configuration has no remote content to fetch, so you’ll need to maintain it yourself. Back up local changes before updating a remote configuration to avoid overwriting your edits.
When reviewing rules in Config, pay attention to their order and target policies. The snippet below illustrates the syntax; it isn’t a complete configuration file you can use as a replacement. PROXY must resolve to a valid policy in your actual configuration.
[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY
DOMAIN-SUFFIX matches domain suffixes; IP-CIDR matches IP ranges. In this example, no-resolve means the IP rule won’t trigger a DNS lookup. GEOIP matches against an IP geolocation database, while FINAL handles connections that haven’t matched another rule. Domain rules rely on available domain information; IP and GEOIP matches can also be affected by DNS results. Rules are generally processed in order, so a broad rule near the top can shadow more specific rules below it.
8. Do you need On Demand when switching between Wi-Fi and Cellular?
On Demand starts connections when specified conditions are met; it doesn’t make nodes faster or replace Global Routing. First connect manually and confirm that it works. Then go to Settings → On Demand to configure automatic connection behavior. This avoids adding variables before the connection is working properly.
Check the setup: test both networks
On Wi-Fi
- Complete any network sign-in that requires browser confirmation first.
- Manually connect to the same node and test the same destination.
- Check the Wi-Fi conditions and exclusions under Settings → On Demand.
On Cellular
- Turn off Wi-Fi and confirm that mobile data is connected.
- Keep the same node and Global Routing mode, then test again.
- Check the Cellular conditions under On Demand and see whether they trigger as expected.
Verify a manual connection before adding On Demand conditions. Change one condition at a time so you can tell what triggered an automatic reconnect.
If the connection turns back on after you switch it off, check On Demand before removing the system VPN configuration. To stop On Demand connections completely, disable the relevant conditions first, then turn off the connection toggle and check the system status.
9. Subscription times out, or latency looks fine but pages won’t load—what should you check?
A latency test, a successfully established tunnel, and a webpage loading are three different outcomes. A latency test may cover only one stage of a connection; it doesn’t confirm that DNS, TLS, the remote exit, or the destination site is working. Choose checks based on what you’re seeing instead of enabling every advanced option.
What if a subscription update keeps timing out?
First check that the URL saved on Home is complete, then confirm that your local network can reach the subscription address. If you have a working node and the subscription address requires a proxy, connect first, then go to Settings → Subscribe and check Update via Proxy before trying again. If you don’t have a working node, enabling this option won’t establish a proxy connection.
A node has latency, but webpages won’t load. Why?
Temporarily choose Proxy under Home → Global Routing and try the same page. If it still fails, compare with another node you already have. If only domain names fail, check the active Config’s DNS settings and any resolution errors. Latency alone doesn’t prove the proxy is usable.
Why won’t just one website load?
Keep the node unchanged, compare Config with Proxy, and check which rule and policy match the domain. If both modes fail while other sites work, consider whether the destination site is down, restricts accounts by region, or blocks the current exit.
Does switching to Cellular fix it?
Keep the node, destination, and routing mode the same, then test again on Wi-Fi. If the difference is repeatable, check Wi-Fi sign-in, local DNS, and network restrictions first. Record the difference before making changes; don’t change the protocol and port at the same time.
When asking for help, include the network, routing mode, destination, and error instead of just saying “it doesn’t work.” Redact server addresses, subscription URLs, and authentication details in logs. The original timeout, DNS resolution, or TLS error message is usually enough; there’s no need to share the full configuration.
10. How can you tell setup is complete, and what needs to be done on a new device?
A successful first setup isn’t measured by how many nodes appear in the list. You should be able to explain how a request is handled: whether the connection is on, which node is selected, the Global Routing mode, and which policy matched in Config. On a new device, check the app configuration and your service’s device limits separately; don’t assume all settings sync automatically.
- Record a baseline: Note a working node, the active Config, and the Global Routing mode. Keep one reproducible working setup before trying other features.
- Test routing: With Config selected, visit two destinations that should take different routes. Use the connection log to confirm the policies rather than judging only by whether the pages load.
- Test updates: Manually refresh an existing subscription and confirm that its nodes are still selectable. Check remote Config updates separately.
- Protect your details: Back up configurations you want to keep and store subscription URLs securely. Exported files may contain sensitive details; don’t upload them to public comment areas.
- Retest after moving: Get the app for the new device’s platform, import your existing details again, and test the connection. If your service limits the number of devices that can be online at once, follow its terms.