This article explains how team members can import nodes, apply consistent rules, reduce frequent disconnections, and avoid account security checks when using Shadowrocket on iPhone or iPad. It is intended for everyday users who need to collaborate on accessing overseas tools, reference sites, or test environments.
1. Before you start: Standardize the client and node source
Shadowrocket, commonly known as “小火箭” (Little Rocket), is a popular proxy client for iOS. For team use, the key is not to have everyone find nodes on their own, but to keep the client version, subscription source, and routing rules as consistent as possible. This helps prevent frequent IP changes across different network environments on the same account.
- Make sure Shadowrocket is installed on the device and that you allow it to add a VPN configuration.
- Prepare a working subscription link or an individual node link. Common protocols include VLESS, VMess, Trojan, and SS.
- If you’re using the free nodes on this site, copy the subscription or individual node link first, then import it into the client and test that it works.
- For team use, assign one administrator to maintain the subscription; other members only need to update it.
2. How to import a subscription into Shadowrocket
Importing a subscription makes it easier to manage nodes across a team. When nodes change, members can simply refresh the subscription instead of adding them manually each time.
- Open Shadowrocket and tap “+” in the upper-right corner.
- Select “Subscribe” or “Subscription” as the type.
- Paste the subscription link into the URL field and enter a note describing the team or purpose, such as “Reference searches.”
- Tap Save. Return to the home screen, open the subscription, and select “Update.”
- Select a node and turn on the switch at the top. The first time you connect, follow the prompts to allow the VPN configuration.
If you have a link for a single node, copy it and open Shadowrocket; it will usually be recognized automatically. You can also tap “+” and enter the details manually after selecting the corresponding protocol. Subscriptions are generally the better choice for everyday users, as they help prevent configuration errors.
3. How teams can improve account stability
Many overseas platforms monitor login locations, IP changes, device fingerprints, and activity frequency. When several team members share an account, using nodes in different regions or on different carriers can lead to verification checks, login restrictions, or security alerts. To reduce the risk, follow these guidelines:
- Stick to one region: Use a node in the same country or region for the same business account over the long term. Avoid switching regions frequently.
- Limit who uses the account: Avoid having multiple people log in to the same account at the same time. If necessary, take turns.
- Use consistent rules: Apply the same routing rules across the team instead of switching back and forth between direct and proxy connections.
- Use a consistent connection: Avoid switching between Wi-Fi, cellular data, and different VPNs just before logging in to sensitive accounts.
This cannot guarantee that a platform will never ask for verification, but it can significantly reduce instability caused by drastic changes in the connection environment. For teams, a stable setup matters more than chasing a particular node in the short term.
4. Recommended routing rule settings
Go to the “Configuration” page in Shadowrocket to use the default configuration or import a shared team configuration. For most teams, a good approach is to route domestic traffic directly, proxy overseas traffic, and enable ad blocking as needed. If you’re unfamiliar with the rules, don’t delete rules such as FINAL, DOMAIN, or GEOIP at random, or some apps may lose internet access.
When testing, start by turning off advanced features such as complex rewrites, scripts, and MITM, and use only the basic proxy settings. Once you’ve confirmed that the node works, enable additional features as needed. This makes troubleshooting easier.
5. Troubleshooting connection failures and disconnections
- Subscription update fails: Check that the link is complete and that your network can access it. If necessary, switch networks and try again.
- Node won’t connect: Try another node in the same subscription, or check that the protocol, port, UUID, or password hasn’t been changed by mistake.
- Connected, but webpages won’t load: Switch the routing mode to “Global” for testing. If it works in Global mode, the issue is with the rules.
- An account is frequently asked to verify: Switch nodes less often, log in from a consistent region, and avoid having multiple people use the account at once.
- Unstable speed: Free nodes can be significantly affected by network routes and the number of users, so it’s a good idea to keep a few alternatives ready.
In summary, using Shadowrocket is straightforward: install the client, import a subscription, select a node, and turn on the connection. For team use, the keys are to standardize the node source and rules, and minimize changes to the account’s connection environment. Following these steps can make day-to-day access and collaboration more reliable, while also making issues easier to troubleshoot.