This guide addresses the practical question “How do I use Shadowrocket?” It covers adding nodes on iPhone/iPad, importing subscriptions, enabling the proxy, and understanding the relationship between IP, DNS, and your browser environment to help you avoid common issues such as “connected but can’t open anything” or “IP changed but things still aren’t working.”
1. Shadowrocket basics
Shadowrocket is commonly known among Chinese-speaking users as “Little Rocket.” It is mainly used to import proxy nodes such as V2Ray, VLESS, Trojan, and Shadowsocks on iOS devices. Before you begin, make sure you have a working node or subscription link. This site also collects free nodes for testing, but free nodes can be unreliable, so it’s a good idea to keep a few backups.
- Open Shadowrocket and go to the home screen, then tap “+” in the upper-right corner.
- For a single node, select the corresponding type and enter the server, port, password, UUID, encryption method, and other details.
- For a subscription link, tap “Config” or “Subscription,” paste in the subscription URL, save it, and update it.
- Return to the home screen, select a node, and turn on the switch at the top.
- The first time you use it, iOS will prompt you to add a VPN configuration. Tap Allow and enter your passcode.
Once connected, a VPN icon will usually appear in the status bar. We recommend opening a browser and visiting an IP lookup site first to confirm that your outgoing IP has changed. If it hasn’t, the node may be unavailable, the rules may not be taking effect, or the app you’re using may not be routed through the proxy.
2. How IP, DNS, and your browser environment are related
Many users assume that turning on Shadowrocket means their entire environment has changed, but that’s not quite right. Your IP represents your network’s exit point and determines which region websites see you as connecting from. DNS translates domain names into IP addresses; if your DNS leaks, you may experience slow access, DNS poisoning, or incorrect region detection. Your browser environment includes information such as language, time zone, cache, cookies, and WebRTC.
Put simply, Shadowrocket mainly changes your proxy exit, but it doesn’t automatically clear saved login sessions, language preferences, or browsing cookies. For example, if you switch to a US node while your browser language is still Chinese and your account’s region history is still in China, some websites may continue to flag your activity. This doesn’t mean Shadowrocket isn’t working; it means your network and browser environments aren’t aligned.
3. Recommended rules and DNS settings
Most users don’t need to start by changing complex rules. Try a common split-tunneling mode under “Config/Rules”: connect directly to domestic websites and route international websites through the proxy. This helps keep domestic apps such as WeChat, banking apps, and maps from slowing down, while YouTube, Google, X, and similar services use the node.
- If you just want to access international websites, start with “Rule Mode.”
- If a particular website won’t open, temporarily switch to “Global Mode” to test.
- You can use the DNS settings included in the config. If you encounter DNS poisoning, try switching to a remote DNS server.
- Don’t run multiple VPN apps at the same time, as they may conflict over routing.
If you often find that you’re connected but webpages won’t load, update your subscription in Shadowrocket, switch nodes, and restart Safari or Chrome. In some cases, you may also need to close and reopen the browser or clear cookies for the affected website.
4. Troubleshooting connection failures
If Shadowrocket won’t connect, troubleshoot in order instead of changing settings at random. First, check whether the node has expired or the subscription needs updating. Second, confirm that your phone’s internet connection is working by turning off Shadowrocket and visiting a regular website. Third, try another node to determine whether the problem is with a single node or the configuration. Fourth, check that your device’s time is correct; an incorrect time can cause TLS handshake failures.
Also note that all node protocol settings must match exactly. For example, a single incorrect VLESS UUID, transport method, TLS setting, or Reality parameter can cause the connection to fail. If you imported the node from a subscription, you usually don’t need to change its details manually; manual edits can easily introduce errors.
Finally, if your IP has changed but a website still reports that you’re in the wrong region, try a private browsing window, clear your cookies, check for WebRTC leaks, or switch to another node in the same region. Consistent use depends on keeping your node, DNS, and browser environment aligned—not just checking whether the VPN icon is lit.