This article explains how to import a subscription into Shadowrocket and addresses common issues teams encounter when multiple people use it at the same time, such as dropped connections, disorganized nodes, and unstable account environments. It’s for users who already have a subscription link and want to import it quickly into Shadowrocket on an iPhone or iPad, while ensuring team members follow a consistent setup.
1. What to prepare before importing a subscription
Shadowrocket is only a client; it does not provide routes on its own. You’ll first need a working subscription link, usually starting with https. It may come from a proxy service, a company’s compliant proxy environment, or a free-node page curated by this site. For team use, it’s best for an administrator to distribute the same subscription entry point to everyone. If people copy different nodes at random, troubleshooting later can be difficult.
- Make sure Shadowrocket is installed and has permission to add VPN configurations.
- Copy the entire subscription link, including the token, parameters, and final characters.
- Import it over a stable connection, such as Wi-Fi or a reliable cellular network.
- Before sharing it with the team, confirm whether the subscription allows multiple users.
2. How to import a subscription into Shadowrocket
- Open Shadowrocket and tap “+” in the upper-right corner of the home screen.
- Select “Subscribe” or “Subscription” as the type. Don’t select a single-node type.
- Paste the subscription link into the URL field. You can add a note with the team name, such as “Design Team Proxy.”
- Tap “Done” in the upper-right corner. Back on the home screen, pull down to refresh the subscription.
- Once the refresh is complete, a list of nodes will appear. Choose one with low latency and a working connection.
- The first time you connect, a VPN permission prompt will appear. Tap “Allow.”
If no nodes appear after importing, check whether the link has expired or been truncated by a line break, then try refreshing again on a different network. Don’t repeatedly delete and reinstall the app; many issues are simply caused by an invalid subscription address or a network access failure.
3. How team usage affects account environment stability
For teams, importing a subscription into Shadowrocket isn’t just about whether the connection works—it can also affect the stability of your account login environment. For example, if accounts for cross-border e-commerce, overseas social media, or collaboration platforms use a US node one day, a Japanese node the next, and a Singapore node after that, the platform may flag the login environment as unusual.
Teams should therefore use consistent groups, regions, and purposes: use one group of nodes for operational accounts and another for research, and don’t let downloads or updates occupy business nodes. Team members shouldn’t arbitrarily change the exit region for the same account, especially not switch countries and IP addresses repeatedly in a short period.
Administrators can specify each node’s purpose in its subscription note, such as “Account Login Only,” “Research,” or “Backup Connection.” Team members should select nodes according to these guidelines rather than running a full speed test and switching among them at will. This is better for maintaining account continuity than simply chasing lower latency.
4. Troubleshooting connection failures and refresh issues
- Subscription refresh fails: Try opening the link in a browser to see if it loads, or switch networks and refresh again.
- Nodes import but won’t connect: Try another node in the same region and check that your device’s clock is accurate.
- Web pages won’t load after connecting: Check Shadowrocket’s routing mode. If you’re a general user, start with the default rules under “Configuration.”
- Multiple team members have issues at once: Contact the subscription provider first to check for device or data limits.
For teams, consistency is what matters most: use the same subscription source, consistent node names, and shared usage guidelines. The free nodes provided by this site can be used to test the import process, but teams relying on business accounts long term should prioritize stability and traceability. Don’t treat temporary nodes as core business connections.