How do you import a subscription into Shadowrocket, and how do you update it and connect afterward? And how can teams reduce changes to their network egress? Using Shadowrocket on iPhone as an example, this guide walks you through everything from copying a subscription link to verifying your connection, and explains how subscriptions relate to account environment stability. Button names may vary slightly between versions, so follow the labels in your app.
Before importing: Check the client and subscription type
Get the official Shadowrocket app from the App Store, and avoid modified versions from unknown sources. Have the subscription link provided by your service ready, and confirm that it supports Shadowrocket. A subscription link is not the same as an official website address or a link to a single node: subscriptions are generally used to retrieve and update multiple nodes, while links such as vless:// and vmess:// are usually used to import individual configurations.
Subscription links may contain access tokens, so protect them like passwords. Don’t post them in public groups or include them in screenshots. If you use free nodes curated on this site, check when they were last updated, which clients they support, and any usage restrictions. You’ll need to verify availability yourself.
Import a subscription into Shadowrocket: Follow these steps
- Copy the full link from the subscription provider’s page. Make sure you don’t miss any trailing parameters or include spaces or line breaks.
- Open Shadowrocket and tap “+” in the top-right corner of the home screen. Under “Type,” select “Subscribe” or “Subscription.”
- Paste the link into the “URL” field. Enter an easy-to-recognize name in the remarks field, such as “Team Office Subscription,” then save.
- Return to the home screen and wait for the subscription to load. If it doesn’t load automatically, find the update option for that subscription and refresh it manually.
- Expand the subscription, select a node, and turn on the connection switch on the home screen. The first time you connect, follow the system prompts to allow a VPN configuration and complete device verification.
- Open a website you want to use to verify the connection. For everyday use, “Config” or rule-based mode is usually a good choice; the actual routing depends on your current rules. For troubleshooting, you can temporarily switch to proxy mode for comparison, then switch back afterward.
A successful import only means the configuration was retrieved; it doesn’t guarantee that a node will work. Latency tests are only a guide. The best test is whether the websites or apps you need can actually be accessed.
For teams: How do subscriptions relate to account stability?
A subscription distributes node configurations; it doesn’t, by itself, make business accounts more stable. The environment used to sign in is also affected by factors such as egress IP, device, browser state, login location, and the platform’s risk controls. Updating a subscription and switching nodes can change your egress IP. Even if the node name stays the same, that doesn’t necessarily mean the egress IP is fixed.
Teams can standardize client setup instructions, but shouldn’t share personal subscriptions indiscriminately. First confirm whether the provider allows multiple users and whether it limits simultaneous connections. For work accounts that need to stay signed in, try to keep the device and usual egress IP consistent, and avoid switching between regions repeatedly in a short time. Enable multi-factor authentication and follow the business platform’s rules. Using the same node consistently does not guarantee that your account won’t be prompted for verification.
Import failed or can’t connect? Troubleshoot in this order
- Subscription is empty or an error appears: Check that the link is complete and hasn’t expired, and ask the provider to confirm the format and authorization status.
- Update failed: Turn off the proxy, make sure the phone’s basic network connection is working, and try again. Avoid repeatedly deleting and reinstalling the app.
- Nodes appear but won’t connect: Update the subscription manually, try another node, and compare the results over Wi-Fi and cellular data.
- Only some apps are affected: Check the routing rules and whether another VPN is conflicting. Also check whether the target service is experiencing an outage or restricting access.
If the issue persists, note the error message, client version, and type of network where it occurred, then contact your subscription provider. Before sending a screenshot, hide the subscription link, token, and account details so the provider can troubleshoot safely.