This guide explains how to import a subscription into Shadowrocket and how teams can reduce disconnections, configuration mix-ups, and account issues. “Shadowrocket” here typically refers to the iOS app. It supports subscription links for V2Ray, VLESS, Trojan, SS, and other protocols. If you’re a team member, simply follow the steps using the subscription URL provided by your administrator.
1. What to prepare before importing a subscription
Before you begin, make sure Shadowrocket is installed and that you have a working subscription link. Subscription links are usually provided by your service provider or team administrator. You can also test with free nodes listed on this site, but their stability depends on the number of users online and the status of the routes, so they’re not recommended as a team’s sole long-term solution.
- Make sure your iPhone has a working internet connection. Consider turning off Low Power Mode first.
- Make sure the subscription link is complete. It usually starts with http or https.
- Don’t share your team’s subscription link in public groups, as misuse could make it stop working.
- If you already have an older configuration, back it up or take a screenshot first to avoid accidentally deleting it.
2. How to import a subscription into Shadowrocket
- Open Shadowrocket and go to the main screen.
- Tap the “+” in the top-right corner, then select “Subscribe” or “Subscription” as the type.
- Paste the subscription link from your administrator into the URL field.
- In the Remarks field, enter a team name, department, or purpose, such as “Design Team – Office.”
- Tap “Done” in the top-right corner to save.
- Return to the home screen, tap the subscription you just added, and select “Update” or pull down to refresh.
- Once the node list appears, choose a clearly named node with low latency.
- Turn on the connection switch at the top. The first time you connect, allow Shadowrocket to add a VPN configuration.
Once connected, a VPN icon will appear in the status bar. Try visiting a commonly used work website or a search page to test the connection. Don’t rely solely on the app’s “Connected” status—some nodes may connect but still be unable to access the services you need.
3. How subscriptions and account stability are related for teams
The biggest team-related issues usually aren’t about importing a subscription; they’re about reduced stability caused by sharing accounts, frequently switching environments, or exposing subscription links. A subscription is just a way to load configurations. Your experience depends on node availability, the number of users, account security checks, and client settings.
Don’t have multiple people use the same personal account to sign in to sensitive platforms such as email, ad dashboards, or social media accounts. Even if the VPN node is working normally, frequent sign-ins by different team members from different cities and devices may trigger security checks. Teams should keep usage consistent: use one set of nodes for work access and another for test browsing, and avoid mixing the two.
If your administrator provides nodes in multiple regions, you don’t need to switch between them frequently. When account environment stability is important, stick to the same region or route for a while. Frequently switching between countries and IP addresses can cause significant changes to your sign-in environment.
4. Troubleshooting connection problems after importing
- Tap “Update” on the subscription first to make sure the nodes haven’t gone stale.
- Test two or three different nodes to determine whether the problem is with one node or the entire service.
- Check that your device’s system time is correct. An incorrect time can cause TLS connection failures.
- Turn off other VPNs, proxies, and accelerators to avoid configuration conflicts.
- Switch between Wi-Fi and cellular data to rule out local network restrictions.
- If the subscription update fails, copy the link again and make sure it doesn’t contain spaces or line breaks.
Team administrators can also use consistent names for subscriptions and nodes, such as “Purpose-Region-Number,” so team members can report problems accurately. When reporting an issue, include the node name, network type, a screenshot of the error, and when it occurred. This makes troubleshooting much easier than simply saying “It doesn’t work.”
5. Recommendations
Importing a subscription into Shadowrocket is straightforward. The key is to keep configuration sources clear, control access to subscriptions, and maintain a relatively consistent account environment. For teams, one person should be responsible for maintaining the subscription link. Team members should simply update the subscription and select the designated node. If something goes wrong, refresh the subscription, try another node, switch networks, and then report the issue to the administrator. This helps improve connection success rates and reduces instability caused by frequent changes to the account environment.