This article answers the beginner question “How do I use Shadowrocket?” It covers installing the app on an iPhone, importing a subscription, and connecting. It also explains how teams can reduce login checks caused by frequent changes to their network egress. Shadowrocket is a proxy client, not a node service; simply turning on a proxy is not enough to ensure a stable account environment.
1. Prepare the app and nodes
Search for Shadowrocket in the App Store and check that the developer is Shadow Launch Technology Limited. Availability and pricing depend on your local store listing. Do not install modified versions from unknown sources, and avoid sharing an unfamiliar Apple ID across your team.
You’ll also need a subscription link, node link, or QR code from your service provider. Make sure it supports Shadowrocket. The free nodes on this site can be used for learning and connectivity tests, but availability may change, so don’t rely entirely on public free nodes for important business needs.
2. Import a subscription and connect for the first time
- Open Shadowrocket and tap “+” in the upper-right corner of the home screen. Under Type, select “Subscribe,” paste the full subscription URL into the URL field, add a recognizable remark, and save. Names may vary slightly between versions.
- Return to the home screen and update the subscription. Wait for the nodes to appear. If you have only a single node link, copy it and import it as prompted by the app. To add a QR code, use the scan option.
- Select a node and run the connectivity or latency test provided by the app. Treat the results as a guide only; they don’t guarantee that every website will work.
- Set “Global Routing” to “Config” to route traffic according to the rules in your configuration. If you haven’t set up rules yet, you can temporarily use “Proxy” mode to check whether the target website opens, then adjust your settings afterward.
- Turn on the connection switch on the home screen. The first time you connect, follow the iOS prompt to add a VPN configuration and complete system verification. Then visit the target website to check that the connection is working.
Your subscription URL is effectively an access credential. Don’t include it in public documents, screenshots, or group announcements. Deleting the local subscription doesn’t revoke the link. If it’s exposed, contact the provider to have it reset.
3. Team use and account environment stability
Websites may assess risk based on a combination of egress IP, location, device, browser data, and login activity. Shadowrocket can affect some network routes, but it cannot guarantee that an account won’t be prompted for verification. Sharing the same egress point also doesn’t mean users have the same or a trusted login environment.
Teams can keep a simple record of each member, device, business account, and usual egress region. Use consistent devices and regions where possible, and avoid switching nodes repeatedly while logging in or working. If you need to switch, finish the current task first, then check the egress point again. Use the platform’s approved member invitations and permission controls. Don’t share a main account password among multiple people, and enable two-factor authentication.
4. Troubleshoot connection issues in order
- First, turn off the proxy and test a regular webpage to rule out Wi-Fi, mobile network, or billing issues.
- If no nodes appear, check that the subscription URL was copied in full and hasn’t expired, then update it manually. Changing the remark alone won’t help.
- If the app shows that you’re connected but websites won’t open, try another node and check whether the routing rules are sending the target website through a direct connection.
- If only some domains fail, check your DNS and routing rules. Restore a trusted configuration first, and don’t blindly add more network configuration profiles.
- If the problem persists, temporarily turn off other VPNs or network filtering tools and try again to rule out configuration conflicts.
An account verification prompt doesn’t necessarily mean the node is faulty. Follow the platform’s instructions to complete verification and check your login history. Avoid repeatedly switching regions to “fix” your environment. For teams, a consistent operating procedure is usually more valuable than minimizing latency for a single session.