This guide answers the question “How do I use Shadowrocket?” It covers the initial setup after installation, importing free nodes or a subscription, and checking your IP, DNS, and browser environment. It will help you quickly determine whether your connection is working and troubleshoot common connection failures.
1. Basic steps for using Shadowrocket
Shadowrocket is a popular proxy client for iOS, commonly known as “小火箭” (Little Rocket). It does not provide proxy servers itself, so you’ll need to import working nodes or a subscription link. This site collects free nodes for testing, which are suitable for temporary use and learning. However, free nodes can vary in reliability, so check whether they’re actually working.
- Install Shadowrocket on your iPhone or iPad, and allow it to add a VPN configuration.
- Open the app, tap “+” in the top-right corner, then select “Type” or “Import from Clipboard.”
- If you have a link for a single node, such as VLESS, VMess, Trojan, or SS, copy it and return to Shadowrocket. The app will usually recognize it automatically.
- If you have a subscription link, select “Subscribe,” paste the URL, save it, and tap Update.
- Return to the home screen, select a node, and turn on the connection switch at the top. The first time you connect, confirm the system’s VPN permission prompt.
When the connection succeeds, a VPN icon appears in the iOS status bar. Don’t rely on the icon alone: check your IP and DNS as well to avoid situations where the app shows as connected but webpages won’t load.
2. How IP, DNS, and your browser environment are related
Many people assume that if Shadowrocket is on, everything is working properly. In fact, you should check at least three things: your outbound IP, DNS resolution, and browser cache. Your outbound IP determines where websites think you’re connecting from; DNS determines how your domain names are resolved; and your browser may retain old cookies, location permissions, or cached data.
- Check your IP: Open an IP lookup website before and after connecting, and compare the country or region shown.
- Check DNS: If your IP has changed but some websites still won’t load, the cause may be DNS pollution or an unsuitable routing rule.
- Check your browser: Try an incognito window, or clear the target website’s cache and cookies.
- Location permissions: Some apps use GPS instead of relying only on your proxy IP. You may need to disable location access or handle it separately.
In Shadowrocket, you can check the current mode on the Configuration or Rules page. If you’re new to the app, start with “Global Proxy” to test the connection, then switch to rules mode. If you’re unfamiliar with the rules, mixing them indiscriminately can cause some websites to use the proxy while others connect directly.
3. Updating subscriptions and switching nodes
A subscription isn’t a one-time import that stays usable forever. Nodes may stop working, domains may change, and routes may undergo maintenance. Open the subscription list in Shadowrocket, tap Update, and wait for the node list to refresh. Then choose a node with low latency that loads webpages normally. There’s no need to stick with the same node all the time.
If you copy free nodes from this site, it’s a good idea to import several as backups. When testing, start with common webpages, then try video and sign-in websites. If a node frequently times out, switch to another one instead of repeatedly restarting your phone.
4. Quick troubleshooting for connection failures
- Make sure the node link is complete, with no missing characters or extra spaces.
- Check that your device’s date and time are correct. A large time discrepancy can cause TLS connection failures.
- Switch between Wi-Fi and cellular data to rule out restrictions on your current network.
- Switch to Global Proxy to test whether the issue is caused by routing rules.
- Delete the old VPN configuration, then authorize Shadowrocket again.
In summary, the basics of using Shadowrocket are: “import a node or subscription—select a node—connect—check your IP, DNS, and browser environment.” Following these steps makes it easier to determine whether the problem lies with the node, rules, DNS, or browser cache.