This guide answers the beginner’s question, “How do I use Shadowrocket?” It covers installing the app on iPhone, importing nodes and subscriptions, testing the connection, and troubleshooting common issues. It also explains how teams can reduce the impact of frequent network changes on account environments. Shadowrocket is a proxy client, not a node service, and it cannot guarantee that business accounts will avoid security checks.
1. Prepare the app and subscription
Search for Shadowrocket in the App Store and check the name and developer information before installing. Availability depends on what your local store offers. Don’t install configuration profiles from unknown sources or supposed “free cracked versions.” Ask your service provider or team administrator for a node link, subscription URL, or QR code, and confirm that it works with Shadowrocket.
Subscription URLs usually contain access credentials, so treat them like passwords. Don’t share them in public group chats or screenshots. Teams should give each member their own subscription access. Avoid sharing Apple accounts, and don’t share business account passwords casually.
2. Import nodes and connect
- Open Shadowrocket and tap “+” in the upper-right corner of the home screen. If you have a subscription URL, select “Subscribe” in the type menu, paste the URL, add a descriptive note, and save. Labels may vary slightly between versions.
- If you have a link for a single node, copy it and return to the app to import it as prompted. To use a QR code, tap the scan option on the home screen. After importing, check that the node names appear. If you see a subscription group but no nodes, try updating the subscription first.
- Select a node from the list. You can run a connectivity or latency test to start with, but treat the results as a guide—they don’t guarantee that a particular website will work.
- Under “Global Routing,” choose a mode that suits your needs. “Config” is usually best for everyday use, as it routes traffic according to the configuration file. “Proxy” can help with temporary troubleshooting, but it’s not recommended for long-term use without a clear reason.
- Turn on the connection switch on the home screen. The first time you connect, allow the app to add a VPN configuration and complete any verification required by iOS. Then visit a website you normally use and check that both the page and its features work as expected.
The VPN icon doesn’t necessarily mean the proxy is working. A node may be down, a rule may not match, or the destination website may restrict access—any of these can leave you “connected” but unable to open a site.
3. Team use and account environment stability
An account environment depends on more than the exit IP address. It can also include the device, browser, login location, and usage patterns. Teams can standardize client instructions, configuration sources, and update procedures without requiring everyone to use the same exit point. For business accounts that need persistent sessions, try to keep the device and exit region consistent, and avoid switching between regions repeatedly in a short period.
A stable connection is no substitute for platform compliance or account security measures. Enable two-factor authentication and use the platform’s built-in team member permissions. If you see an unusual login alert, check the activity history first rather than repeatedly switching nodes to try to bypass verification.
4. Troubleshoot connection failures in order
- First, turn off the proxy and check that your Wi-Fi or cellular connection can access the internet normally.
- Update the subscription, check whether it has expired and whether the URL is complete, then test another node.
- If only one website won’t open, temporarily switch to “Proxy” mode and test again. If that fixes the issue, check the routing rules. After testing, switch back to your original mode.
- If all apps are affected, check whether another VPN is running at the same time. If necessary, disconnect the other VPN, reconnect, and review the client logs.
When contacting your administrator, provide your operating system and client versions, when the issue occurred, which network you were using, and a redacted error message. Don’t send the full subscription URL. The free nodes on this site can be used to learn how to import nodes and run basic tests. Availability may change, so don’t rely on them to guarantee uninterrupted team operations.