This guide addresses the practical question “How do I use Shadowrocket?” From importing nodes after installation and testing the connection to understanding how IP, DNS, and your browser environment are related, it will help you use a proxy on your iPhone or iPad more reliably.
1. Basic steps for using Shadowrocket
Shadowrocket is commonly called “Little Rocket” by Chinese-speaking users and is mainly used to configure proxy nodes on iOS devices. It is not itself a node provider, so whether you can connect depends on the availability of the nodes or subscription you import. This site compiles information about some free nodes, and you can also use a subscription link you already have.
- Open Shadowrocket, go to the home screen, and tap “+” in the top-right corner.
- If you have a subscription link, select Subscribe as the “Type,” or paste the subscription URL directly. Save it, then update it.
- For a single node, select a type such as Vmess, VLESS, Trojan, or Shadowsocks, then enter details such as the server, port, UUID, or password.
- Return to the home screen, select a node, and tap the switch to enable the proxy.
- The first time you enable it, the system will prompt you to add a VPN configuration. Tap Allow and enter your device passcode.
After importing a node, it’s a good idea to tap it to test its latency. Low latency doesn’t necessarily mean the node will work, but a timeout usually indicates that the node is unreachable, the subscription has expired, or your network environment does not support the connection.
2. How IP, DNS, and your browser environment are related
Many users assume that once Little Rocket connects, their “environment is fine.” In fact, you also need to check whether your IP, DNS, and browser fingerprint are consistent. Your IP is the outgoing address websites see; DNS handles domain name lookups; and your browser environment includes information such as language, time zone, WebRTC, and cache.
Normally, when a global proxy is enabled, the IP shown when you visit a website should be the node’s exit IP. If DNS requests still go through your local ISP, a “DNS leak” may occur, causing some websites to flag your environment as unusual. You can enable a suitable remote DNS in your Shadowrocket configuration, such as a commonly used public DNS service, and avoid using your local ISP’s DNS.
- IP unchanged: The proxy may not be enabled, the rules may not match, or the current app may not be using the proxy.
- DNS issue: Check your DNS settings, then try switching to global mode and testing again.
- Browser still flagged: Clear the cache, disable WebRTC leaks, and make sure your system time zone is not too inconsistent with the target region.
3. Recommended connection modes and rule settings
Beginners can start with “Global” mode to test whether a node works. Once you can access websites normally, switch to “Config” or “Rule” mode so that domestic websites connect directly and overseas websites use the proxy. This provides a more natural experience and reduces unnecessary proxy traffic.
If you imported a subscription, update it regularly, since free nodes often change. If you can’t connect, don’t just keep toggling the proxy on and off. First confirm that the subscription updated successfully, then try testing nodes that use different protocols or regions.
4. Connection troubleshooting checklist
- Make sure your phone’s network is working. You can first turn off Little Rocket and test access to domestic websites.
- Check that all node details are correct, especially the port, UUID, password, TLS, and transport method.
- Switch between Wi-Fi and cellular data, since some networks restrict proxy connections.
- Switch to Global mode to rule out a misconfigured rule set.
- Update your subscription or try another node to avoid using one that has expired.
- Restart Shadowrocket. If necessary, delete the VPN profile and approve it again.
In short, the essentials of using Shadowrocket are to import a working node, choose the right mode, and check that your IP and DNS are consistent. For everyday browsing, Rule mode is usually best; when troubleshooting, start with Global mode to verify the connection. This makes it easier to tell whether the issue is with the node, rules, DNS, or browser environment.