This article addresses the practical question of how to import a subscription into Shadowrocket (“Little Rocket”), with a focus on shared use by multiple people or teams. It explains how to import a subscription and update nodes in Shadowrocket, and how subscription management, account environments, and connection stability are related, helping you avoid frequent disconnections, disorganized nodes, and accidental changes.
1. What to prepare before importing a subscription
Shadowrocket is a commonly used proxy client for iOS. Before importing a subscription, make sure Shadowrocket is installed and that you have a valid subscription link. Subscription links usually start with https and return a list of nodes when opened. You can use an existing subscription or try one of the free-node pages curated on this site. However, free-node stability depends on the number of users and network conditions, so free nodes are best suited for temporary use or troubleshooting.
- Make sure your phone can access the internet.
- Copy the entire subscription link, including the token, parameters, and any trailing characters.
- For team use, have an administrator distribute the subscription centrally rather than allowing people to forward it freely.
2. Steps to import a subscription into Shadowrocket
Here’s the most common import method, suitable for first-time setup or switching subscriptions:
- Open Shadowrocket and go to the home screen.
- Tap the “+” in the upper-right corner and select “Subscribe” or “Subscription” as the type.
- Paste the subscription link into the URL field. For the label, enter a clear name such as “Team Subscription” or “Backup Nodes.”
- Tap Save. Return to the home screen, pull down to refresh, and wait for the node list to appear.
- Select a node with low latency and a clear name, then turn on the connection switch at the top.
If no nodes appear after importing, first check that the link is complete, then try switching networks and refreshing. Some subscriptions need to be updated regularly. Avoid manually splitting a subscription into individual nodes for long-term use, as subsequent node changes won’t sync.
3. How subscriptions and account environments relate in team use
Many people assume that importing the same subscription means every device will have the same experience. In reality, connection stability also depends on the account environment, device network, and usage habits. In team settings, take particular care not to switch the same set of nodes frequently across multiple users. Also avoid repeatedly logging in to the same business account from different regions and network environments, as this may trigger security checks on the destination website.
A subscription is just a “list of node entry points”; it is not the account environment itself. For example, if team member A logs in to a platform using a Hong Kong node, then team member B soon logs in to the same account using a US node, this may look like an unusual change in environment. A safer approach is to keep the region and node type consistent for each business account and avoid unnecessary switching. If several people need to collaborate, agree on usage rules in advance.
4. Troubleshooting connection failures and subscription issues
If you can’t connect after importing a subscription into Shadowrocket, troubleshoot in this order:
- Subscription won’t refresh: Check whether the link has expired and whether it was copied in full. Try opening it in a browser to see if it returns any content.
- Nodes are listed but won’t connect: Test two or three other nodes to rule out an issue with a single node.
- Connected, but webpages won’t load: Check Shadowrocket’s rule mode. Try switching to Global Proxy mode to test.
- Several team members are having issues: The subscription source, node routes, or network egress may be the problem. Contact the subscription provider for an update.
- Only one device is affected: Restart Shadowrocket, turn VPN permissions off and back on, or delete and reimport the subscription.
Don’t change too many settings at once while troubleshooting. Take a screenshot of your original configuration first, then try changes one at a time. For teams, it’s best to assign one person to maintain the subscription while other members only refresh it and avoid changing rules. This helps prevent inconsistencies caused by differing configurations.
5. Tips for use
For everyday use, add frequently used nodes to your favorites and update the subscription regularly. If speeds are slow or connections fail, first determine whether the issue affects one node or the entire subscription. Don’t publish your subscription link publicly, as this may lead to misuse, expiration, or restrictions. For team collaboration, consistency is more important than constantly chasing the “fastest node.” Keeping regions and rules consistent and updating the subscription centrally usually makes the experience easier to manage.