This guide explains how to import a subscription into Shadowrocket (小火箭) and why team use can affect account-environment stability. It’s for users who already have a V2Ray/VLESS/SSR/Clash subscription link and want to import it into Shadowrocket on an iPhone or iPad, while reducing frequent disconnections and account security checks.
1. Check these details before importing a subscription
Importing a subscription into Shadowrocket is straightforward, but team use can make issues like “it works for some people but not others” or “the account environment keeps changing” more likely. Before you begin, check three things: that the subscription link is complete, that Shadowrocket supports the node protocol, and whether the link requires a login or additional authentication. This site shares some free nodes and subscription guides, but free resources can vary in reliability. For teams, it’s especially important to group nodes and have a backup plan.
- The subscription link should start with http or https. Make sure you don’t leave out any parameters when copying it.
- Shadowrocket may not recognize Clash subscriptions directly. Check whether the subscription contains compatible nodes.
- Team members should follow the same guidelines and avoid switching regions and routes at will.
2. How to import a subscription into Shadowrocket
- Open Shadowrocket on your iPhone and go to the home screen.
- Tap “+” in the top-right corner and select “Subscribe” or “订阅” as the type.
- Paste your subscription link into the URL field. Add a note such as “Team backup” or “Work environment” to make it easy to identify.
- Tap Done, return to the home screen, and pull down to refresh. Wait for the node list to load.
- Select a working node with low latency, then turn on the connection switch at the top.
- The first time you connect, your device will ask to add a VPN configuration. Tap Allow and enter your device passcode to confirm.
If no nodes appear after importing, the issue is usually not with your phone. The subscription format may be incompatible, the link may have expired, or your network may be unable to access the subscription address. Try opening the link in a browser first. If it downloads or displays content, return to Shadowrocket and refresh.
3. How team use affects subscription and account-environment stability
The key to using Shadowrocket as a team isn’t just “getting connected”—it’s keeping the account environment as consistent as possible. For example, if multiple people manage an overseas platform account, ad dashboard, or social media account, switching from a US node one day to a Japan node the next—or frequently changing the outgoing IP for the same account across multiple devices—may trigger the platform’s security checks.
Set a few simple rules for your team: use the same regional node for each business account; don’t have multiple people log in to the same account at once; avoid switching routes repeatedly in a short period; and keep one primary node and one backup node for important accounts. In Shadowrocket, you can label nodes with notes such as “Account A – Primary” and “Account A – Backup” to reduce the risk of mistakes.
4. Troubleshooting common connection problems
- Subscription refresh fails: Check whether the link has expired, or switch between Wi-Fi and mobile data and try again.
- A node appears but won’t connect: Try another node from the same subscription to check whether the problem is limited to a single node.
- Connection succeeds but websites won’t load: Check Shadowrocket’s Global or Rules mode. If needed, switch to Global temporarily to test.
- Team members get different results: Check whether they’re using different subscription versions, rule configurations, or DNS settings.
Finally, remember that Shadowrocket is only the client. Stability also depends on subscription quality, your local network, node load, and how you use the service. For teams, standardizing the subscription import process and clearly documenting rules for switching nodes is usually more effective for long-term stability than changing nodes at random.