This article explains how to use Shadowrocket (小火箭) and why sharing nodes across a team can lead to disconnections, risk-control checks, or unstable connections. You’ll learn how to import nodes or subscriptions, route traffic selectively on iPhone or iPad, and reduce the likelihood of account-environment anomalies by using consistent rules.
1. First, understand Shadowrocket’s role in a team
Often called 小火箭, Shadowrocket is a popular proxy client for iOS. It does not provide proxy connections itself; instead, it lets you configure V2Ray, VLESS, Trojan, SS, and other nodes on your phone, then forward traffic according to rules. For teams, stability depends not only on node quality, but also on whether multiple people use the same exit, whether their rules are consistent, and how often their login locations change.
If team members connect through Hong Kong one day and the US the next, while logging in to the same business account, the platform may flag the account environment as unstable. The recommended approach for teams is to keep node regions consistent, use the same traffic-routing rules, and avoid frequently switching exit points.
2. Basic steps for using Shadowrocket
- Install Shadowrocket on your iPhone or iPad and allow it to add a VPN configuration.
- Get a node or subscription link. You can use your own service or test with the free nodes on this site. Note that the stability of free nodes may vary over time.
- Open Shadowrocket, tap “+” in the upper-right corner, and select “Subscribe” to import a subscription, or choose the appropriate protocol and paste in a node link manually.
- Once imported, return to the home screen, select a node, and turn on the connection switch at the top.
- The first time you connect, a system VPN permission prompt will appear. Tap Allow. When the VPN icon appears in the status bar, you’re connected.
We recommend first visiting a search engine or an IP lookup site in your browser to confirm that your current exit region meets your team’s requirements. Don’t rely solely on the client showing “Connected”—also verify that your traffic is actually going through the proxy.
3. How teams can keep account environments stable
- Stick to one region: For the same business account, use a node in the same country or region over the long term to avoid sudden location changes.
- Use the same rules: Have all team members use the same Shadowrocket rules to avoid some members using a global proxy while others route traffic selectively or connect directly.
- Keep device usage consistent: Avoid having multiple people log in to the same account at the same time from different cities and exit points.
- Separate by purpose: Use different nodes for activities such as research, social media management, and development testing to prevent them from affecting one another.
In Shadowrocket, go to “Configuration” and select a routing mode. For most teams, rule-based routing is recommended: commonly used domestic sites connect directly, while overseas services use the proxy. If an account is sensitive to location, you can use a global proxy for a short time, but make sure all related activity uses the same exit point.
4. Troubleshooting connection failures and instability
If Shadowrocket can’t connect, check the following in order: whether the node has expired, whether the subscription needs updating, whether your phone’s network is working, and whether the system VPN permission has been disabled. Then switch to a backup node in the same region rather than immediately switching to a different region.
If you’re connected but browsing is slow, try updating the subscription, switching to a node that uses the same protocol, disconnecting from poor-quality public Wi-Fi, or restarting the client. If only one app is behaving abnormally, the issue is usually that a rule isn’t matching. Check the domain’s routing in the logs, then adjust the rules as needed.
Finally, remember that Shadowrocket is only a client. A stable account environment depends on the right combination of nodes, rules, and login habits. For teams, setting shared guidelines and having members import the same subscription and rules is often more effective than frequently changing nodes.