This guide answers the beginner’s question, “How do I use Shadowrocket?” It covers installing the app on an iPhone, importing a subscription, and testing the connection, as well as how teams can reduce account verification caused by frequent changes in their outbound IP address. Shadowrocket is a proxy client and does not provide nodes itself. A stable account environment involves more than simply connecting to a VPN; it also depends on the device, login location, and platform rules.
1. Before you install: treat the client and subscription separately
Search for Shadowrocket in the App Store and check the app name and developer information before installing. Availability for purchase depends on your region’s store. Don’t install configuration profiles from unknown sources or purported “shared-account editions.” Prepare a subscription link or node QR code from a trusted source, and confirm that the service supports Shadowrocket.
Teams should assign each member their own subscription rather than casually sharing an Apple ID or business account. A subscription link is an access credential, so don’t post it in public groups or include it in screenshots or support tickets. This site’s free nodes can be used for learning and temporary testing, but they are not suitable for ensuring a fixed outbound IP for critical business use.
2. Import a subscription and connect for the first time
- Open Shadowrocket and tap “+” in the top-right corner of the home screen. Under Type, select “Subscribe” (the label may vary by version), paste the full subscription URL into the URL field, enter a recognizable name, and save.
- Return to the home screen and update the subscription. Confirm that the node list appears. If you have a link or QR code for a single node, use the clipboard import or QR scanning feature; don’t mistake a node link for a subscription URL.
- Select a node and choose a routing mode such as “Config” under “Global Routing,” as needed. Check whether the current rules cover the target website. For an initial test, you can temporarily use “Proxy” mode to help diagnose the connection, then switch back to an appropriate split-routing setup.
- Turn on the connection switch on the home screen. The first time you connect, follow the system prompt to allow a VPN configuration, then confirm with your device passcode or biometric authentication.
- Open a browser and visit the target service. Check the client’s connection log to confirm that traffic is routed through the proxy. The VPN icon only indicates that the tunnel is active; it does not guarantee that the target website is accessible.
3. How team use affects account stability
Platforms may assess risk based on factors including the outbound IP address, device, cookies, login times, and user activity. Multiple people taking turns logging in, automatic node switching, or accessing an account from different regions within a short period may trigger verification. A fixed outbound IP can reduce one of these variables, but it cannot guarantee that risk controls won’t be triggered.
Teams should keep a record mapping each member to their device, business account, and usual outbound region. Where possible, use the same device and usual region for each account, and don’t switch between multiple countries after a single failed attempt. The region shown in a node’s name may not match its actual outbound location; verify it using a trusted IP lookup page. For enterprise systems, prioritize platform-supported member permissions, two-factor authentication, and organizational access options instead of sharing passwords.
4. Troubleshoot connection failures in order
- None of the nodes work: First turn off the proxy to confirm that your local network is working. Then check whether the subscription has expired, the URL is complete, and your system clock is set to sync automatically.
- The subscription won’t update: Check for spaces or a truncated URL, and review the provider’s announcements. Don’t send the full link to strangers to check for you.
- You’re connected but webpages won’t load: Check the selected node, routing mode, and connection log. Temporarily switch routing modes to compare, and make sure no other VPN is running at the same time.
- One account keeps triggering verification: Stop retrying repeatedly, check whether the outbound IP has changed, and follow the platform’s verification process. Don’t try to bypass restrictions by repeatedly switching nodes.
Before making changes, note your original settings and change only one thing at a time. For teams, keeping a shared record of incident times, client versions, and redacted logs is more useful for troubleshooting than reinstalling the app without a plan. Always comply with local laws and the target service’s rules.