This guide explains how to import a subscription into Shadowrocket: prepare the subscription link, add it to the app, update nodes, and troubleshoot connection failures. It also covers how teams can reduce the impact of egress changes on account environments. The steps below use the iPhone version; button names may vary by version.
1. What to prepare before importing
“Little Rocket” usually refers to the iOS client Shadowrocket. Install it from its official App Store listing, and verify the app name and developer information. Do not install configuration profiles from unknown sources or purported cracked versions. You’ll also need the subscription link provided by your service provider. This is usually an HTTPS URL used to retrieve and update the node list.
A subscription URL is different from an official website address, a purchase page, or a link for sharing a single node. When copying it, make sure it doesn’t include spaces, line breaks, or punctuation from a chat message. The link may contain an access token, so team members should obtain their own authorized subscriptions rather than sharing links in group chats or public documents. If you use free nodes from sources such as this site, check that they’re valid and review the terms of use first.
2. How to import a subscription into Shadowrocket
- Open Shadowrocket and tap “＋” in the upper-right corner of the home screen to add a configuration.
- Under “Type,” select “Subscribe” or “订阅.” If your interface looks different, look for the subscription type option.
- Paste the complete subscription link into the “URL” field. Enter an easy-to-recognize name in the remarks field, such as “Work subscription,” then save.
- Return to the home screen and wait for the node list to load. If no nodes appear, try pulling down to refresh or open the subscription’s edit menu and update it.
- Select a node and turn on the connection switch on the home screen. The first time you connect, follow the iOS prompt to allow the VPN configuration and complete system verification.
- Open a browser and visit a website you want to use. Confirm that it loads, then check that the target app works as expected.
A successful import does not guarantee a working connection. Seeing a node list only means the subscription was parsed. Node status, network restrictions, and routing rules can still affect access. A latency test is no substitute for testing actual access.
3. How team use relates to account environment stability
A subscription itself does not determine whether an account remains stable. Relevant factors include the actual egress IP, region, device, and login behavior. Subscription updates may add or remove nodes, and manual switching or automatic policies may change the egress point. So, “importing the same subscription” does not mean “always using the same IP.”
Teams can standardize client versions and operating instructions, but they don’t need to share subscription credentials. For tasks that require continuity, choose an allowed region and a relatively stable node, and avoid switching frequently during a single session. Keeping the same node name does not guarantee that the egress IP will remain unchanged. If needed, verify the actual egress IP and follow the target platform’s account and regional rules. This cannot guarantee that risk controls will be avoided.
4. Troubleshooting import or connection failures
- Invalid address message: Copy the original subscription link again and check whether it has expired or been revoked, or whether you used a web page address by mistake.
- No nodes after updating: Make sure your current network can reach the subscription URL, and confirm with the provider that Shadowrocket is supported.
- Node connection times out: Check your local network first, then try another node. Avoid repeatedly importing the same subscription.
- Some apps won’t open after connecting: Check the routing mode and rules to confirm that the target traffic is going through the proxy. Then troubleshoot DNS according to the service provider’s instructions.
- Problems after an update: Check whether the currently selected node is still valid. If necessary, switch nodes and reconnect.
When asking for help, you can provide the client version, error message, and time of the issue. Be sure to redact subscription tokens, account information, and the full URL.