This article explains how to import a subscription into Shadowrocket and why teams may experience frequent disconnections, inactive nodes, or account issues. Follow the steps below to import a subscription into Shadowrocket on your iPhone or iPad, and use consistent guidelines to reduce connection instability caused by team members making configuration mistakes.
1. Basic steps for importing a subscription into Shadowrocket
Shadowrocket is just a client; whether it can connect depends on your subscription link, node protocol, and network environment. This site shares some free node resources for testing connectivity. For long-term team use, we recommend choosing a subscription from a stable, well-managed source.
- Open Shadowrocket and go to the home screen, then tap “+” in the upper-right corner.
- Select “Subscribe” or “订阅” as the type. Make sure you don’t select a type for a single node by mistake.
- Paste the subscription link into the URL field. For the remark, enter “Team Subscription” or the project name.
- Tap Done, return to the home screen, and pull down to refresh the subscription. Wait for the node list to appear.
- Choose a node with low latency and a compatible protocol, then turn on the connection toggle at the top.
- The first time you connect, the system will prompt you to add a VPN configuration. Tap Allow and enter your device passcode.
If the subscription is empty after importing, first check that the link is complete. Common mistakes include missing the token, including a line break, or using a webpage URL instead of a subscription URL.
2. For teams: keeping account environments stable
When multiple team members share a subscription, the problem is often not how to import a subscription into Shadowrocket, but inconsistent usage. For example, frequently switching between country nodes, sharing the subscription externally, or using an outdated client can all increase the likelihood of connection issues.
- Don’t share the same device configuration file: Each member should import the subscription on their own device to avoid configurations overwriting one another.
- Avoid frequently switching between regions: Work accounts, email, and collaboration platforms are sensitive to login environments. Logging in from multiple countries within a short period may trigger security checks.
- Use consistent client versions: Wherever possible, team members should use similar versions of Shadowrocket to minimize differences in how rules are interpreted.
- Set a preferred node group: Agree on a “preferred node for work” and switch to a backup only if the connection fails.
- Protect the subscription link: The subscription is effectively an account access point, so don’t post it in public groups or share it in screenshots.
3. Troubleshooting connection failures and subscription issues
If the subscription imports successfully but won’t connect, troubleshoot in this order. First, update the subscription in Shadowrocket; then try other nodes in the same group; finally, check whether Low Data Mode is enabled, another proxy app is causing a conflict, or your local network is restricted. If all nodes time out, try switching between Wi-Fi and cellular data.
If only one team member is having trouble, check whether their subscription has expired, their system time is correct, and they have another VPN configuration installed. If all team members are affected at the same time, the subscription source or upstream nodes are likely unavailable. Wait for maintenance to finish or switch to a working subscription.
4. Recommended guidelines for team use
Your team can create a simple set of instructions: the administrator distributes the subscription link; members import it without modifying it; update the subscription before connecting; use a consistent region during work hours; and, if a problem occurs, capture the node name and error message in a screenshot. This makes troubleshooting easier and helps reduce the risk of account restrictions. In short, importing a subscription into Shadowrocket is straightforward. What really affects stability is the subscription source, node-switching habits, and whether team members follow consistent guidelines.