How to Use Shadowrocket: A Team Guide to Stable Accounts and Environments

This article addresses the practical question of how to use Shadowrocket, commonly known as “小火箭” (Little Rocket), with a focus on teams: how to install it, import nodes or subscriptions, apply consistent rules, and reduce issues such as frequent account anomalies, unstable environments, and connection failures.

1. Understand the basics of team use

Shadowrocket, often called “Little Rocket,” is a popular proxy client for iPhone and iPad. It handles connections and traffic routing; stability usually depends on node quality, subscription management, consistency of the IP environment, and whether team members switch between routes at random.

If your team uses it to sign in to the same types of overseas platforms, collaboration tools, or test accounts, avoid letting each person switch freely between countries and nodes. Signing in frequently from different regions and IPs on different carriers can trigger platform security checks, resulting in more CAPTCHAs, account verification requests, or failed logins.

2. Install Shadowrocket and import nodes

1. Get the Shadowrocket client ready on your iPhone or iPad, then install and open the app.
2. Get a working node or subscription link. You can use a service you already have, or look for free nodes on this site for temporary testing, though free nodes may be unreliable.
3. To import a single node, tap “+” in the top-right corner and select the relevant type, such as Vmess, VLESS, Trojan, or Shadowsocks. Enter the server, port, UUID or password, and other details, then save.
4. To import a subscription, copy the subscription link, tap “+” or “Add Subscription,” paste the URL, save it, and update the subscription.
5. Return to the home screen, select a node, and turn on the connection switch at the top. The first time you connect, follow the prompts to allow the VPN configuration to be added.

Subscriptions are generally more convenient for everyday users because nodes are easier to update. For team use, an administrator should manage the subscription centrally, while members simply update it rather than mixing in nodes from unknown sources.

3. Configure a more stable team environment

• Stick to one region: For the same business account, use a node in the same country or region over the long term. Don’t use the US today, Japan tomorrow, and Europe the day after.
• Use fixed groups: Create node groups for different purposes, such as “Office Collaboration,” “Research,” and “Temporary Testing,” to avoid mixing them up.
• Enable rule mode: Use Rule mode in Shadowrocket so domestic websites connect directly and overseas services use the proxy, avoiding unnecessary traffic routing.
• Document usage guidelines: Team members should know which accounts must use a fixed node and which are for ordinary browsing and can switch freely.

If a platform is sensitive to the login environment, have the same account used by the same team member, on the same device, and through the same route. Little Rocket is just a connection tool; account environment stability depends more on the team’s usage habits.

4. Troubleshoot common connection failures

1. First, check that your phone’s network is working. Try switching between Wi-Fi and cellular data.
2. Update the subscription and confirm that the node hasn’t expired or been removed.
3. Try another node in the same region to determine whether the issue is with a specific node or the client.
4. Check that your system time is correct. An incorrect time can cause TLS connection failures.
5. Turn the VPN off and back on. If necessary, restart Shadowrocket or your phone.
6. If you imported a node manually, check that the protocol, port, UUID, and encryption method are correct.

If you “can connect but can’t open web pages,” try switching to Global mode first. If Global mode works but Rule mode doesn’t, the issue is likely with rule-based routing. If none of the nodes work, check the subscription source or network restrictions.

5. Usage tips

For team use, the key isn’t switching nodes frequently but setting clear guidelines: who uses them, which region to use, which accounts they’re for, and what to do if something goes wrong. Keep one primary route and one or two backups in the same region. This makes troubleshooting easier and reduces the risks associated with major changes to the login environment.