This article addresses the practical question of “how to use Shadowrocket,” with a focus on multi-person team scenarios: how to install it, import nodes or subscriptions, unify routing rules, and reduce login errors, risk controls, or unstable connections caused by changes in account environment.
1. Before You Start: Standardize the Client and Node Source First
Shadowrocket, often called “Little Rocket,” is mainly used on iPhone/iPad to import proxy nodes, subscription links, and route traffic by rules. When used by a team, it is not recommended for everyone to randomly use different configurations, otherwise troubleshooting becomes very difficult. It is recommended to first confirm three things:
- All members use the same version or a similar version of Shadowrocket.
- Use a unified node source, for example a team subscription, or temporarily test availability from this site’s free node page.
- Clarify the purpose: web browsing, logging into overseas tools, accessing work backends, etc. Different use cases have different stability requirements.
The core of team environment stability is not how fast a single node is, but keeping the same account on a similar region, exit IP type, and access pattern as much as possible, avoiding frequent switching across countries and networks.
2. Steps to Import Nodes into Shadowrocket
- Open Shadowrocket on your iOS device.
- Tap the “+” in the upper right corner, choose a node type such as VLESS, VMess, Trojan, or Shadowsocks, and fill in the address, port, UUID/password, TLS, and other parameters according to the information provided.
- If you received a subscription link, tap “Configuration” or “Subscription,” choose “Add Subscription,” paste the link, and update it.
- Return to the home page, select a node, turn on the top switch, and when using it for the first time, allow VPN configuration to be added as prompted.
- Open a browser and visit the target website to test it. If it does not open, switch to another node in the same region or check whether the subscription has expired.
For ordinary users, importing via subscription is more recommended, because when nodes change later, you only need to “update subscription” instead of modifying them one by one manually. If you are only testing temporarily, you can also copy and import the free node configurations provided by this site, but free nodes fluctuate more than normal ones, so they are not recommended for long-term use with important accounts.
3. How to Configure It More Stably for Team Use
When multiple people share the same guide, it is recommended that the administrator first provide unified rules: which apps use the proxy, which connect directly, and which region is fixed for account login. Shadowrocket can use rule mode in “Configuration” so that domestic websites connect directly while overseas services use the proxy, reducing unnecessary detours.
Do not let the same business account log in with a US node today, a Japan node tomorrow, and a Europe node the day after. Many platforms assess risk based on login region, IP changes, device fingerprint, and access frequency. During team collaboration, fixed node groups can be assigned by member or business line, and at minimum the region should remain consistent.
If you need to log into sensitive platforms such as work backends, advertising accounts, or social media accounts, it is recommended to connect to the node first, then open the corresponding app or webpage; after finishing, do not frequently toggle the VPN on and off. Before switching nodes, it is best to log out of the account or wait for a while before logging in again, to reduce abnormal prompts caused by sudden environment changes.
4. Troubleshooting Connection Failures and Account Exceptions
- Cannot connect: first update the subscription, then switch to another node with the same protocol, and confirm that the phone time is set automatically.
- Can connect but cannot open webpages: check whether “Global Routing/Rule Routing” is selected, and try switching to rule mode or global mode for testing.
- A specific app is behaving abnormally: close the app, reconnect the node, and reopen it; if necessary, clear the app cache.
- The account shows a risk warning: stop switching regions frequently, use a fixed exit, and reduce multiple people logging into the same account at the same time.
The recommended troubleshooting order is to check in sequence: “whether the subscription is available — whether the node is online — whether the rules are correct — whether the account environment has changed.” Do not keep changing country nodes as soon as a problem appears, because this often makes the account environment even more unstable.
In summary, the basic use of Shadowrocket is not complicated: import a subscription, select a node, enable the connection, and route traffic according to rules. The key to team use is unified configuration, fixed regions, reduced frequent switching, and troubleshooting node issues separately from account risk-control issues. This makes it easier for members to follow and is also more conducive to long-term stable use.