This guide covers the basics of using Shadowrocket: installing it on an iPhone, importing a node, and enabling the proxy. It also explains how teams can reduce repeated verification caused by frequent changes in their network exit. Shadowrocket is a proxy client and does not provide usable connections by itself. Account stability also depends on the node’s exit, the device, login habits, and platform rules.
1. What to prepare before installing
Search for Shadowrocket in the App Store and check the app name and developer information. Availability depends on what your local store currently offers. Don’t install configuration profiles from unknown sources or use an Apple ID shared by someone you don’t know. Get a subscription link, node QR code, or individual node link from a trusted source, and confirm that the service supports Shadowrocket.
Treat subscription links as sensitive credentials, since they may contain access tokens. Team members should not post them in public groups, include them in support-ticket screenshots, or store them in shared documents. Before allowing multiple people to use a subscription, check the provider’s device limit and sharing rules.
2. Import a node and connect
- Open Shadowrocket and tap “+” in the top-right corner of the home screen. For a subscription, select “Subscribe” in the type menu, paste the link, and save it. Menu names may vary slightly by version.
- For a QR code, scan it using the app’s scanner. For an individual node link, copy it and follow the app’s prompts to import it. After importing, check that the node name, protocol, and server information are all present.
- Return to the home screen, expand the subscription, and select a node. Test the connection first. The test result is only a guide, so you should still verify it by visiting the actual website you need.
- Choose a mode under “Global Routing” based on your needs. For everyday use, “Config” is a suitable choice, though routing depends on the current rules. For temporary troubleshooting, switch to “Proxy,” then switch back when you’re done testing.
- Turn on the connection switch on the home screen. When prompted, allow the system to add a VPN configuration. Then open a browser and visit the target website to confirm the connection works.
The VPN icon does not guarantee that a particular service is accessible. If the subscription is empty, first check whether the link has expired or contains extra spaces, then try updating the subscription. Avoid repeatedly deleting and reinstalling the app.
3. How teams can keep account environments stable
Teams can set a few simple guidelines: decide who is responsible for updating the subscription, which region each member will typically use, and how to switch connections if something goes wrong. For important accounts, try to use the usual device and a relatively consistent exit region. Avoid logging in from several regions in a short period, and don’t have multiple people operate the same account at the same time.
A consistent node name does not mean the exit IP is fixed. The exit can change even on the same node due to service adjustments or load balancing. You can check the current exit IP and region the first time you connect and whenever an issue occurs. Record only the information you need, and don’t save passwords, verification codes, or complete subscription links. A proxy cannot guarantee that you won’t be asked to verify your account, and it is no substitute for the platform’s team-member permissions.
4. What order should you follow when troubleshooting a failed connection?
- First turn off the proxy and check whether Wi-Fi or cellular data can access the internet. If the underlying network is down, fix that first.
- Update the subscription and check that the node is still valid. Test another node for comparison, and avoid switching rapidly between nodes and repeatedly logging in.
- If only some websites won’t open, check the routing rules. Temporarily use “Proxy” mode to see whether the issue is caused by a rule match.
- Pause any other VPN or network-filtering apps and try again. If the problem persists, send the person maintaining the service the error message, time, and client version. Hide sensitive information before sharing screenshots.
The free nodes on this site can be used to learn how to import nodes and test connectivity, but availability and exit locations may change. If your work requires account continuity, first check that the connection meets your needs, and follow local laws and the rules of the platform you’re using.