This guide answers the beginner question “How do I use Shadowrocket?” It covers installing the app on an iPhone, importing a subscription, and testing the connection, then explains how teams can reduce account verification triggered by frequent changes in their exit IP. Shadowrocket is a proxy client and does not provide usable servers itself. Your connection experience depends on node quality, your local network, and your routing settings, and there is no guarantee that an account won’t trigger security checks.
1. What to prepare before installation
Search for Shadowrocket in the App Store and check the app name and developer information. Availability and pricing depend on what the App Store shows in your region. Don’t install modified apps from unknown sources or use a shared Apple ID provided by a stranger. For team use, each member should install the app through an authorized method.
Get a subscription link, single-node link, or QR code from your service provider. A subscription link is an access credential, so don’t post it in public group chats or include it in screenshots or support tickets. The free nodes on this site can be used to learn how to import nodes and test connectivity, but availability may change, so they shouldn’t be treated as a fixed exit IP for team operations.
2. Import a subscription and connect
- Open Shadowrocket and tap “+” in the upper-right corner of the home screen. To import a subscription, select Subscribe as the type, paste the full address, and save it. The wording may vary slightly by version.
- If you have a single-node link, copy it and import it as prompted by the app. To add a QR code, use the scan option. If the import fails, first check for missing characters, extra spaces, or an expired link.
- Return to the home screen, update the subscription, and expand the node list to select a node. A latency test can help you assess responsiveness, but it doesn’t guarantee that a website will work.
- Under “Global Routing” or a similar routing setting, choose “Config,” “Proxy,” or “Direct” as needed. Config mode is generally used for everyday traffic routing, but make sure trusted rules are in place. For troubleshooting, temporarily switch to Proxy mode and compare the results.
- Turn on the connection switch on the home screen. The first time you connect, follow the iOS prompt to allow the VPN configuration and complete system verification. Then open the target website and check that it loads and uses the expected exit IP.
Seeing the VPN icon doesn’t mean traffic to your target website is going through the proxy. In Config mode, different websites may use either a direct connection or the proxy, so you still need to verify the result.
3. How team use relates to account environment stability
Teams should standardize their procedures rather than share personal accounts or force every device to use the same exit IP. For operations that require a stable environment, record the usual region, node name, and routing mode, and avoid switching an account between regions repeatedly in a short period. For collaboration, prioritize the platform’s member invitations, subaccounts, and permission management features.
A stable exit IP is only one part of an account’s environment. Devices, browser sign-in status, multi-factor authentication, and user behavior can also affect security checks. Don’t treat a fixed node as a guarantee against account restrictions, and don’t disable account security features just to maintain a connection.
4. Troubleshoot connection failures in order
- Turn off the proxy and test a regular webpage to confirm that your Wi-Fi or cellular connection is working.
- Check whether the subscription has expired and whether it updates successfully, then try another node for comparison. Avoid repeatedly reinstalling the app.
- Temporarily switch routing modes. If Proxy mode works but Config mode doesn’t, check whether the rules are routing the target domain directly.
- Check for conflicts with other VPN or network-filtering apps, and make sure the system date and time are correct.
- If the connection still doesn’t work, note the error, network type, and time it occurred, then report the issue to your service provider. Redact subscription addresses, passwords, and tokens from logs.
During troubleshooting, change only one variable at a time. Once the connection is restored, return to the node and mode agreed on by your team. Before using the service, check local laws and the target platform’s rules, and avoid repeatedly testing unknown free nodes with sensitive business accounts.