This guide explains how to use Shadowrocket in practice: install the app on an iPhone, import nodes, choose a routing mode, and reduce account verification caused by frequent changes in network egress when using it with a team. Shadowrocket is a proxy client; it does not come with ready-to-use connections and cannot guarantee that an account won’t trigger security checks.
1. Get the app and node details ready
Search for Shadowrocket in the App Store and check the app name and developer information. Availability for purchase and download depends on what’s shown in your regional store. Don’t install modified versions provided by strangers, and don’t sign someone else’s Apple ID into iCloud on your device just to download the app. Team members should obtain the app individually through legitimate means.
Get a subscription link or a single-node link from your service provider. The free nodes on this site can be used to learn how to import nodes and test connectivity, but availability may change, so don’t rely on them as the sole connection for critical work. Subscription links often contain access credentials. Don’t share them in public group chats or show them in screenshots.
2. Import a subscription and connect
- Open Shadowrocket and go to the home screen, then tap “+” in the top-right corner. Menu labels may vary slightly between versions.
- To import a subscription, select “Subscribe” as the type, paste the full link into the URL field, add a descriptive remark, and save. If you have a single-node link, copy it and import it using the app’s prompts, or scan the node’s QR code.
- Return to the home screen and check that the node appears under the subscription group. If it doesn’t, make sure you copied the full link and try updating the subscription. Don’t mistake the subscription webpage address for the actual subscription link.
- Tap a node, then turn on the connection switch on the home screen. The first time you connect, the app will ask to add a VPN configuration. Confirm and authorize it using your device passcode or system authentication.
- Open a browser and visit the service you need to use, then test a regular website as well. Node latency tests can help narrow down your options, but the only reliable test is whether the service you need opens properly.
3. Choosing a routing mode
For everyday use, “Config” mode is generally the best choice. It uses the current rules to determine which connections go direct and which use a proxy; make sure the rules come from a trusted source. “Proxy” mode typically routes more traffic through the selected node. It can be useful for temporary comparisons and troubleshooting, though some system or app traffic may still be excluded. “Direct” mode accesses services without a proxy. Test your connection again after changing modes, and don’t assume that turning on the switch means every app uses the same egress route.
4. How team use affects account stability
Platforms may consider network egress, devices, login locations, and user activity when deciding whether to request verification. Having multiple people take turns using the same account or switching nodes across regions within a short period may lead to additional verification, but a single verification prompt isn’t enough to conclude that the proxy caused it.
Teams should keep a consistent mapping between members, devices, accounts, and their usual egress routes wherever possible. Label nodes by purpose and region, use a consistent set of trusted rules, and avoid frequent ad hoc switching by team members. For collaboration, use the platform’s member permissions where available rather than sharing passwords or verification codes. Nodes with the same name don’t necessarily have a fixed IP address. For critical work, confirm the egress characteristics with your service provider and follow the target platform’s rules.
5. Troubleshoot connection issues in order
First, turn off the proxy and check that your Wi-Fi or cellular connection is working. Then check whether the subscription has expired and whether the node is still available, and update the subscription. If the app shows that you’re connected but webpages won’t load, try another node and compare “Config” and “Proxy” modes. If the latter works but the former doesn’t, check the rules and DNS settings.
If the problem persists, temporarily disable other VPNs or network tools that might conflict, restart the client, and try again. When asking for help, include your system and client versions and an error message with sensitive details removed. Don’t publicly share subscription tokens, node passwords, or account login information.