How do you use Shadowrocket? This guide walks you through installing it on an iPhone or iPad, importing nodes, connecting, and troubleshooting. It also explains how proxy egress relates to account environment stability when a team shares a business account. The goal is to make configurations reusable and problems easier to diagnose—not to treat “connected to VPN” as a guarantee of account security.
1. What to prepare before installing
Shadowrocket is a proxy client and does not include usable nodes. Get it from its official App Store page; availability and pricing are as shown in the store. Don’t install configuration profiles from unknown sources or purported cracked versions. You’ll also need a node link or subscription URL from a trusted source, and should confirm that the provider supports Shadowrocket.
Subscription URLs usually contain access credentials, so treat them like passwords. Don’t post them in public group chats or support tickets, or include them in screenshots. For team use, designate someone to maintain the configuration and share it only with people who are authorized to use it.
2. Import a subscription and connect
- Open Shadowrocket and tap “+” in the upper-right corner of the home screen. To add a subscription, choose a subscription type such as “Subscribe,” paste the full subscription URL into the URL field, add a descriptive remark, and save. The labels may vary slightly between versions.
- Return to the home screen and update the subscription. Wait for the node list to appear. If you have a single node link, copy it and import it as prompted by the app; for a QR code, use the scan option. Don’t paste the subscription URL into the server address field.
- Select a node. Under “Global Routing,” start with “Config” mode and make sure the rules come from a trusted source. Rules determine which requests use the proxy: “Direct” bypasses the node, while “Proxy” routes traffic through the selected proxy.
- Turn on the connection switch on the home screen. The first time you connect, follow the iOS prompt to allow the VPN configuration to be added. When the VPN indicator appears, visit your target website to test the connection. If needed, check the request log to confirm whether the request followed the expected routing rule.
A successful node latency test doesn’t guarantee that the target website will be accessible. Also check that pages load, sign-in works, and the target service shows the expected login location. The free nodes offered on this site can be used for learning and temporary testing, but shouldn’t be assumed to provide a fixed exit location over the long term or to be suitable for sensitive business use.
3. Team use and account environment stability
Signing in to the same business account from different countries or regions within a short period may trigger a new-location verification from the platform. However, account risk checks can also depend on the device, cookies, login frequency, and user activity. A fixed node name doesn’t mean the exit IP is fixed: providers may change routes or exit IPs, so rely on actual test results.
Teams should agree on the usual login region, designate a configuration owner, and establish a process for switching nodes. Check the exit region before important operations, and avoid having multiple people sign in at the same time from networks with significantly different locations. Don’t switch nodes frequently just to get lower latency. If you need to change routes, save your work first, then check the new connection. Use the platform’s member invitations, role-based permissions, and two-factor authentication where available; don’t use a shared password as a substitute for proper access management.
4. Troubleshoot connection issues in order
- First turn off the proxy and test your regular internet connection. If that doesn’t work, switch between Wi-Fi and cellular data.
- Check whether the subscription has expired and whether the URL is complete, then update it manually. If the list is empty, contact the provider to confirm the format and authorization.
- Make sure a node is selected and the connection switch is on. Check whether another VPN app is causing a conflict.
- If only certain websites fail, check the routing rules and request log. If everything fails, try another node. Don’t disable certificate verification without a good reason.
If you still can’t identify the problem, note the client version, error message, and time it occurred. Hide any subscription credentials before asking for help. Teams should also keep a record of configuration changes so they can be rolled back if needed.