This article explains how to import a subscription into Shadowrocket, step by step: prepare the link, add the subscription, update nodes, and check the connection. It also explains how teams can reduce account verification triggered by frequent changes in their exit IP. “Little Rocket” usually refers to Shadowrocket on iPhone or iPad. A successful import only means the client has read the configuration; it does not mean the nodes are necessarily available or guarantee a stable account environment.
1. What to prepare before importing
First, get the official Shadowrocket app from the App Store and verify the developer and app details to avoid unofficial software with the same name. Then obtain a subscription link compatible with Shadowrocket from your service provider. A subscription is usually an HTTPS URL, unlike a share link for a single node, and can sync node changes when updated.
Treat your subscription link like a password: it may contain access credentials, so don’t post it in public groups or documents, or include it in screenshots. If you use free nodes provided through sources such as this site, check the format, expiration date, and usage instructions. They are not recommended for work involving sensitive information.
2. How to import a subscription into Shadowrocket
- Copy the full subscription URL. Check that no spaces, line breaks, or Chinese punctuation have been added at the beginning or end.
- Open Shadowrocket and tap “＋” in the upper-right corner of the home screen to open the add page.
- Tap “Type” and select “Subscribe.” The label may vary slightly in different versions.
- Paste the URL into the “URL” field, enter an easy-to-recognize name in the remarks field, such as “Team Authorized Subscription,” then save.
- Return to the home screen and wait for the client to fetch the nodes. If they don’t update automatically, tap the update button for the subscription group or update it manually from the subscription management page.
- Expand the group, select a node, and turn on the connection switch on the home screen. The first time you connect, follow the system prompts to allow adding a VPN configuration and complete device verification.
- Open a website you need to access to confirm the connection. Before testing, turn off any other VPNs to prevent network tools from interfering with one another.
Don’t treat the subscription URL as a website login URL. If opening it in a browser displays a string of characters or downloads a file, that doesn’t necessarily mean the link is broken; what matters is whether the client can recognize it. Don’t submit URLs containing credentials to unfamiliar online conversion sites, either.
3. Troubleshooting import or connection issues
- Format error: Copy the original link again and confirm that the provider supports Shadowrocket, rather than offering a configuration intended only for another client.
- No nodes after updating: Check whether the subscription has expired, been disabled, or is restricted to certain devices, then contact the provider to confirm.
- Subscription download times out: Switch between Wi-Fi and mobile data and try again. If the link requires a particular network to access, ask the provider for an alternative entry point.
- Nodes are available but you can’t access the internet: Try another node, confirm the connection switch is on, and check that you haven’t accidentally selected direct connection mode.
- Some websites won’t open: Test again using the default rule mode. Avoid adding rules or DNS settings from unknown sources at the outset.
4. How team use relates to account stability
Each team member should install the client separately and use a subscription authorized under the service terms. Don’t share Apple IDs or business account passwords. Using the same subscription doesn’t mean sharing the same exit IP: different members may select different nodes, or node routing may change, resulting in different exit IPs.
For business accounts that need persistent logins, use a consistent, compliant region and node where possible, and avoid switching regions frequently over a short period. Enable two-factor authentication and manage team permissions according to the platform’s rules. Account risk checks may also take device, browser state, and user behavior into account, so a VPN alone cannot guarantee stability. If you encounter an unexpected verification prompt, stop switching nodes and contact official support rather than repeatedly changing nodes to try to log in.