How to Use Shadowrocket: Team Setup & Account Environment Stability Guide

This article addresses both “how to use Shadowrocket” and why multi-person team usage can affect account environment stability. It is suitable for ordinary users who need to import nodes on iPhone/iPad, route traffic by scenario, reduce frequent disconnections, and lower the risk of account controls.

1. Installation and Basic Preparation

Shadowrocket, often called the “little rocket,” is a commonly used proxy client on iOS that supports protocols such as Vmess, VLESS, Trojan, and Shadowsocks. Before using it, please make sure your device system is functioning normally, your network is available, and you have prepared a node link or subscription URL. This site also compiles testable free nodes, which are suitable for temporarily verifying whether the client is configured correctly, but for long-term team use, it is recommended to choose a more stable subscription source.

1. Open the App Store, search for Shadowrocket, and install it.
2. Enter the client and allow it to add a VPN configuration; otherwise, it will not be able to take over network traffic.
3. Prepare a node link, QR code, or subscription URL.
4. Test connectivity on a personal device first, then roll it out to team members.

2. How to Import Nodes and Subscriptions

After opening Shadowrocket, tap the “+” in the upper-right corner. If it is a single node, choose the corresponding protocol and paste the link; if it is a subscription, select “Subscribe/订阅,” paste the subscription address, and save it. After saving, return to the home page, tap the node name, and then turn on the switch at the top to connect.

For team use, it is recommended to standardize on subscription import rather than having everyone manually copy multiple nodes. This makes it easier later to change routes, remove invalid nodes, and adjust groups, while also reducing connection failures caused by members entering parameters incorrectly.

3. Rule-Based Routing: Don’t Send All Traffic Through the Proxy

Many unstable account environments are not caused by Shadowrocket itself, but by network exit points changing too frequently. For example, when logging into collaboration tools, social media accounts, ad dashboards, or e-commerce platforms, using one region today and another tomorrow can easily trigger verification checks.

• General browsing of overseas sites: you can use automatic selection or a node with lower latency.
• Team account logins: try to keep to the same region and the same node or group of routes.
• Domestic apps: direct connection is recommended to avoid issues with location, payments, or verification codes caused by proxying.
• Downloads and video: do not share the same node with important accounts, to avoid congestion affecting stability.

In Shadowrocket’s “Configuration,” you can choose rule mode. Beginners can start with the default rules and then adjust based on actual needs. The key principle is: switch important accounts as little as possible, and keep domestic services on direct connection whenever possible.

4. Stability Recommendations for Team Use

When multiple people share usage, the biggest risk is everyone switching nodes at will or casually enabling global proxy mode. It is recommended that teams establish simple rules: fixed routes for account-related work, separate routes for testing work, and free nodes only for temporary access. This can reduce issues such as abnormal logins, SMS verification, and secondary verification caused by a chaotic network fingerprint.

Also note that the same platform account should not be logged into by multiple members from different countries or regions within a short period of time. Even if the nodes work, that does not mean the account environment is stable. A more reliable approach is to assign fixed devices and fixed network strategies to specific roles or accounts, and record the names of commonly used nodes.

5. How to Troubleshoot Connection Failures

1. First confirm that the phone itself can access the internet normally; turn airplane mode off and then back on.
2. Check whether the nodes have expired and whether the subscription has updated; if necessary, refresh the subscription.
3. Switch to a backup node in the same region, and avoid frequent direct changes across regions.
4. Confirm that the system VPN permission has been granted and that Shadowrocket’s top switch is turned on.
5. If only a certain app is having issues, try changing from global mode to rule mode.

If it still fails, you can first import the free nodes provided by this site to perform a connectivity test. If the free nodes work, it means the client configuration is basically correct; if none of them work, then check your local network, DNS, time settings, or client version.

In summary, the key to using Shadowrocket is not just “being able to connect,” but also standardized node importing, sensible routing rules, and fixed team routes. For scenarios that require multi-person collaboration, a stable account environment is often more important than one-time connection speed.