This guide answers common questions about how to use Shadowrocket: how to import nodes or subscriptions, how to enable the proxy, and why the same node can show different results for IP, DNS, and browser settings. It’s for iPhone and iPad users who have just installed Shadowrocket and want to get started step by step.
1. Get a node or subscription ready
Shadowrocket is a popular proxy client for iOS, but it doesn’t provide server connections—you’ll need to import usable nodes. These may use protocols such as Vmess, VLESS, Trojan, or Shadowsocks, or come as a subscription link. You can use a subscription you already have, or try the free nodes listed on this site for temporary testing. Free nodes can be unreliable, so it’s a good idea to have a few backups.
- Open Shadowrocket and tap “+” in the top-right corner.
- For a subscription link, set “Type” to Subscribe, paste the URL, save it, then tap Update.
- For a single-node link, copy it and return to Shadowrocket; it will usually be detected automatically. You can also select the corresponding protocol and enter the details manually.
- Return to the home screen, select a node, and tap the switch at the top. The first time you connect, follow the prompt to allow Shadowrocket to add a VPN configuration.
When the connection is successful, a VPN icon appears in the iOS status bar. Most app and browser traffic will then follow the configured rules.
2. Choosing a routing mode
Many people assume that turning on the switch automatically enables global proxying, but Shadowrocket’s behavior depends on its configuration rules. There are three common modes:
- Configuration mode: Routes traffic according to rules—for example, connecting directly to domestic websites and using a proxy for overseas websites. Recommended for everyday use.
- Global proxy: Routes almost all traffic through the node. Useful for testing your IP, but may slow down access to domestic services.
- Direct mode: Bypasses the proxy. Often used to check whether a problem is caused by the node.
If you just want to access popular overseas websites, use Configuration mode. To check whether your IP has changed, you can temporarily switch to Global Proxy, then switch back when you’re done.
3. How IP, DNS, and browser settings are related
IP is the outgoing address that websites see, and is usually determined by the node you select. After connecting, visit an IP lookup website. If it shows the node’s location, the proxy is probably working.
DNS resolves domain names. If DNS requests still go through your local network, a DNS leak may occur—for example, your IP appears to be overseas while your DNS shows your local provider. You can enable remote DNS in Shadowrocket’s settings or use the DNS built into your configuration file. Avoid combining multiple DNS tools at random, as this can cause conflicts.
Browser settings include language, time zone, cookies, WebRTC, and location permissions. Even if your IP changes, your browser may still reveal information about your original environment through your system language, previously used accounts, or location permissions. For testing, use a private browsing window, disable website location access, and clear site cookies if needed.
4. Troubleshooting connection failures
- Try a different node first. Free nodes often stop working, so update your subscription and try again.
- Check that the link is complete. Make sure you haven’t missed any parameters or line breaks when copying it.
- Switch networks. Try cellular data instead of Wi-Fi to rule out local network restrictions.
- Turn off other VPNs or accelerators. iOS can reliably use only one VPN configuration at a time.
- Check the logs. Tap the information icon next to the node or open the logs. “timeout” usually means the server is unavailable, while “handshake failed” usually indicates a protocol parameter mismatch.
In short, the basic Shadowrocket workflow is to import a node, choose a routing mode, enable the VPN, and check your IP and DNS. For everyday use, rule-based routing is recommended. If you run into problems, update your subscription and try another node first, then check your DNS and browser settings—that’s usually the quickest way to resolve the issue.