This guide answers the beginner’s question, “How do I use Shadowrocket?” It covers installing the app on an iPhone, importing nodes, enabling rule-based routing, and why changes to a team’s exit IP may affect account logins. The goal is to get the connection working and make the settings easy to review—not to treat a VPN as a guarantee of account stability or exemption from verification.
1. Get the app and subscription ready
Shadowrocket is a proxy client for iOS. The app itself does not provide nodes. Before installing it, check the app name and developer information in the App Store. If it is unavailable in your store region, follow the store’s rules; do not install packages tied to shared accounts or configuration profiles from unknown sources.
You’ll also need a subscription link, node share link, or QR code from a trusted source. A subscription is a set of connection configurations and may contain access credentials, so don’t post it in public group chats. The free nodes on this site can be used for learning and temporary testing, but you’ll need to check whether they work and whether their exit IPs change.
2. Import a node and connect for the first time
- Open Shadowrocket and allow any necessary network permissions. Copy a node share link, return to the app, and follow the prompts to add it. You can also tap the add button and choose to import by scanning a QR code.
- For a subscription, select the subscription type on the add screen, paste the full link, and save it. Then update the subscription. The menu names may vary slightly between versions, so follow the current interface.
- Check that your node list contains entries, then select a node and test the connection. Treat the test results as a guide; latency alone cannot tell you whether every website is accessible.
- Set “Global Routing” to “Config” and use a rule configuration from a source you’ve verified. To troubleshoot initially, you can briefly switch to “Proxy” mode to see whether the issue is related to rule-based routing.
- Turn on the connection switch on the home screen. The first time you connect, follow the system prompt to allow the VPN configuration to be added, then open a browser and check the target website.
Seeing the VPN icon does not mean the target service is necessarily accessible. Check both whether the webpage loads and whether the selected node is active. If checking your exit IP, don’t enter business account credentials on an unfamiliar IP-checking website.
3. How team use affects account environment consistency
Account platforms may assess exit IP, region, device, browser state, and user activity together. Frequently switching countries or regions, or sharing one account among multiple people, may trigger additional verification, but not every login issue is caused by a proxy.
Teams should keep the environment used for each business account as consistent as possible: stick to the same devices and browser configurations, choose an exit region that meets business requirements, and avoid switching nodes arbitrarily during work. Use the platform’s member seats and access controls where available rather than collaborating by sharing passwords.
If you need a fixed exit, first confirm that the node service explicitly supports one. Nodes with the same name do not necessarily keep the same exit IP forever. Free or shared nodes should not be treated as a long-term fixed environment, and you should not switch nodes repeatedly in an attempt to bypass platform risk controls.
4. Troubleshoot connection failures in order
- Subscription won’t update: Check that the link is complete and hasn’t expired, and that your current network can access the subscription address. Avoid repeatedly importing duplicate entries.
- No websites load: First turn off the proxy to confirm your local network is working. Then check that the node is valid, and temporarily disable other VPN apps to rule out conflicts.
- Only some websites won’t load: Review the request log and matched rules. Briefly switch routing modes for comparison, then restore your usual routing settings after testing.
- Webpages load, but the account asks for verification: Check login alerts and any changes to devices or regions. Verify your account through the platform’s process, and don’t keep retrying with multiple exit IPs.
When troubleshooting, change only one setting at a time and record the node, routing mode, and error. Before reporting the issue to a colleague or support team, redact subscription addresses, passwords, and tokens, and comply with local laws and the relevant service terms.