This article explains how to import a subscription into Shadowrocket and how to troubleshoot connection problems by checking your IP, DNS, and browser environment. “小火箭” usually refers to Shadowrocket on iOS. These steps are for users who already have a subscription link or a free node subscription from this site.
1. Basic steps for importing a subscription into Shadowrocket
Before importing, make sure you have a subscription link, which usually starts with https://, rather than a long configuration string for a single node. If you need to copy the link, copy it in full without leaving out any parameters.
- Open Shadowrocket and go to the main screen.
- Tap the “+” in the upper-right corner, then select “Subscribe” as the type.
- Paste the subscription URL into the URL field. You can enter “Free Nodes” or a custom name as the remark.
- Tap Save. Then return to the list and pull down to refresh the subscription.
- Select a node and turn on the connection switch at the top.
- The first time you connect, you’ll be prompted to add a VPN configuration. Follow the system prompts to allow it.
If you’re using a free node subscription from this site, refresh it first, then test a node with a low latency and a clear name. Free nodes may stop working as the number of users or the status of a route changes, so try another node if a connection fails.
2. Can’t connect after importing? Check the subscription and node first
Many problems aren’t caused by Shadowrocket itself. The subscription may not be up to date, the node may be unavailable, or the protocol may not be compatible. Check the following in order:
- Make sure the subscription link opens in a browser. If it shows a blank page, a 404 error, or is inaccessible, the link may have expired.
- Pull down to refresh the subscription manually in Shadowrocket and check whether the node list has updated.
- Try two or three different nodes instead of testing just one.
- Check that your system time is correct. An incorrect time can affect some TLS connections.
If the node list includes different protocols, such as VLESS, VMess, and Trojan, Shadowrocket can generally recognize them, provided the subscription is formatted correctly. Don’t import a Clash configuration file as a standard subscription, or Shadowrocket may be unable to parse it.
3. How IP, DNS, and your browser environment affect the connection
Once Shadowrocket connects, the IP address websites see will usually be the node’s IP. If a webpage still shows your local IP, you may not have enabled the proxy, your routing rules may not be applying, or browser cache may be affecting the result. Try testing again in a private window.
DNS can also affect your experience. If DNS isn’t working properly, the VPN may show as connected while webpages fail to load or some websites fail to resolve. Try enabling remote DNS in Shadowrocket’s configuration, or switch to your system network and reconnect. Avoid running multiple proxy tools at the same time, as this can cause DNS and routing conflicts.
Your browser environment matters too. Some websites read information such as cookies, language, time zone, and WebRTC, which can make your apparent location differ from the location associated with the node’s IP. To troubleshoot, disable browser extensions, use private browsing, and clear the target website’s cache. If you only want to check whether the proxy is working, use an IP-checking website first.
4. Tips for handling common errors
If you see messages such as “timeout,” “TLS handshake failed,” or “unable to parse subscription,” don’t keep toggling the connection on and off. A better approach is to refresh the subscription, then try another node. If it still fails, restart Shadowrocket and your network, then check whether the subscription link has expired. For most users, making sure the subscription URL is correct, the node is available, and system VPN access is allowed will resolve most issues.
In summary, importing a subscription into Shadowrocket is straightforward: add a Subscribe entry, paste the link, refresh the node list, and connect to a node. If you have trouble accessing websites afterward, check whether your IP has changed, DNS is working, and your browser environment is interfering.