This guide explains how to use Shadowrocket, how team members can import subscriptions consistently, check their proxy exit, and troubleshoot connection failures. Shadowrocket is a proxy client for iOS and does not include usable nodes. Whether an account environment remains stable also depends on node egress, network changes, and the platform’s own security rules; simply enabling a proxy is no guarantee.
1. Before you install: You need both the client and a node
Search for Shadowrocket in the App Store and verify the app name and developer information. Get it through an official channel; availability depends on what your regional store actually offers. Don’t install configuration profiles from unknown sources or use shared Apple IDs from untrusted sources. Get a subscription URL or node link from your provider, and check its validity period, device limits, and supported protocols.
Teams should standardize procedures, not share all credentials. Subscription links may contain access tokens, which others could use if exposed. Don’t post them in public groups or include them in screenshots. Whenever possible, assign access to individual team members and follow the provider’s usage restrictions.
2. Import a subscription and connect for the first time
- Copy the complete subscription URL, open Shadowrocket, and tap “+” in the upper-right corner of the home screen.
- Select “Subscribe” under Type, paste the URL into the URL field, and add a helpful remark before saving. Labels may vary slightly between versions.
- Return to the home screen and wait for the node list to load. If no nodes appear, refresh using the subscription update option and check that you copied the full URL.
- Select a node and set “Global Routing” to the mode that suits your task: Configuration routes traffic according to rules, Proxy routes traffic through the proxy for a temporary check, and Direct bypasses the proxy. Configuration mode depends on the rules actually loaded.
- Turn on the connection switch on the home screen. The first time you connect, follow the system prompt to add a VPN configuration, then confirm with Face ID, Touch ID, or your device passcode.
- Open the website you need to access, then use a trusted IP lookup site to check the exit region. After testing, switch back to your usual routing mode.
Turning on the connection switch does not mean all apps use the proxy. Routing rules may send some traffic directly, and certain apps may handle network traffic differently. Check the target website and connection logs to confirm.
3. How team use relates to account environment stability
When multiple people use the same business service, frequently switching nodes or exit regions may trigger additional verification on some platforms—but a fixed exit is no guarantee that verification won’t occur. Even if a shared node keeps the same name, its actual exit may change, so a fixed node name does not mean a fixed exit IP.
Teams should agree on commonly used node regions, routing modes, and how to report problems. Check the exit before signing in as usual, and avoid switching repeatedly during a single task. Each member should use their own account and collaboration permissions allowed by the platform, and enable two-factor authentication. Don’t use a proxy to circumvent platform restrictions. Free nodes can be used for basic connectivity tests, but should not be relied on to keep critical business operations stable.
4. Troubleshoot connection failures in this order
- First, turn off the proxy and test a regular website to confirm that Wi-Fi or cellular data is working.
- Update the subscription and check whether it has expired, been disabled, or reached its device limit. If importing fails, obtain the original link again.
- Try another node. A successful latency test does not necessarily mean the target website is accessible.
- Temporarily switch to Proxy mode for comparison. If the site opens, check the routing rules. Restore your previous settings after testing.
- Check whether another VPN is enabled at the same time. If the issue persists, restart the client and note the error, network type, and time it occurred.
When reporting an issue to an administrator, provide the client version, node remark, and error details with sensitive information removed. Don’t send the full subscription URL, account password, or verification code.