Subscription Links vs. Nodes: What’s the Difference?
What is a VPN subscription link? It’s usually a configuration URL that includes access credentials. A client uses it to retrieve a list of nodes or a complete configuration. It isn’t an installer or a webpage you can open to connect. To get started, import the link into a compatible client, choose a route, and enable the connection.
Think of a subscription as the source of your configuration and a node as an individual connection endpoint. When a service changes node addresses or adds routes, you’ll usually need to refresh the subscription in your client to see those changes. Importing a link once doesn’t keep your local list in sync automatically; that depends on the client’s settings.
| Term | What it does | Common misconception |
|---|---|---|
| Subscription link | Provides a client with a node list or configuration file | Opening it in a browser automatically enables a connection |
| Single-node link | Specifies one connection endpoint and its authentication parameters | Importing one node automatically receives updates to the entire subscription |
| Routing rules | Determine which requests connect directly and which go through a proxy | A node list means every app will use the proxy |
| Client | Parses the configuration and handles relevant traffic according to system permissions | Every client supports the same subscription formats and protocols |
Where to find your subscription link
Get your link from the service’s account dashboard, not from an unverified source. ShunVPN users can visit the client download page, sign in, and follow the on-page instructions to get a subscription and a compatible client. No email address is required to create an account. Whether routes are available depends on your account status and the information shown in the dashboard; signing in and paying are separate steps.
Use the dashboard’s copy or import option whenever possible. Selecting the text manually can omit parameters at the end or add unwanted spaces and line breaks. If the dashboard offers different formats for different clients, choose the one that matches your app instead of copying any option labeled “subscription.”
A QR code may contain the same subscription URL, so scanning it doesn’t make it any less sensitive. Screenshots, clipboard history, and synced notes can all retain the full credentials. When asking for help, share only the error message and the necessary client details—not the full link, QR code, or configuration file.
How to import a subscription and verify it works
Button labels vary between clients, but the process is much the same: add a remote configuration, fetch its contents, enable it, and then connect. The steps below explain the general workflow; follow the instructions for your operating system and client when handling permissions.
- Check compatibility. Review the configuration formats and protocols your client supports. Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different protocols or protocol suites. Support for one doesn’t mean support for all, and the subscription file format must be compatible too.
- Add the remote subscription. In the client’s configuration, subscription, or profiles section, choose the option to import from a URL and paste the complete address. You can give it a recognizable local name, but don’t change any authentication parameters in the URL.
- Fetch and check the contents. Download or update the configuration and make sure the app doesn’t report a parsing error and that the node list appears. A successful import only means the configuration can be read; it doesn’t confirm that a particular route will connect.
- Enable the configuration and connect. Select the configuration you just imported and a route, then grant permissions as prompted by your system. System proxy and TUN modes handle traffic differently. Follow the client’s instructions rather than enabling every option at once.
- Test access. Try the website or app you need to use, then check the client’s connection logs to see whether requests match the expected rules. If something goes wrong, note what happened before changing settings. Adjust one thing at a time instead of changing rules, DNS, and nodes all at once.
On Windows and macOS, the system proxy usually applies only to apps that honor the proxy settings. Some command-line tools require proxy environment variables to be configured separately. TUN mode may need additional permissions and routing configuration. Mobile clients typically use the system VPN interface to handle traffic, but which requests go through it depends on the app and its configuration.
A connection icon in the status bar alone doesn’t prove that the target app is using the expected route. For platform-specific instructions, see the Quick Start Guide. Don’t assume permission steps for another operating system will apply.
When to refresh a subscription—and what changes
There’s no refresh schedule that applies to every service. Refresh manually after the first import, when you’re notified of route changes, or when nodes are missing or keep failing. If your client supports automatic updates, you can enable them according to its documentation; there’s no need to refresh repeatedly just to “keep your speed up.”
Refreshing a subscription usually downloads the configuration again; it doesn’t add data or extend a plan. ShunVPN monthly subscriptions reset each month on the activation date. Data packages remain valid until used and never expire. These account terms are separate from refreshing a subscription: updating the configuration doesn’t change your plan.
Check what the subscription contains, too. Some provide only nodes; others include proxy groups, rules, and DNS settings. Refreshing a remote configuration may overwrite changes you made locally. To keep custom rules, use the client’s supported override or merge options and check their priority.
First confirm that the subscription synced successfully, then check the route and your local network. Repeatedly refreshing the same configuration usually won’t fix congestion on your access network, an outage on the target website, or a routing-rule mismatch.
Troubleshooting failed imports, empty node lists, and connection issues
Start by identifying which step failed. A link that won’t return content, content the client can’t parse, and visible nodes that won’t connect are different problems. Calling all of them a “broken subscription” makes troubleshooting less focused.
- ✅ Can’t fetch the subscription: Copy the link again from the dashboard, check for extra spaces and whether it has been reset, and make sure your current network can reach the subscription URL. If you see a certificate error, check your system clock first; don’t disable certificate verification.
- ✅ Parsing failed: Check the subscription format, client version, and supported protocols. A URL opening in a browser doesn’t mean the client can parse its response; the page may be a sign-in screen or an error message instead.
- ✅ The list is empty: Make sure the new configuration is selected, check whether the update log reports success, and see if the account dashboard says the resources are unavailable. The import dialog closing doesn’t, by itself, mean the import worked.
- ✅ Nodes appear, but you can’t connect: Check the selected route, proxy mode, whether the app follows the system proxy, and whether another proxy or VPN app is running on your device.
- ✅ Only some websites have issues: Review routing logs and DNS settings. Check whether domain lookups and request routes match what you expect, then investigate any restrictions on the target platform.
A DNS leak occurs when domain lookups that should follow a controlled route take an unexpected path. Using a subscription doesn’t automatically prevent this: DNS behavior also depends on your operating system, browser secure DNS, client mode, and configuration. Check the actual DNS records rather than relying only on a change in your apparent IP address.
Subscription format and route type are different things. IEPL, transit, and direct connections describe transport paths or ways of connecting—not protocol options in an import menu. A subscription link alone doesn’t tell you whether a route uses a dedicated line, and it can’t guarantee a particular speed or access to any platform.
How to reset a leaked link and restore access
If your link appears on a public page, in an unfamiliar conversion tool, or on someone else’s device, look for an option in your account dashboard to reset the subscription, reset its token, or manage security. If there’s no clear option, use the contact page to confirm what to do. Don’t assume that changing characters in the URL will invalidate the old link.
After resetting the link, copy the new URL, replace the remote subscription on each of your devices, and update it. Refreshing the old URL won’t switch to the new credentials. If the client saved a complete configuration when you imported it, check for old authentication details there too; changing the configuration name isn’t enough.
Also distinguish between “the old link can no longer download a configuration” and “the old configuration can no longer connect.” Some systems manage subscription tokens separately from node credentials, so resetting a link may not revoke access for nodes that have already been downloaded. Confirm what the reset covers, and contact the service if related credentials need attention. Don’t assume changing your account password also resets the subscription.
After addressing the leak, remove public screenshots and shared copies, check your account usage for unusual activity, and make sure your devices are using the new configuration. When asking for help, you can share the error, operating system, and client version—but not the complete configuration. Subscription issues can usually be diagnosed from error details; you don’t need to share access credentials.