This article addresses the practical question of how to import a subscription into Shadowrocket, with a focus on shared use by groups or teams: how to import a subscription and update nodes in Shadowrocket on iPhone or iPad, while reducing connection instability caused by mistakes, frequent switching, or shared accounts.
1. What to prepare before importing a subscription
Shadowrocket is just a client; it cannot connect to the internet on its own. You’ll first need a working subscription link or an individual node. A subscription is usually a URL beginning with http/https that contains node information for protocols such as VLESS, VMess, Trojan, and Shadowsocks. For team use, it’s best for an administrator to distribute a single subscription. Avoid repeatedly sharing different versions in group chats, as members may import the wrong link.
- Make sure Shadowrocket is installed and is allowed to add VPN configurations.
- Prepare a working subscription link, preferably obtained from a consistent source.
- If you’re using the free nodes on this site, copy the subscription or node link first, then import it for testing.
- Team members should use the same set of instructions to reduce repeated questions.
2. How to import a subscription into Shadowrocket
- Open Shadowrocket and go to the home screen.
- Tap the “+” in the upper-right corner, then select “Subscribe” or “Subscription” as the type.
- Paste the subscription link in the URL field. You can enter a team name or purpose as the remark, such as “Office backup.”
- Tap Done or Save. Return to the home screen and pull down to refresh the subscription.
- Once the refresh succeeds, the nodes will appear in the list. Select one.
- Turn on the connection switch in the upper-right corner. The first time you connect, follow the prompts to allow Shadowrocket to create a VPN configuration.
To import a single node, you can also copy its link and open Shadowrocket. Some versions will automatically detect it on your clipboard; alternatively, tap “+” and paste it manually. For team use, however, the subscription method is recommended: when nodes change, members only need to refresh instead of updating them one by one.
3. How team use affects account and environment stability
Many people assume that unstable connections are only caused by node quality, but account and usage conditions can also affect the experience in a team setting. For example, frequently switching the same set of nodes across different networks, or sharing a subscription indiscriminately with a large number of people, can lead to congested routes, security checks, or node abuse.
It’s a good idea to establish a few simple rules within the team: one person per device or one configuration per person. Don’t share the same subscription publicly. If a subscription needs to be changed, have the administrator notify everyone. Team members should avoid changing advanced settings such as proxy rules, DNS, or LAN bypass options. These steps can reduce the chances of problems like “it works for everyone else but not me” or “it was working a moment ago, then suddenly disconnected.”
4. How to troubleshoot connection failures
- Refresh the subscription first to make sure the nodes haven’t gone stale.
- Test two or three different nodes instead of relying on just one.
- Check that your device’s system time is correct; an incorrect time can cause TLS connection failures.
- Turn the VPN off and back on. If necessary, restart Shadowrocket.
- Switch from Wi-Fi to cellular data to see whether the issue is caused by restrictions on your local network.
- If none of the nodes work, contact your subscription provider or switch to a backup subscription.
When troubleshooting as a team, ask members to share a screenshot of the error, their network type, and the name of the selected node instead of simply saying “it doesn’t work.” The administrator can first check whether the subscription is working overall, then determine whether the problem is with an individual device or the connection route.
5. Usage tips
Importing a subscription into Shadowrocket is straightforward; the key is managing it afterward. For everyday users, remember three things: get subscriptions from trusted sources, refresh them regularly after importing, and when a connection fails, try another node before troubleshooting the network. Teams should also prioritize access control and centralized maintenance, and avoid letting subscription links spread without limit. This site provides free nodes and client tutorials for temporary testing and beginners. For long-term team use, prepare multiple backup options so a single subscription issue doesn’t affect everyone.