This article explains how to import a subscription into Shadowrocket (小火箭) and why sharing it across a team can affect account environment stability. It’s for users who already have a subscription link and need to set up Shadowrocket on an iPhone or iPad. Follow the steps to import and group nodes, then perform basic troubleshooting.
1. What to prepare before importing a subscription
Shadowrocket is just a client app; whether it can connect depends on whether your subscription is valid. A subscription is usually a link beginning with https that contains node information for protocols such as VLESS, VMess, Trojan, and Shadowsocks. This site also curates free nodes for testing and temporary use, but teams that need long-term access should prepare a more reliable subscription from a consistent source.
- Make sure Shadowrocket is installed on your device and allow it to add a VPN configuration.
- Copy the full subscription link, making sure you don’t omit any characters or include extra spaces.
- Team members should use a consistent naming convention, such as “Region-Purpose-Date.”
- Don’t post subscription links in public groups, as they may be abused and become unusable.
2. How to import a subscription into Shadowrocket
- Open Shadowrocket and go to the home screen, then tap “+” in the top-right corner.
- Select “Subscribe” as the type.
- Paste the subscription link into the URL field. You can enter “Team Subscription” or the project name as the remark.
- Tap “Done” in the top-right corner. 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, then turn on the connection switch 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 no nodes appear after importing the subscription, first check whether the link has expired, whether you need to log in before copying it, or whether a chat app truncated it automatically. After a successful import, choose a node with low latency and a clear name. Avoid switching back and forth between regions frequently.
3. How team use affects account environment stability
Many teams aren’t just concerned with whether they can connect; they also want to know whether their accounts might be flagged when multiple people work together. The key is consistency in network egress. If the same business account is accessed from the United States one moment, then Japan or Europe ten minutes later, the platform may flag the environment as unusual and trigger verification or restrictions.
For team use, group nodes by purpose: keep a dedicated group for operations accounts, use another group for research, and reserve free nodes for temporary testing. This helps avoid unnecessary IP changes. For accounts that need to stay logged in long term, stick to one region and, if necessary, one node. Don’t switch just because another node has slightly lower latency.
Also, avoid using the subscription on too many devices at once. When multiple people share one subscription, a large number of simultaneous connections may cause congestion, trigger risk controls, or make the connection unstable. Administrators can update the subscription regularly and notify members to refresh it at the same time, so no one continues using outdated nodes.
4. Common connection issues and how to troubleshoot them
- Subscription refresh fails: Switch networks and try again—for example, switch from Wi-Fi to cellular. Check whether the subscription link opens in a browser.
- Node times out: Try another node in the same region, or wait a few minutes before testing again. Don’t tap repeatedly in quick succession.
- Connected, but webpages won’t load: Check the global routing and rule mode settings, or temporarily switch to global mode for testing.
- Team members get different results: Compare Shadowrocket versions, subscription refresh times, selected nodes, and local networks.
In short, importing a subscription into Shadowrocket is straightforward. The challenge is managing node switching, subscription distribution, and the account login environment when working as a team. Keep three things in mind: use a reliable subscription source, group nodes by purpose, and keep the region and network egress stable for important accounts. This makes it easier for team members to get started and reduces the likelihood of connection failures and account issues.