This guide explains how to use Shadowrocket and how team members can reduce changes to their account environment caused by switching nodes at random or using inconsistent rules. You’ll learn how to install the client on an iPhone, import a subscription, configure traffic routing, and troubleshoot connection issues in order. First, keep in mind: a working VPN connection does not mean your account environment is stable. Platforms may also assess risk based on your device, login location, and activity.
1. Prepare the client and nodes
Shadowrocket is a proxy client for iOS and does not include any working servers. Get the official app from the App Store; check the store listing for availability and pricing. Don’t install configuration profiles from unknown sources or use shared Apple accounts provided by strangers.
Get a subscription link from a trusted source, or a link for a single node in a format supported by the client, such as some VLESS, VMess, or Trojan configurations. Teams should confirm the subscription’s permitted use and device limits. Free nodes provided by this site can be used for connectivity tests, but their availability and exit locations may change, so don’t assume they’re suitable as a fixed long-term exit.
2. Import a subscription and connect
- Open Shadowrocket, tap “+” in the upper-right corner of the home screen, and select “Subscribe.” The label may vary slightly between versions.
- Paste the subscription URL into the URL field, add a descriptive note, and save. Return to the home screen and update the subscription to confirm that the nodes appear in the list. If you have a link for a single node, copy it and import it using the prompts in the app.
- Select a node and run a connectivity test. Treat the results as a guide, and also open the target website to confirm that it works.
- Go to “Global Routing.” For everyday browsing, “Config” mode is generally suitable; make sure you have trusted routing rules in place. Without rules, don’t assume the app will route traffic correctly by default.
- Turn on the connection switch on the home screen. The first time you connect, follow the system prompt to allow the VPN configuration to be added. Once the VPN status appears, visit the websites that require a proxy.
Subscription links usually contain access credentials. Don’t share them in public group chats, support ticket screenshots, or online conversion sites. For team distribution, use separate authorizations provided by the service whenever possible, and revoke a person’s access promptly when they leave.
3. How teams can reduce changes to the account environment
Keep a record of each member’s device, node label, exit region, and rules version, and coordinate updates rather than having everyone try nodes at random. For important business accounts, try to keep the device and usual network path consistent. Before switching routes, finish the current task to avoid changing exit locations in the middle of a login or submission.
The same node name does not guarantee a fixed exit IP address. The service provider may change the route. After connecting, check the current public exit IP and confirm that the target website is actually using the proxy. Before enabling automatic selection or failover, check whether it can switch regions. For team collaboration, use the platform’s member and permission features rather than sharing login credentials.
4. Troubleshoot connection failures in this order
- No nodes appear in the list: Check that the subscription URL is complete and hasn’t expired, then try updating it. Don’t post subscription contents on public forums.
- No websites load: Turn off the proxy first to check your local network, then check the node status, device time, and subscription validity.
- Only some websites fail: Check whether the routing rules send the target domain through a direct connection. If needed, briefly switch proxy modes for comparison, then restore the original settings.
- Websites load, but repeatedly ask you to verify your identity: Stop switching nodes repeatedly and check the exit region, device login history, and any security alerts from the platform.
Don’t assume that “switching to another node” will fix every problem. Change only one variable at a time and record the results before and after each change. If your account displays a security alert, verify your identity through the platform’s process instead of continuing to change exit locations and attempt to log in.