What is a VPN subscription link?
A VPN subscription link is a dedicated address that a client uses to retrieve route configurations. It is not a regular website link or a payment page. After you import it into a compatible client, the client requests configuration data from that address, including route names, server addresses, and the authentication details needed to connect. A successful import only means the configuration was retrieved; you still need to select a route and enable the connection.
“VPN subscription” is a common term for this setup, but it does not mean every configuration uses the same VPN protocol. A subscription may contain configurations for Shadowsocks, VMess, Trojan, VLESS, Hysteria2, or TUIC. Actual protocol support depends on the configuration provided by the service and the client’s core. This article covers general procedures and does not present these protocols as a list of protocols offered by VPNJT.
| Item | Purpose | Where to use it |
|---|---|---|
| Subscription link | Retrieves a set of routes or a complete configuration and can be requested again for updates | The client’s remote subscription or configuration import feature |
| Single-node link | Describes one route and is not the same as a complete subscription | A node import feature that supports the corresponding protocol |
| Local configuration file | Stores the configuration as it was exported and may not include a remote update address | The client’s file import feature |
| User panel address | Manages your account, plan, subscription, and support tickets | Open it in a browser; do not use it as a subscription import |
Subscription links usually contain a token that identifies the account. Someone with the full address may be able to retrieve the configuration without knowing the login password. Treat the link as an access credential, not as a URL to share publicly.
A QR code may also encode the full subscription link. Before sharing a QR code, import-screen screenshot, or diagnostic log, check whether it includes the address, token, or node authentication details.
Get a subscription from the user panel
Start in the VPNJT user panel. Log in to get the subscription; an active plan is required to access the client download. Creating an account does not require an email address, but having an account does not mean a plan is active. If you cannot find the expected option, first check which account is signed in, the plan status, and remaining data. Do not look for a supposed universal subscription on an unfamiliar site.
- Open the user panel and sign in to the account you want to use.
- Check the plan status. Review the information in Account Overview to make sure you are not signed in to a different account.
- Follow the panel’s current instructions to find the subscription option. Choose a format compatible with your client, then copy the complete address. The option name and layout may vary in the interface.
- Go to the client download page to get the client and instructions for your operating system.
- Paste the address into the client’s subscription import field. Do not paste it into a node server address field or submit it to a search engine.
If the panel offers multiple import options, choose one for your target client rather than assuming the first format listed is best. A subscription may contain an encoded set of nodes or a configuration file with proxy groups and routing rules. A client that can read one format may not be able to read another.
After copying, do not delete parameters after the question mark or replace symbols in the address with full-width characters. If the clipboard content has extra spaces or line breaks at either end, remove those characters without changing the address itself. Check the panel instructions or the user guide to confirm the format; there is no need to post the actual link in a public community.
Import into clients on different platforms
The interfaces differ across Windows, Android, iOS, macOS, and Linux, but the basic process is the same: add a remote subscription, retrieve the configuration, enable it, select a route, and then turn on the proxy or tunnel. An app may label the option “Subscription,” “Configuration,” “Profiles,” or “Import from URL.” Follow the instructions in the app.
Windows and macOS
Add the remote address in the configuration management area, save it, and then update or download the configuration. When the route list appears, make sure the new configuration is selected, then enable the system proxy or TUN mode you need. The system proxy mainly affects apps that follow system proxy settings; it does not automatically cover all traffic. TUN mode uses a virtual network interface to handle traffic and usually requires permission. The actual scope still depends on routing rules.
Do not rely only on the taskbar or menu bar icon to determine whether you are connected. Open the target website to test it, then review the client’s connection logs to confirm that requests matched the expected rules and route. Enabling launch at startup does not enable the proxy; check these two options separately.
Android and iOS
Paste the subscription address into the client or use a compatible import option provided by the panel. The first time you connect, the system may ask for permission to let the app establish a VPN configuration. Confirm that the request comes from the client you just installed. Background activity and battery-saving settings on mobile devices may affect connection stability. If the connection drops after switching apps, first check whether the system restricts background activity for the client.
iOS clients use the system’s network extension capabilities, while Android clients often handle traffic through the system VPN interface. Neither eliminates the need to check protocol compatibility. An app may launch normally but still not support a protocol or configuration field used in the subscription.
Linux
Graphical clients can use the same remote subscription process. When using a command-line core, first check whether it supports retrieving subscriptions directly and which configuration formats it requires. Do not treat the subscription address as a startup configuration file path. The service process’s user account, configuration file permissions, DNS settings, and routing permissions may all affect the result. Follow the documentation for the client listed in the panel to install and start it.
- ✅ The client supports the subscription format and the protocols actually used in it.
- ✅ The new configuration is enabled, not merely saved in the configuration list.
- ✅ A route is selected, and the system proxy or tunnel is enabled as needed.
- ✅ The target request follows the expected rules and is not mistakenly sent through a direct connection.
- ❌ Do not assume that “import successful” means every app is using the proxy.
How often should you update a subscription?
Updating a subscription retrieves the remote configuration again; it does not renew your plan or add data. An update can fetch the latest configuration after routes change, authentication details are modified, or the service publishes a new configuration. If nothing has changed and your connection works, there is no need to update repeatedly to “improve speed.” Updating does not improve the quality of your local network.
If your client supports automatic updates, you can enable the feature according to its instructions. The interval depends on the service configuration, client capabilities, and your needs; there is no fixed interval that suits everyone. Update manually when route names change, an old route keeps failing, or you receive a configuration update notice, then check the result.
VPNJT monthly subscriptions reset data each month on the activation date, not when the client last updated. The price difference for a mid-cycle upgrade is converted into remaining days. Data add-ons are used until depleted and never expire. Tapping “Update subscription” does not reset monthly data early or replenish a depleted data add-on.
After updating, check the selected route and rules. If the remote subscription includes a complete rules configuration, local changes may be replaced during an update. If the client only updates the node list, its rules may be kept separately. First confirm what the app updates, then use its supported override or custom rules feature. Avoid editing a remote configuration that updates automatically.
How to decide: Update the subscription when the configuration changes, check your allowance in the panel for data issues, and review rules for routing issues. Separate these problems so repeated updates do not hide the real cause.
Troubleshoot failed imports and connections
First distinguish a “subscription fetch failure” from a “route connection failure.” The former occurs while retrieving the configuration and may be related to the address, access credentials, network, or format. The latter happens after the configuration has loaded and calls for checking the route, proxy mode, and target app. The troubleshooting steps are different.
Download failed or no configuration found
Copy the address again from the panel and make sure you did not copy a login page link. Check the account and plan status, then verify the client format. If the response is a web page rather than a configuration, authentication may have failed, the wrong option may have been used, or the request may have redirected to a login page. Do not turn off certificate verification to work around an error. Check the system time, address source, and network environment instead.
Some clients use the current proxy when fetching a subscription. If the current route is no longer working, the update request may fail too. Check in the client’s instructions whether subscription requests use a direct connection or a proxy. Retrieve the configuration again on a network that can access the panel. Avoid changing all network settings at once; otherwise, it will be difficult to tell which action made a difference.
A route is listed, but the target website will not open
Confirm that the current configuration is enabled and a route is selected, then check whether the request reaches the client. If an app does not follow the system proxy, it may need its own proxy settings or a suitable tunnel mode. Routing rules decide whether to connect directly or use a proxy based on conditions such as domains and addresses, so global mode and rule-based mode may produce different results.
DNS resolution also needs to be checked. With some configurations, web requests use a proxy while domain names are still resolved by the local network, which can cause resolution differences or a risk of DNS leaks. Enabling TUN does not by itself prove that DNS is handled as expected. Check the client’s DNS settings and connection logs rather than relying only on a changed exit address.
A subscription is a way to distribute configuration; it does not determine whether a route uses an IEPL dedicated line, a relay, or a direct connection. Dedicated lines and relays refer to how the service organizes its network paths, while direct connections typically connect from the user’s network to the target proxy server. You cannot determine the route type just by looking at the subscription address, and a successful import does not guarantee access to streaming regions or AI tools.
If the issue persists, submit your operating system, client name, error message, and failure stage through a support ticket. Hide the subscription address and authentication fields in screenshots. Do not attach the full configuration publicly.
Reset and clean up after a link leak
If the full subscription link has been posted on a public page, shared document, or untrusted tool, treat it as a leaked credential. Deleting the original message can limit further distribution, but it cannot recall copies that others have already made. Changing the account password may not invalidate the subscription token; the two may use separate authentication mechanisms.
- Return to the official user panel and check whether it offers a subscription reset or token replacement. If there is no clear option, ask how to proceed through a support ticket rather than guessing what a button does.
- Confirm the scope of the reset, including whether the old subscription address will stop working and whether downloaded node authentication details will also change. Replacing only the retrieval address may not revoke an old configuration that has already been obtained.
- After getting a new link, replace the remote subscription address on each of your devices and update it. Clients still using the old address will not learn about the new one automatically.
- Remove old configurations, exported files, QR codes, and shared clipboard records. If the old and new subscriptions are both present, make sure the new configuration is the one enabled.
- Check the data records provided by the panel and contact support if you find usage you cannot explain. Do not conclude that someone used the account based on a single change in data usage.
VPNJT has no limit on the number of devices connected at the same time. You can configure your own devices as needed, but that does not mean subscription links should be shared publicly. When using multiple devices, share the link only among trusted devices and avoid storing it in shared notes with broad access or online conversion tools.
Beginner’s checklist: You can get a subscription from the official panel, enable it in a compatible client, explain which rule a target request follows, and know to confirm that old credentials are invalid after a leak. These checks are more useful than simply seeing a list of routes.