This article addresses the practical question of “how to import subscriptions into Shadowrocket”: after obtaining a subscription link, how to import, update, and connect it in Shadowrocket, and why the same subscription may behave differently under different IP, DNS, or browser environments, helping you complete setup and troubleshooting quickly.
1. What to prepare before importing a subscription
Shadowrocket is a commonly used proxy client on iOS that supports batch importing nodes through subscription links. You should prepare the following first: the Shadowrocket app installed, a valid subscription URL, and a stable network environment. This site also compiles free node and subscription testing information. When using it, it is recommended to first confirm whether the link is complete and still within its validity period.
- Subscriptions generally start with http or https; do not miss any parameters when copying.
- If the link contains fields such as token, user, or sub, do not modify them manually.
- Before importing, turn off other VPNs to avoid interference from double proxying.
2. How to import a subscription into Shadowrocket: step-by-step
- Open Shadowrocket, go to the home page, and tap the “+” in the top right corner.
- Choose the type “Subscribe” or “Subscription”; do not select a single-node type by mistake.
- Paste your subscription link into the URL field. For remarks, you can enter “free nodes” or a custom name.
- Tap save in the top right corner, then return to the home page and pull down to refresh the subscription.
- After a successful refresh, multiple nodes will appear. Select one node and turn on the connection switch at the top.
- On the first connection, iOS will prompt you to add a VPN configuration. Tap Allow and enter your system password.
If the subscription imports successfully but you still cannot access the internet, do not repeatedly delete the app right away. It is recommended to switch between 2–3 nodes for testing first, because a successful subscription import does not mean the nodes are necessarily usable; a node may be unavailable due to routing, region, or temporary maintenance.
3. How IP, DNS, and browser environment are related
Many users think that as long as Shadowrocket shows “Connected,” the proxy is definitely working, but the access environment also matters. IP determines the exit address a website sees. If the node is working properly, an IP check should show the region of the proxy node rather than your local ISP address.
DNS is responsible for resolving domain names into IP addresses. If DNS still goes through the local network, issues may occur such as websites not opening, abnormal redirects, or inaccurate region detection. In Shadowrocket, you can enable appropriate DNS settings in the configuration. Ordinary users can generally keep the client defaults and adjust only when encountering pollution or resolution failures.
Browser environment includes cache, cookies, language, time zone, WebRTC, and more. Even if the proxy IP has changed, a website may still determine your original environment based on old cookies or browser fingerprints. During testing, you can use an incognito window or clear the target website’s cache before visiting again.
4. Troubleshooting import and connection failures
- Subscription import failed: check whether the link was copied completely, and try opening the link in Safari to see whether it returns content.
- No nodes appear: the subscription format may not be recognized by Shadowrocket; try the corresponding link in Clash/V2Ray format instead.
- No internet after connecting: turn the VPN off and back on, switch nodes, or test by changing from Wi‑Fi to cellular.
- Only some websites cannot be opened: prioritize checking DNS, rule-based routing, or browser cache issues.
- Frequent disconnections: the node may be unstable; refresh the subscription and choose a node with lower latency.
Summary: the core of importing a subscription into Shadowrocket is “add the subscription URL, refresh, select a node, and connect.” After that, check the IP, DNS, and browser environment to more accurately determine whether the problem lies with the subscription, the node, or the local access environment.