This article explains how to import subscriptions into Shadowrocket and why issues like disconnections, invalid nodes, and account anomalies can occur when shared by multiple team members. It is suitable for users who already have a subscription link and want to quickly import it into Shadowrocket on iPhone/iPad while keeping the account environment as stable as possible.
1. What to prepare before importing a subscription
Shadowrocket itself is only a client and cannot connect on its own. You need to prepare a valid subscription link or an individual node. A subscription is usually a URL beginning with https and contains node information such as VLESS, VMess, Trojan, and Shadowsocks. You can use your own subscription, or check the free nodes on this site for temporary testing, but free nodes are affected by the number of users and are usually less stable than dedicated lines.
- Make sure Shadowrocket is installed and allowed to add VPN configurations.
- Copy the complete subscription link without missing parameters or adding extra spaces.
- Try to avoid having multiple people edit the same subscription notes at the same time, so troubleshooting is easier.
2. Specific steps to import a subscription into Shadowrocket
- Open Shadowrocket, go to the home page, and tap the “+” in the upper-right corner.
- Select “Subscribe” or “Subscription” as the type.
- Paste the subscription link into the URL field. In the remarks field, you can enter a team name or purpose, such as “Operations Team – Backup.”
- Tap “Done” in the upper-right corner, then return to the home page and pull down to refresh the subscription.
- After the refresh succeeds, a node list will appear. Choose a node with lower latency and a matching protocol.
- Turn on the connection switch at the top. On first use, follow the prompt to allow the VPN configuration to be added.
If the list is empty after importing, first check whether the link has expired, whether it needs to be copied after logging in, or whether it was automatically truncated by chat software. Within a team, it is recommended to distribute subscriptions only through fixed documents or password management tools to avoid version confusion.
3. The relationship between team use and account environment stability
Many people think that as long as it connects, there is no problem, but in team collaboration scenarios, you need to pay even more attention to exit IP, region, number of devices, and switching frequency. For example, if the same business account logs in from a Hong Kong IP in the morning, a U.S. IP in the afternoon, and then multiple people operate it simultaneously from different devices at night, it can easily trigger platform risk controls, resulting in more verification codes, login anomalies, or account restrictions.
It is recommended that teams assign fixed nodes by role or business function: customer service, advertising, and information lookup should each use their own stable line whenever possible, and should not switch back and forth frequently between different countries and nodes. If you are only accessing information, you can use public or free nodes for testing; if long-term account logins are involved, it is best to use a more stable and more independent subscription environment.
4. Troubleshooting connection failures and subscription issues
- Refresh failed: Switch networks and try again, for example, from Wi-Fi to cellular data; confirm that the subscription address can be opened in a browser.
- A node can be selected but will not connect: try switching to another node, or check whether the system time is accurate.
- The connection succeeds but web pages will not open: switch between global/rule mode in Shadowrocket settings, or check the DNS settings.
- Some team members can use it while others cannot: this may be caused by differences in device systems, network carriers, or subscription concurrency limits.
During troubleshooting, do not have everyone randomly changing settings at the same time. It is recommended to assign one administrator to maintain the subscription link, while other members are only responsible for refreshing and selecting the designated node. This both reduces the chance of mistakes and makes it easier to determine whether the issue is with the client, the node, or account risk control.
In summary, importing a subscription into Shadowrocket is not complicated. The key is copying the correct link, refreshing successfully, and selecting the right node. For team use, stable usage habits are more important than simply pursuing a larger number of nodes, so try to maintain fixed purpose, fixed region, and less frequent switching.