This guide answers the beginner question, “How do I use Shadowrocket?” It covers installing the app on an iPhone, importing nodes, and connecting, as well as ways teams can reduce login verification caused by frequent changes in their exit IP. Shadowrocket is a proxy client and does not include usable proxy servers. Whether it connects depends on the nodes, subscription, and current network, and it cannot guarantee that an account will not trigger security checks.
1. What to prepare before installing
Search for Shadowrocket in the App Store on your iPhone or iPad. Check the app name and developer information before installing. Availability and purchase requirements depend on what is shown in your local store. Do not install configuration profiles from unknown sources or use an Apple ID shared by someone you do not know.
Get the subscription URL, node link, or QR code from your service provider. Subscription URLs usually contain access credentials, so do not post them in public group chats, screenshots, or shared documents. This site’s free nodes can be used for initial testing, but availability may change, so do not rely on them long-term for critical business needs.
2. Import nodes and connect for the first time
- Open Shadowrocket and tap “+” in the upper-right corner. To import a subscription, select “Subscribe” in the type menu, paste the subscription URL, and save it. The wording may vary slightly between versions.
- If you have a link for a single node, copy it, return to the app, and follow the prompts to add it. You can also use the in-app scanner to import a QR code. After importing, check that the server and protocol are displayed correctly.
- After saving the subscription, use the update option in the list to fetch its contents. If parsing fails, check for spaces or line breaks introduced when copying, or confirm that the link has not expired.
- On the home screen, select a node and set “Global Routing” to “Config” to route traffic according to the rules. Turn on the connection switch at the top. The first time you connect, follow the system prompt to allow a VPN configuration to be added, then complete local authentication.
- Visit the website you actually need to use and check that it connects. A latency test is only a rough guide: a response from the test does not guarantee that the target website will work.
“Proxy” mode usually sends more traffic through the selected exit, while “Direct” mode bypasses the proxy. When troubleshooting routing issues, you can briefly switch to “Proxy” for comparison, then restore the appropriate rules to avoid routing unrelated traffic through the proxy.
3. How this relates to a stable environment for team accounts
When a team shares a business account, simultaneous logins and switching exit regions can lead to additional security checks. Shadowrocket can only affect your network exit; it cannot keep the entire account environment consistent. The device, browser state, login timing, and platform rules also matter.
- Use the platform’s official member invitations, subaccounts, and access controls whenever possible, and avoid sharing the main account password.
- Keep a node that has been tested and verified for everyday work devices. Avoid randomly changing regions before each login; switch deliberately if a connection fails.
- Record who is responsible for each device, the usual exit region, and when it changes. Do not record subscription keys, passwords, or verification codes.
- Enable two-factor authentication. If you receive an unusual activity alert, check the login history first rather than repeatedly switching nodes in an attempt to “bypass security checks.”
4. Troubleshooting connection failures
First, turn off the proxy and check that your Wi-Fi or cellular connection can access the internet. Then update the subscription and check whether it has expired or been disabled. Next, try another node and make sure no other VPN is connected at the same time. If the connection works but some websites do not, compare “Config” and “Proxy” modes to see whether the issue is related to the rules. Do not import unfamiliar configurations or install certificates without a good reason.
If the problem persists, check the app logs for timeouts, parsing failures, or authentication errors. When contacting your provider, share only the information needed and redact any credentials. Change one variable at a time to make it easier to tell whether the problem is with your local network, the node, or the routing configuration. You should also follow local laws and the rules of the platform you are accessing.