This article explains how team members can import subscriptions into Shadowrocket on iPhone, use the same nodes, and reduce issues such as some members connecting while others lose connection or accounts being flagged repeatedly. It’s suitable for company collaboration, remote teams, or groups testing the same set of subscription nodes.
1. What to check before importing a subscription
Shadowrocket is just a client app. A stable connection mainly depends on the subscription, node quality, network conditions, and how accounts are used. For team use, it’s best for an administrator to organize the subscription links and share them with members, rather than having everyone copy different versions from various sources.
- Make sure the subscription link is complete: It usually starts with http or https. Be careful not to omit any parameters.
- Make sure members have installed Shadowrocket and allow it to add a VPN configuration.
- Avoid using the same account simultaneously on too many devices to prevent restrictions or frequent disconnections.
- If you’re using free nodes from this site, test them with a small group before sharing them with the whole team.
2. How to import a subscription into Shadowrocket
Here are the steps for the standard Shadowrocket interface. Labels may vary slightly between versions, but the process is much the same.
- Open Shadowrocket, go to the home screen, and tap “+” in the upper-right corner.
- Select “Subscribe” as the type.
- Paste the subscription link into the URL field. You can enter a name such as “Team Subscription” or “Backup Nodes” in the Remarks field.
- Tap Done or Save, return to the home screen, and pull down to refresh the subscription.
- Once the refresh is complete, the nodes will appear in the list. Select one and turn on the connection switch at the top.
- The first time you connect, iOS will prompt you to add a VPN configuration. Follow the prompts and enter your passcode to confirm.
If no nodes appear after importing the subscription, the link may have expired, the subscription address may be inaccessible on your network, or the client may not recognize the subscription format. Ask the administrator to copy the link again, or switch networks and try refreshing once more.
3. How team use affects account stability
Many people assume that knowing how to import a subscription is enough for long-term, stable use. But in a team setting, consistency in the account environment matters. For example, frequently switching regions while multiple people share the same node, or signing in to the same account from different cities and network gateways within a short period, may cause some websites to flag the activity as unusual.
We recommend that teams follow three guidelines: First, group nodes by purpose—for example, keep office use, research, and testing environments separate. Second, stick to a consistent region where possible instead of frequently switching from Asia to Europe or the Americas and back. Third, assign important accounts to a consistent team member, device, and node whenever possible. This can reduce the likelihood of verification challenges, security warnings, and failed logins.
4. Quick troubleshooting for connection failures
- Subscription refresh fails: Check whether the link has expired. Try switching between Wi-Fi and cellular data, then refresh again.
- A node is selectable but you can’t access the internet: Try another node from the same subscription, or check whether VPN is enabled on your device.
- Only some apps are inaccessible: Check Shadowrocket’s rule mode and temporarily switch to Global mode for testing.
- Multiple team members disconnect at the same time: The issue is likely with the subscription source, upstream nodes, or network routing. Wait for service to recover or switch to a backup subscription.
The key to using Shadowrocket subscriptions as a team isn’t just adding the link. It’s about using a consistent subscription source, choosing nodes in a coordinated way, and avoiding major changes to account environments. It’s a good idea to keep one primary subscription and one backup. If a problem occurs, refresh first, try a different node next, and switch networks last. This makes troubleshooting more efficient.