This article explains how to use “Shadowrocket” and why issues like disconnections, account anomalies, and unstable nodes are common in multi-person team usage. You’ll learn how to install it, import nodes, enable the proxy, and make the usage environment more stable for team members.
1. Basic Steps for Using Shadowrocket
Shadowrocket is commonly called “Little Rocket” by Chinese users and is mainly used on iPhone/iPad to import V2Ray, VLESS, Trojan, Shadowsocks, and other nodes or subscriptions. Ordinary users do not need to understand server-side configuration; they only need a working node or subscription link.
- Install Shadowrocket on your iOS device, and when opening it for the first time, allow it to add a VPN configuration.
- Tap the “+” in the top right corner. You can choose “Type” to manually enter a node, or choose “Subscribe/Subscription” to paste a subscription link.
- If you use free nodes provided by this site or similar sources, it is recommended to copy the full subscription address first to avoid manually entering the wrong port, UUID, or encryption parameters.
- After importing, return to the homepage, select a node, and turn on the switch at the top.
- When connecting for the first time, the system will prompt for VPN permission confirmation. Tap Allow and enter your device passcode.
After a successful connection, a VPN icon will usually appear in the status bar. If webpages will not open, first switch nodes, then check the rule mode.
2. Why Account Environment Stability Matters for Team Use
Many teams use Shadowrocket not just for browsing webpages, but for logging into overseas tools, social media backends, collaboration platforms, and more. In this case, a stable network exit is more important than whether it can connect just once. If the same account frequently switches between different countries, different IPs, and different devices, the platform may flag it as an abnormal login.
For team use, it is recommended to follow the “three fixeds” principle: fixed members, fixed devices, fixed node regions. For example, the member responsible for a certain account should try to use the same phone and the same regional node over the long term, rather than frequently switching between the US today, Japan tomorrow, and Europe the day after. Free nodes can be used for temporary lookups and testing, but when long-term account operations are involved, frequent changes of exit should be minimized.
3. Recommended Shadowrocket Settings
- Proxy mode: Beginners can start with “Configuration/Rules” mode, where domestic websites connect directly and overseas websites go through the proxy.
- Node naming: Teams can name nodes by “region-purpose-member,” for example, “US-Research-A.”
- Subscription updates: Do not have multiple people frequently refresh the subscription at the same time. It is recommended to update it once a day at a fixed time.
- Rule maintenance: If a certain app cannot access the network, you can temporarily switch to “Global Proxy” for testing to confirm whether the issue is caused by the rules.
4. Troubleshooting Connection Failures and Instability
If Shadowrocket cannot connect, do not repeatedly toggle it on and off at first. Check in order: whether the node has expired, whether the subscription has been updated, whether the system time is correct, whether VPN permission is allowed, and whether the current Wi-Fi/cellular network is available. If only one app is behaving abnormally, try switching the rule mode; if all websites fail to open, the node is most likely unavailable or the network is restricted.
In team scenarios, avoid having multiple people share and log into the same sensitive account at the same time. It is recommended to keep a simple tracking sheet recording the account, device, commonly used node region, and person in charge. This can both improve troubleshooting efficiency and reduce the risk caused by frequent changes in the account environment.
In summary, using Shadowrocket is not complicated. The key is to correctly import subscriptions, choose suitable rules, and maintain a relatively stable device and node environment within the team.