This article explains how to use Shadowrocket and why connections can become unstable when a team shares nodes. You’ll learn how to install the app on an iPhone or iPad, import a subscription, assign usage rules, and configure account environments correctly to reduce disconnections, security checks, and connection failures.
1. Check the basics before setting up team access
Shadowrocket is a popular proxy client for iOS and supports common protocols such as SS, VMess, VLESS, and Trojan. For team use, the key isn’t simply having everyone import the subscription at once—it’s ensuring that the subscription source, node assignments, and system proxy rules are consistent. This site also collects free nodes for testing, but their stability depends on how many people are using them, so we recommend using them only for temporary testing.
- Have each team member install the app using their own Apple ID environment, and avoid switching accounts frequently.
- Use the same subscription link or a node file prepared by the administrator.
- Avoid having too many people sign in to business platforms at the same time using the same account and node.
- Make sure the phone’s time and region settings are correct and that network permissions are enabled, to prevent certificate or DNS issues.
2. How to import a subscription into Shadowrocket
- Open Shadowrocket and tap “+” in the top-right corner.
- Select “Subscribe” or “订阅” as the type, then paste in the subscription link provided by your team.
- Enter a label, such as “Office Subscription” or “Test Nodes.”
- Tap Done, return to the home screen, and pull down to refresh. Wait for the node list to appear.
- Choose a node with low latency in the region you need, then turn on the connection switch at the top.
- The first time you connect, you’ll be prompted to add a VPN configuration. Tap Allow and enter your device passcode.
If you have a link for a single node, you can also copy it and open Shadowrocket; the app will usually recognize it and prompt you to import it. For teams, we recommend using a subscription link so the administrator can update the nodes and members can simply refresh the list.
3. How team usage affects account environment stability
Many people assume that connection failures are always caused by the nodes, but in team settings, a more common problem is an inconsistent account environment. For example, if the same business account signs in from Hong Kong and then from the United States just a few minutes later, the platform may flag the activity as unusual. Frequently switching between nodes in different countries on the same device may also trigger security checks.
Assign fixed routes based on purpose: use one region for research, a fixed region for social media management, and separate nodes for testing. Aim to keep each account on a relatively consistent network environment, and avoid having multiple people use the same business account at once. You can rename nodes in Shadowrocket—for example, “Japan – Research” or “US – Testing”—to avoid selecting the wrong one.
4. Troubleshoot connection failures in this order
- Refresh the subscription first and check that the nodes haven’t expired and the format is correct.
- Switch networks and test both Wi-Fi and cellular data.
- Try two or three different nodes instead of repeatedly reconnecting to just one.
- Check whether Shadowrocket is set to “Global Routing” or rule-based mode. If the rules seem to be causing problems, temporarily switch to global mode for testing.
- Turn off other VPNs, accelerators, or security apps on your device to avoid conflicts.
If none of the nodes can connect, the subscription may be unavailable, the network may be restricted, or the client configuration may be corrupted. Try deleting the old subscription and importing it again. If only one platform won’t open, check the routing rules and DNS first rather than immediately replacing all the nodes.
5. Recommended team practices
Administrators should update the subscription regularly, while members only need to refresh it. Keep important accounts on nodes in a fixed region; don’t use free test nodes for critical business activities. If a problem occurs, record the time, node name, and network type before reporting it to the team. These habits can reduce communication overhead and improve both account environment stability and connection availability when using Shadowrocket.