What is a VPN subscription link? It’s an address a service uses to deliver connection configurations to compatible clients. Once you import the link, the client reads the available connection profiles. Select “Update subscription” to fetch the latest configuration from the server. It isn’t a single connection address you can paste into a browser to speed things up, nor is it the same as a plan. For beginners, the most useful order is: get the link from the service dashboard, make sure your client supports its format, import and update it, then select a route and test the connection.
First, understand the difference between a subscription link, a server, and a client
A subscription link is usually a URL beginning with https:// that points to a service’s configuration endpoint. The client connects to that endpoint and parses the route names, server details, and connection parameters. The link is a credential for retrieving configuration; a route is a connection destination listed in that configuration; and a client is software that reads the configuration and establishes the connection. Knowing the difference helps pinpoint whether the problem is with retrieval, parsing, or connecting.
Some clients can also import a single connection profile shared as a link, often starting with the protocol name. A single route and a subscription URL serve different purposes: the former adds one specific profile, while the latter can fetch the full set of routes provided by the service whenever it’s updated. Keeping an old copy of the route list doesn’t preserve the ability to get future updates.
| What you have | Main purpose | Next step |
|---|---|---|
| Subscription link | Lets a compatible client retrieve and update its configuration | Import it from the client’s subscription or configuration menu |
| Single-route share link | Adds a specific route | Import it using the client’s route import option |
| Client installer | Provides tools for reading configuration and establishing a connection | Install it, then import a compatible configuration |
Format matters, too. Common clients may accept Clash-style YAML, sing-box-style JSON, or other subscription formats supported by specific clients. A file extension alone doesn’t tell you whether a configuration will work: parsing, protocol support, and routing rules all depend on the client. Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are names of different protocols or connection methods—not interchangeable “subscription formats.” Support for a particular protocol doesn’t necessarily mean a client can read every subscription URL a service provides.
Where to get your link and how to store it safely
Start with the dashboard of the service you use or its official setup guide. For VPNNJ, open the user dashboard to find your account’s connection details, then check the client downloads for your platform. If the dashboard offers configurations for different clients, choose the one that matches yours. VPNNJ does not require an email address to register, but treat your subscription link as a private access credential.
When copying the link, don’t edit or remove any characters. And don’t mistake another page’s URL in your browser’s address bar for a subscription link. If the service offers both “Copy subscription” and “Download configuration,” first check whether your client needs a remote URL or a local file. A remote URL makes it easy to fetch updated configuration later; a local file usually contains only what was available when you downloaded it. Dashboard labels vary, so confirm whether the client shows an updatable subscription or a one-time imported configuration.
- ✅ Copy the link from the service dashboard and check that it matches your client or configuration format.
- ✅ Paste the link into the client’s subscription field. Don’t share it in public posts, shared documents, or screenshots.
- ✅ After importing, confirm that the subscription updates successfully and that routes appear in the list.
- ❌ Don’t assume an unfamiliar conversion website in search results is a required step for importing a link.
A subscription URL may contain information used to identify your access permissions. When troubleshooting, you can share the error message and client type. Before showing a page or log to anyone, hide the full URL and its query parameters.
How to import a subscription on each platform
Button labels vary between clients, but the general process is similar: install a client that supports the configuration format, open “Subscriptions,” “Configuration,” or “Profiles,” add the remote URL, update it, then select a route and connect. Don’t keep switching routes before confirming that the format is supported. If the configuration hasn’t been parsed, changing routes won’t fix the import problem.
Windows and macOS
In your desktop client, check whether the add-configuration menu offers “Import from URL” or a similar option. Paste the subscription URL, wait for the update to finish, then check for routes or groups. On Windows, system proxy mode typically affects only apps that follow the system proxy settings. For broader traffic coverage, the client may offer TUN mode, depending on its implementation, drivers, and permissions. A macOS client may also ask you to approve a network extension. Before granting permission, make sure the request comes from a trusted client you installed, then follow the system prompts.
Android and iOS
On mobile, add the remote URL from the client’s configuration or subscription screen. Once the update succeeds, select a route and allow the system to establish a VPN connection. If the connection often drops when an Android app is in the background, check the system’s background activity restrictions for that client. On iOS, distinguish between a configuration that hasn’t been imported and a system connection that hasn’t been approved. Protocol and configuration format support varies by app, so don’t assume a configuration that works on desktop will also work on mobile.
Linux
Linux clients may have a graphical interface or rely mainly on the command line and configuration files. Read the client’s format documentation first: if it accepts only local configuration files, you can’t use a remote subscription URL as a file path. If it supports subscription management, add the URL and update it as instructed. Otherwise, use a compatible configuration from the service and an explicitly supported import method. Before running commands, check that the configuration file has the right read permissions, and don’t commit credentials to a public repository.
On any platform, seeing route names in the client only confirms that it read the configuration. You still need to connect and check that the target app uses the expected proxy route. If you need routing rules for specific apps or websites, review the rule mode and direct-connection rules. Confusing “Global,” “Rules,” or “Direct” settings with route types can leave the client showing as connected while the target app takes a different route than expected.
How often to update and what to check afterward
There’s no universal update schedule for every service. Update the subscription once right after importing it. Update it again if the service dashboard indicates a configuration change, the route list doesn’t match the dashboard, you switch to a different configuration, or an existing route stops working. If your client supports automatic updates, enable them if useful, but make sure you know where to update manually. Updating a subscription fetches configuration; it doesn’t renew your plan or automatically choose the best route for what you’re doing.
After updating, check whether route names or groups have changed, then connect to a route suited to your current use. AI tools, web browsing, and cross-border business may call for different regions and routing rules. IEPL dedicated lines, relays, and direct connections describe different access or transmission paths; none is necessarily faster for every destination. Direct routes take a more straightforward path, relays add an extra connection point, and dedicated lines use a specific transmission arrangement. Choose based on the destination, your current network, and actual connection performance—not just the route name.
If a website shows an exit region that doesn’t match your selected route, first confirm that the current proxy mode covers the target app, then check routing rules and DNS settings. A DNS leak means domain lookups aren’t following the intended resolution path; it’s a separate issue from whether the route connects. Use a trusted IP and DNS checker to compare exit details rather than relying only on the client’s “Connected” status. You can also check your visible exit address on our My IP page.
Import errors and leaked links: what to do
If you see “Unable to retrieve subscription,” first check that the link was copied in full, that the device’s current network can reach the configuration endpoint, and that the service dashboard shows the configuration as available. If you get a format error or the list is empty after updating, check that the client supports the configuration format before guessing which region to use. If routes appear but won’t connect, confirm that the client supports the selected protocol and meets the version requirements in its documentation, then test another route suited to your use. Don’t paste the subscription URL into an unfamiliar online converter and hope for the best.
If the link appears on a public page, in a shared record, or in a screenshot, first remove anything you can control and stop sharing the old link. Then check the service dashboard for an option to reset or regenerate your subscription credentials. If there’s no clear option, contact customer support to ask how to revoke the old link. Once you have a new one, remove the old subscription from your client, import the new URL, and update the configuration. Renaming the local subscription or uninstalling the client won’t invalidate a link that’s already been exposed.
If old routes still appear after a reset, check for cached configurations or another subscription with the same name. Review the subscription source on each device you use regularly so one device doesn’t keep requesting the old URL after another has switched to the new one. When contacting support, provide the issue, platform, and client name—never post the full subscription URL in a public discussion. Link management matters just as much as route selection: the link determines who can retrieve the configuration, while the route determines how your traffic is handled by the client.
A more reliable troubleshooting order than repeatedly copying route names is to get the right configuration from the dashboard, import and update it in your client, then check the connection’s exit route.