What Is a Subscription Link? A Credential for Fetching Configuration
What is a subscription link? It’s a URL that lets a client fetch server configuration, typically using credentials associated with your account. Once imported, the client can read the nodes, connection parameters, and rules included in the configuration. It isn’t a general information page or a connection switch: getting the link, importing the configuration, and enabling the connection are separate steps.
Think of a subscription link as an updatable source of configuration. When you add a node manually, its connection parameters are stored locally. With a subscription, the client also keeps the remote source so it can fetch configuration again later. That’s why, after a route change, updating the subscription is usually enough—you don’t need to reinstall the client.
Subscription formats vary between clients. A subscription may contain a list of nodes or a complete configuration with proxy groups, DNS settings, and routing rules. A URL opening in a browser doesn’t mean the returned content is compatible with your client. Similar-looking links don’t necessarily use the same format.
| Term | What it does | What it doesn’t tell you |
|---|---|---|
| Subscription link | Lets a client fetch remote configuration and may carry account credentials. | Doesn’t mean the plan is active or a connection is enabled. |
| Node | A set of server parameters used to establish a connection. | A node name doesn’t prove the actual route type or what it can access. |
| Protocol | Defines how the client and server communicate. | It isn’t a subscription format or a measure of route quality. |
| Plan | Defines the services and data-use rules available to the account. | Updating configuration doesn’t renew a plan or add data. |
Where to find it: sign in to the dashboard and choose your client
VPNRD subscription details are available after you sign in. Open the user dashboard, check your account status, then use the option provided there to get your subscription or import the configuration. Client and menu names may change between versions, so follow the current dashboard and guides rather than looking for an exact match in an old screenshot.
To get a client, visit the client downloads page. Downloads are available after signing in on platforms other than iOS; iOS access follows the active plan rules shown in the dashboard. Being able to download a client and being able to use a particular route are separate matters—a successful download doesn’t confirm that your account is in good standing.
- Check which platform and client you’re using, then see whether the dashboard offers a matching import option or format.
- Use the matching import option in the dashboard whenever possible. If you need to add it manually, copy the entire subscription URL—not just its display name.
- In your client, add a remote subscription or configuration source, paste the URL, save it, and update it.
- Check that the client has loaded the configuration, choose the required policy or node, enable the connection, then test the app you want to use.
How to import on each platform: different menus, same verification steps
The steps below describe the general process, not the exact location of a button. A client may call the option “Configuration,” “Subscription,” or “Remote Configuration.” One-click import from the dashboard usually opens an installed app. If nothing happens, first check that the app is installed and your system allows it to open, then try adding the subscription manually.
Windows: check system proxy or tunnel mode after importing
Add the subscription URL in a client that supports its format. After updating, select the configuration and node, then enable the system proxy or a traffic-capture mode such as TUN, following the client’s instructions. The system proxy affects only apps that use that setting; TUN usually requires extra permissions and correct routing configuration. If the node list appears but your browser still uses your usual connection, check that the connection is active and that the app follows the proxy before replacing the subscription URL.
macOS: allow the required network permissions
After adding the remote configuration, allow the required VPN configuration or network extension when prompted. Permission requirements vary by client; not all clients need the same extension. If you also use other network filters, work access tools, or proxies, check for conflicts one at a time. If the configuration downloaded but traffic isn’t being routed through it, check system authorization and the active mode.
iOS: check the configuration source and active profile
First, get a compatible client according to the dashboard rules, then use its import option or add the remote subscription in the app. When connecting for the first time, the system may ask to add a VPN configuration. After importing, make sure the newly added configuration is active, not one you saved earlier. A VPN icon in the status bar doesn’t mean every app uses the same route; actual behavior depends on the client, its rules, and system restrictions.
Android: distinguish import permissions from connection authorization
Updating a subscription and establishing a connection are separate steps. After the client loads the nodes, enabling the connection usually requires VPN authorization from the system. If the connection often drops when the app is in the background, check the system’s background and battery settings for it. If another app on the device also uses the system VPN feature, check for conflicts rather than assuming every interruption means the subscription has expired.
Linux: check the client and core configuration formats
Desktop clients usually let you add a remote configuration. In a command-line environment, follow the documentation for your core when handling configuration files and updates. Don’t treat a subscription URL as the path to a complete configuration file, and never run subscription text as a command. Downloading a credential-bearing URL from the command line may also leave it in shell history, so handle it according to your local credential-management practices.
When to update: follow configuration changes, not a fixed calendar
Updating a subscription fetches new configuration published by the service. Update after importing it for the first time, when the dashboard announces a route change, when the node list looks wrong, or when support asks you to refresh it. If your client supports automatic updates, configure them according to its official instructions. Without a specific reason, there’s no need to set a universal update interval.
If everything is working and there’s no notice of a configuration change, you don’t need to delete and recreate the subscription just because the date changed. Repeatedly adding it can leave duplicates and make it easy to select an old node by mistake. After updating, check whether it succeeded, whether the nodes changed, and whether your own rules still work.
Subscription updates don’t reset your data allowance. VPNRD monthly plans reset their data each month on the activation date; data add-ons remain valid indefinitely until used. Updating won’t reset your usage or restore an exhausted allowance. For billing terms and prices, see plan pricing. Check the dashboard for your remaining data.
Import failed? Check the format, then the network and account
“Update failed,” “couldn’t parse,” and “connection failed” describe different problems. An update failure may mean the URL is incomplete, credentials are invalid, or the request couldn’t be completed. A parse failure often points to an incompatible format. If the configuration loads but you can’t connect, check the node, traffic-capture mode, and local network. The exact error message is more useful for troubleshooting than simply saying “it doesn’t work.”
- ✅ Check that the URL is complete and contains no extra spaces, line breaks, quotation marks, or punctuation added by a messaging app.
- ✅ Make sure you selected a subscription format supported by your current client, not an import option meant for another client.
- ✅ Check the plan status and remaining data in the dashboard, and see whether the subscription credentials have been reset.
- ✅ Check the client’s update error and identify whether the request failed, the content couldn’t be parsed, or a node connection failed.
- ✅ Keep the relevant error text, but redact the full subscription URL, account credentials, and personal details before contacting support.
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are distinct protocols or protocol families, not interchangeable subscription labels. A client’s ability to parse a configuration format doesn’t mean its built-in core supports every protocol and parameter in that configuration. Check the client version and core capabilities. These names are included here to explain the terminology; they don’t mean VPNRD offers every protocol.
Likewise, IEPL dedicated lines, relayed routes, and direct connections describe how routes are organized, not import formats. Switching clients won’t turn a direct connection into a dedicated line, and renaming a node won’t change its actual route. Check the route details shown in the dashboard. If you’re unsure, contact support. Avoid repeatedly processing credential-bearing subscriptions through unknown conversion websites.
After importing: verify routing rules and DNS behavior
Having nodes in a subscription doesn’t mean every network request is handled as expected. In rule mode, domain and address rules determine whether traffic connects directly or through a proxy. Global mode usually sends traffic captured by the client to the selected policy, but system- or app-level exceptions may still apply. Test the apps you need rather than relying only on the client’s connection icon.
First, check whether the app you want to use can connect. Then use IP lookup to check the route used by your current browser. A normal browser result doesn’t prove that other apps or DNS requests use the same route. DNS translates domain names into addresses; if DNS requests aren’t routed as expected, queries may be exposed or the results may not match the route actually used.
If this happens, consult your client’s documentation and check how its DNS mode, system encrypted DNS, browser secure DNS, and routing rules interact. Encrypted DNS protects the connection to the resolver, but doesn’t automatically ensure that requests use the selected node. Don’t disable every system name-resolution feature at once. Change one setting at a time, then retest the scenario that failed.
Updating a complete configuration may also overwrite manual changes. If your client supports overrides or appended rules, use the documented method to preserve custom settings. Avoid editing the remote configuration directly, as the next update may replace your changes.
If a link is exposed: revoke the old credentials, then verify they no longer work
A subscription URL may let anyone who has it retrieve account-related server configuration, so treat it like a credential. A QR code is simply another way to represent the URL; turning it into an image doesn’t make it safe to share publicly. Screenshots, shared clipboards, public logs, and online conversion services can all expose it accidentally.
- Stop it from spreading. Retract messages where possible and remove public images or files, but don’t assume deletion invalidates the credentials.
- Revoke the old credentials. Sign in to the dashboard and look for an option to reset the subscription link or token. If there’s no clear option, contact official support and ask them to revoke the exposed subscription credentials.
- Update your devices. Once you have a new URL, replace the old source in each client and update it. Check that no old configuration is still selected.
- Confirm what was revoked. Ask support which old links and derived connection credentials have been invalidated. If necessary, handle connection credentials as instructed.
- Review your account. Check data usage and sign-in status. If your account password was also exposed, change it separately and address any related sessions.
When troubleshooting with others, share only error messages with sensitive details redacted. Don’t post the full URL in public support tickets or search engines. If support needs to check it, use official channels and provide only the minimum information requested.
Subscription basics for beginners: keep track of sources and limit copies
Day-to-day management can be simple: keep track of which client and subscription source you use, and which rules you maintain yourself. When switching devices, get the details from the dashboard again rather than digging through old chat messages; it’s easier to verify the source. Remove configurations from devices you no longer use to avoid selecting one by mistake later.