This guide explains how to use Shadowrocket and how team members can reduce repeated account verification caused by changes in network environment. You’ll install the client, import a node or subscription, configure routing, and troubleshoot connection issues. First, keep in mind: a working proxy connection does not mean the account environment is stable. Your exit IP, device, login location, and platform rules can all affect verification.
1. Install the client and prepare your connection details
Shadowrocket is a proxy client for iPhone and iPad; it does not include usable proxy routes. Check the app name and developer information in the App Store. Availability and pricing depend on your region’s store. Don’t install configuration profiles from unknown sources or share your team’s Apple ID just to install the app.
After installation, get the subscription link, node link, or QR code provided by your service provider. Any one of these will work. Subscriptions are generally easier to manage centrally, while a single node is suitable for temporary testing. This site’s free nodes can be used to learn the import process, but they’re not recommended as a long-term, fixed exit for critical team accounts.
2. Import a subscription and connect for the first time
- Open Shadowrocket, tap “+” in the upper-right corner of the home screen, and select “Subscribe／Subscription” as the type. Paste the full subscription URL into the URL field, add a recognizable name, and save. Labels may differ slightly between versions.
- Return to the home screen and check whether your nodes appear. If not, find the subscription update option and refresh it manually. For a single-node link, copy it and import it using the app’s instructions; for a QR code, use the in-app scanner.
- Select a node, set “Global Routing” to “Config,” and confirm that the current configuration includes trusted routing rules. Global Routing determines how traffic is routed; it isn’t a speed-selection control. Don’t import rules from unknown sources.
- Turn on the connection switch on the home screen. The first time you connect, follow the iOS prompt to allow the app to add a VPN configuration, then complete device verification.
- Visit a website that requires a proxy and use a trusted IP lookup page to check your exit location. Latency tests are only a guide: a successful latency test doesn’t guarantee that a specific website will work.
3. Team use: keep the login environment predictable
Keep the exit location and device consistent for each business account, and avoid having multiple people log in from different countries or regions at the same time. Your team can record each account’s owner, usual device, node label, and permitted backup regions, but don’t store passwords or subscription keys in those records. Whether an exit IP stays the same depends on the service; nodes with the same name don’t necessarily have the same IP indefinitely.
We recommend that all team members use a verified configuration and notify one another before changing routes. If the platform supports member invitations or subaccounts, use its official collaboration features instead of sharing the main account. A proxy is no substitute for multi-factor authentication and cannot guarantee that the platform’s risk controls won’t be triggered.
4. Troubleshoot connection problems and repeated verification
- Subscription update fails: Check that the link is complete and hasn’t expired, then confirm that your current network can access the subscription URL. Don’t post a full link containing a token in a public group.
- Connected, but webpages won’t load: First turn off other VPN apps, then check that the node is working and the rules are matched correctly. If needed, test with another node for comparison.
- Only one website is having issues: Check the device’s date and time, the website’s status, and your routing rules. Don’t keep switching regions whenever a problem occurs.
- The account keeps asking for verification: Pause simultaneous logins, check whether the exit location or device has changed, and complete verification through the platform’s official process. Don’t keep retrying the password.
Change one setting at a time and record the result; this makes issues easier to diagnose than changing the node, rules, and network all at once. Once the connection is restored, check the exit location and target website again before resuming team operations.