This guide answers the beginner question “How do I use Shadowrocket?” It walks you through installing the app on iPhone, importing nodes or subscriptions, choosing a proxy mode, and troubleshooting connection issues. It also explains how teams can reduce account verification caused by frequent changes in their exit IP. Shadowrocket is a proxy client and does not include working routes; connection quality also depends on the node, your current network, and the server’s status.
1. Before you install: manage the client and subscription separately
Search for Shadowrocket in the App Store and check that the developer is Shadow Launch Technology Limited. Availability for purchase depends on what’s shown in your regional store. Don’t install modified versions from unknown sources, and don’t sign someone else’s Apple account into your device’s iCloud just to install the app.
Get the subscription URL, node link, or QR code from your service provider. Subscription URLs usually contain access credentials, so protect them like passwords. Team members should use subscriptions they’re individually authorized to access. Don’t post links in public group chats or support tickets, or include them in screenshots. If you use free nodes from this site, check that they’re valid and review their usage limits first; don’t rely on them for sensitive work.
2. Import nodes and connect for the first time
- Open Shadowrocket and go to the home screen, then tap “+” in the upper-right corner. To import a subscription, choose “Subscribe” as the type, paste the subscription URL, and save it. Menu labels may vary by version.
- If you have a link for a single node, copy it and follow the client’s prompt to import it from the clipboard. To import a QR code, use the in-app scanner. After importing, check that the server, port, and protocol are all displayed correctly.
- Update the subscription and confirm that the nodes appear in the list. Select a node and run a connectivity test if you like. Test results are only a guide and don’t guarantee that the node will work for your actual needs.
- The first time you turn on the connection switch on the home screen, allow iOS to add a VPN configuration and verify your device passcode when prompted. Then use a browser to visit a site you need and check that it loads correctly.
The VPN icon doesn’t mean the node is working. If the icon appears but webpages won’t load, check the node’s validity period, subscription status, and local network.
3. For teams: choosing rules and account exit IPs
For everyday use, “Configuration” or rule mode is usually the best choice, allowing traffic to be routed according to the selected configuration. For temporary troubleshooting, switch to “Proxy” mode for comparison, then switch back afterward. Rules come from the current configuration; turning them on doesn’t guarantee that they’ll automatically work with every website. Don’t import a remote configuration unless you understand it.
Teams should agree on which services use a proxy, who maintains the subscription, and when nodes should be changed. Try to keep the exit region relatively consistent for each business account and avoid having multiple people sign in from different regions at the same time. Don’t switch nodes repeatedly just to get a lower test latency.
A consistent exit IP doesn’t guarantee account security: platforms may also check the device, login frequency, and user behavior. Prefer the platform’s built-in member permissions, two-factor authentication, and official collaboration features. Don’t use shared accounts as a substitute for access controls.
4. Troubleshoot connection failures in this order
- Turn off the proxy and confirm that your Wi-Fi or mobile network can access the internet. Then switch networks and try again.
- Update the subscription, check whether it has expired or has a traffic limit, and see whether the node is inactive. Then test a different authorized node.
- If only some websites are affected, compare rule mode with proxy mode and check for routing or DNS issues. Don’t change every setting without a clear reason.
- Temporarily turn off other VPNs or network-filtering tools and try again. If the problem persists, record the error and contact your provider. Be sure to hide subscription URLs and credentials in any screenshots.
After troubleshooting, restore your usual rules and share any changes with the team. Follow local laws and the terms of service for the services you use. A successful client connection does not guarantee that your account environment is secure.