This guide addresses the practical question “How do I use Shadowrocket?” It covers importing nodes or subscriptions on an iPhone or iPad, enabling the proxy, and why you should also pay attention to your IP, DNS, and browser environment after connecting. It’s intended for everyday users who are new to internet proxy tools.
1. Basic steps for using Shadowrocket
Shadowrocket, often nicknamed “Little Rocket,” is a popular proxy client for iOS. It doesn’t provide servers itself, so you’ll need to import a working node or subscription link. This site collects information on some free nodes, or you can use a subscription URL you already have.
- Open Shadowrocket. On the main screen, tap “+” in the upper-right corner.
- If you have a single node, select its type, such as Vmess, VLESS, Trojan, or Shadowsocks, and enter the server, port, UUID/password, TLS settings, and other details provided by your service.
- If you have a subscription link, select “Subscribe/Subscription,” paste the URL, and save it. Then return to the home screen and pull down to refresh.
- Select a node from the list and tap the switch on the right. The first time you do this, you’ll be prompted to add a VPN configuration. Tap Allow and enter your device passcode.
- Once the status shows that you’re connected, open a browser and visit a site to check that it loads as expected.
For beginners, importing a subscription is usually the easiest option because it makes updating nodes simpler. If a node stops working, just refresh the subscription or switch to another node.
2. How IP, DNS, and your browser environment are related after connecting
Many users assume that seeing “Connected” in Shadowrocket means all their traffic is being proxied. In practice, you should also check what network information websites can see when you visit them. Your IP address tells a site where you appear to be connecting from; DNS translates domain names into server addresses; and your browser environment includes details such as your language, time zone, cache, cookies, and WebRTC.
- IP: After connecting to a node, use an IP lookup site to check whether your outgoing IP has changed. If it still shows your local ISP’s IP, the proxy may not be working or the rules may not cover your traffic.
- DNS: A DNS leak may reveal your local DNS lookups to websites. You can enable remote DNS in your Shadowrocket configuration or use a reliable ruleset.
- Browser: If you’ve previously signed in to an account or saved cookies, a site may still recognize you based on that history. If needed, use a private window or clear your cache.
- WebRTC: Some browsers may expose local network or real network information through WebRTC. If privacy is a priority, consider disabling this feature.
In short, Shadowrocket proxies your traffic, but your IP, DNS, and browser fingerprint all affect the environment that websites see.
3. Troubleshooting connection failures
If Shadowrocket won’t connect, don’t rush to reinstall it. Check the following in order:
- Make sure the node hasn’t expired and that the subscription link refreshes successfully.
- Try a different network, such as switching from Wi-Fi to cellular data, to rule out local network restrictions.
- Check that your device’s date and time are correct. An incorrect clock can cause TLS handshakes to fail.
- Try another node from the same subscription to determine whether the problem is with one node or the client configuration.
- Check the Shadowrocket logs. Common errors include timeout, TLS failed, and connection refused, which can point to a timeout, a certificate issue, or an unavailable port.
If only some websites won’t load, the issue may be with your rules mode. Try switching temporarily to Global Proxy to test. If that works, switch back to rules mode and check your routing rules.
4. Tips for everyday use
Keep the client and subscription updated, and avoid running multiple VPN apps at the same time, as this can cause routing conflicts. Free nodes are suitable for occasional testing and light browsing, but their reliability may vary. If a connection is slow or keeps dropping, try switching nodes, refreshing the subscription, and checking DNS first. Once you’re familiar with these steps, you’ll be better able to tell whether a problem is caused by the node, the rules, DNS, or your browser environment.