How to Use Shadowrocket: Team Setup and Stability Guide

This guide explains how to use Shadowrocket (小火箭) and why sharing it across a team can affect account environment stability. Follow the steps to install the app, import nodes, connect, and learn how to reduce frequent disconnections, account security checks, and node mix-ups.

1. Before you begin

Shadowrocket, often called “小火箭” (“Little Rocket”) by Chinese-speaking users, is primarily used to import proxy nodes or subscription links on iPhone and iPad. For teams, the priority isn’t simply making sure everyone can connect—it’s keeping node assignments, regions, and usage habits consistent. If a business account logs in from Hong Kong one day, the United States the next, and Japan the day after, some platforms may flag the environment as unusual.

• Prepare an iPhone or iPad with Shadowrocket installed.
• Get a working node link, QR code, or subscription URL.
• Confirm which accounts team members will use, their region requirements, and their use cases.
• For testing, you can use the free nodes available on this site, but we recommend verifying that they work first.

2. How to import nodes into Shadowrocket

1. Open Shadowrocket and go to the home screen.
2. Tap “+” in the upper-right corner. For a single node, select the corresponding type and paste the link. For a subscription, select “Subscribe/订阅.”
3. Paste the subscription URL in the URL field. Add a label such as “Team Hong Kong” or “Test Nodes” to make it easy to identify.
4. Save, return to the home screen, then tap the subscription name to refresh the node list.
5. Select 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.

If you’re the team administrator, don’t give everyone unrestricted access to every node. Instead, group nodes by purpose—for example, have operations accounts always use one region and research accounts use another—to avoid conflicts.

3. Stability settings for team use

The most common issue with team use is “environment drift.” Multiple people logging into the same account, frequently switching nodes, or using devices with significantly different time and language settings can all trigger unusual-activity alerts. We recommend the following:

• Stick to one region: Use a node in the same country or region for each business account over the long term.
• Limit account access: Avoid having multiple people log in to the same platform account at the same time, especially from different cities or networks.
• Use consistent rules: Shadowrocket offers global and rule-based modes. Most users should start with “Configuration/Rule” mode, which routes only international services through the proxy.
• Update subscriptions regularly: If a node stops working or its latency increases, refresh the subscription first, then try a backup node.

4. How to troubleshoot connection issues

If the Shadowrocket switch is on but you still can’t access the internet, check the following in order. Don’t start by repeatedly reinstalling the app:

1. Make sure your phone has a working internet connection. You can first turn off Shadowrocket and test access to a domestic website.
2. Refresh the subscription and try another node in the same region.
3. Check that the node type has been identified correctly. Don’t manually alter links for types such as VLESS, VMess, or Trojan.
4. Open your system settings and make sure VPN access hasn’t been disabled.
5. If a particular app isn’t working, try switching to global mode to see whether the issue is caused by a rule not matching.
6. If it still doesn’t work, switch networks—for example, from Wi-Fi to cellular data.

If only one team member is affected, the cause is usually their local network, system VPN permissions, or an incorrectly imported node. If nobody can connect, the subscription may have expired, the nodes may be unavailable, or there may be an issue with the upstream connection.

5. Tips for teams

Shadowrocket is just a client; stability also depends on node quality, subscription maintenance, and consistent team practices. Keep a simple record of which account is assigned to which region, who uses it, and which backup node to switch to if an issue arises. This makes troubleshooting easier and reduces the risks associated with frequently changing environments. Free nodes can work for temporary testing, but for long-term account operations, prioritize node sources that are stable and can be maintained over time.