This article explains how to use Shadowrocket (“小火箭”) and why sharing nodes across a team can affect account environment stability. It’s intended for everyday users who want to import a subscription, switch nodes, and troubleshoot connection failures on an iPhone or iPad while reducing login issues and risk-control warnings.
I. Basic Shadowrocket Setup
Shadowrocket, often called “小火箭,” is primarily used to import proxy nodes such as V2Ray, VLESS, Trojan, and Shadowsocks on iOS devices. Before you get started, make sure you have a working node link or subscription URL. This site also provides free nodes for testing, but their reliability can vary, so avoid relying on them for long-term access to important accounts.
- Open Shadowrocket and tap “+” in the upper-right corner of the main screen.
- For a single node, select the relevant protocol and enter the server, port, UUID, password, and other details. For a subscription, select “Subscribe/订阅” and paste the subscription URL.
- Save, return to the home screen, and pull down to refresh the subscription. Wait for the node list to load.
- Tap a node and turn on the connection switch at the top. The first time you connect, follow the prompts to allow Shadowrocket to add a VPN configuration.
- Open a browser and visit a test site to confirm that your IP address has changed, then sign in to the account you need to use.
For most users, subscriptions are the better option because you can update your nodes by refreshing the subscription instead of editing each one manually. If you import a subscription with many nodes and aren’t sure which to choose, start with a low-latency node in a region that suits your needs.
II. Why Account Environment Stability Matters for Teams
For teams using Shadowrocket, the most common issue isn’t whether the connection works—it’s frequent changes to the account’s login environment. For example, if the same account is accessed from a US IP address one day, a Japanese IP address the next, and then a European IP address half an hour later, the platform may flag the activity as unusual. This can trigger CAPTCHAs, additional verification, login restrictions, or other risk-control measures.
To avoid this, teams should follow three guidelines: First, keep each account on the same region and connection whenever possible. Second, don’t have multiple people sign in to the same account from different nodes at the same time. Third, avoid frequently switching free nodes when using important accounts. Free nodes are fine for temporary access and connection tests, but team collaboration benefits more from a consistent login environment.
- Assign nodes by account: Keep each account on one region or a designated set of backup nodes.
- Track how team members use them: Keep a simple record of who has signed in, on which device, and through which region.
- Avoid switching everything indiscriminately: Let apps that don’t need a proxy connect directly to reduce unnecessary traffic.
III. Recommended Shadowrocket Settings
Shadowrocket offers several routing modes, including Global, Config, and Direct. For team use, Config/Rules mode is generally preferable. It lets commonly used services in China connect directly while routing only the sites that need a proxy through one. This can help reduce network issues and the chances of sudden changes to an account’s access pattern.
If your subscription includes nodes in multiple regions, rename them—for example, “Account A – Hong Kong Backup” or “Account B – Japan Primary”—to help team members avoid selecting the wrong one. Before signing in to sensitive accounts, such as those for browsers, social media, or cross-border tools, check that the correct node is active and that it’s connected to the right region.
IV. Troubleshooting Connection Failures and Instability
If Shadowrocket won’t connect, check the following in order: whether the subscription has expired or the URL was entered incorrectly; whether the node has been removed; whether your device’s date and time are correct; whether VPN configurations are allowed on your phone; and whether your current network is blocking proxy connections. You can also test over Wi-Fi and cellular data to determine whether the issue is with the node or your local network.
If you can connect but webpages won’t load, check your DNS and routing mode. If one app works but another doesn’t, the routing rules may not be matching correctly. When a team member has an issue, don’t immediately switch nodes across the board. First, capture the node name, error message, and network in use to make troubleshooting easier for everyone. Keeping the node, region, device, and account relatively consistent is generally more reliable than constantly chasing new nodes.