This article addresses how to import a subscription into Shadowrocket and why, in multi-person team use, some people can connect while others experience frequent disconnections. Shadowrocket usually refers to the iOS app Shadowrocket. Importing a subscription is only the first step—account environment, node selection, update frequency, and usage practices all affect overall stability.
1. What to prepare before importing a subscription
For team use, it’s not recommended to casually forward the same configuration file to everyone. A safer approach is for an administrator to obtain the subscription link centrally, then distribute it by member or device for easier troubleshooting later. Subscription links generally come from airport services, internal company network services, or the free node subscription test resources compiled on this site. Free nodes are suitable for temporary trial use, but their stability may change at any time.
- Make sure Shadowrocket is installed and allowed to add VPN configurations.
- Prepare a valid subscription link, usually starting with http or https.
- Avoid exposing the subscription in plain text for long periods in WeChat groups or public documents.
- Team members should, as much as possible, use their own independent accounts or separate subscription entry points.
2. Specific steps to import a subscription into Shadowrocket
- Open Shadowrocket and go to the home page.
- Tap the “+” icon in the upper right and choose “Subscribe” or “Subscription” as the type.
- Paste the subscription link into the URL field; for remarks, you can enter something like “Team Line” or “Backup Subscription.”
- Tap Done or Save, then return to the home page and pull down to refresh.
- After refreshing, multiple nodes will appear. Choose one with lower latency and a clear name.
- Turn on the connection switch in the upper right. On first use, follow the prompt to allow VPN creation.
If no nodes appear after importing the subscription, first copy the link into a browser to test whether it opens. If it says the format is incorrect, the subscription type may be incompatible, and you’ll need to confirm whether it supports Shadowrocket.
3. How account environment stability relates to team use
Many teams assume that “if it can be imported, it will work stably,” but that’s not entirely true. If multiple people use the same account, the same subscription, and the same exit node at the same time, it may trigger server-side limits or risk controls. This can show up as sudden disconnections, nodes turning red, or subscription update failures. In team scenarios, the key is to reduce abnormal concurrency and chaotic operations.
It’s recommended that administrators set a few simple rules: don’t let everyone stay on the same node long-term; don’t repeatedly toggle the VPN on and off just to test speed; don’t share the subscription with non-team members; and report promptly after switching phones or reinstalling the app. This helps reduce instability caused by “excessive account environment changes.”
4. Recommended settings for team use
- Group by region or purpose, such as office use, document lookup, or backup lines.
- Set fixed update times: refresh manually daily or weekly, and don’t have everyone refresh frequently at the same time.
- Keep a backup subscription: switch only when the main subscription has issues, to avoid having no access point in an emergency.
- Use a consistent troubleshooting process: first check whether the subscription has expired, then check node latency, and finally test by switching networks.
In Shadowrocket, you can also go to the configuration or rules page and choose an appropriate rule mode. Ordinary users are advised to use “Configuration” or “Rules” mode. If you’re unfamiliar with the app, don’t casually change advanced items such as DNS, Rewrite, or MITM, since incorrect settings may cause some apps to lose network access.
5. How to troubleshoot connection failures
Step one: turn off the VPN, switch between Wi-Fi and cellular, and try again. Step two: refresh the subscription and switch to another node. Step three: check whether the system time is correct. Step four: delete the old subscription and import it again. If only one member fails, it is most likely due to the local device network, system permissions, or account concurrency issues. If all members fail, the subscription source or upstream nodes are usually experiencing problems.
One final reminder: a subscription link is equivalent to account credentials, so even within a team, its visibility should be controlled. Importing a subscription into Shadowrocket is not complicated, but if you want the team to use it stably, you need to standardize node allocation, subscription updates, and the troubleshooting process in order to reduce repeated disconnections and mutual interference.