A VPN subscription link is usually a configuration URL that includes account credentials. A client accesses the URL to retrieve server nodes and related settings, then lets you choose a route to connect through. It isn’t a regular webpage or the subscription plan itself. Understanding the difference helps you know where to get the link, how to import it, and what to check when something goes wrong.
How Subscription Links, Node Links, and Clients Differ
A subscription service provides routes and data allowances, the client reads the configuration and establishes a connection, and the subscription link connects the two. When you update a subscription, the client fetches the configuration from the server again. When you connect to a route, it uses the server address, protocol, and authentication details in that configuration. These are separate operations, so a successful update doesn’t necessarily mean the connection works.
A single-node link usually describes one node and may use a protocol identifier such as ss://, vmess://, or trojan://. Subscription links are commonly HTTPS URLs that return either an encoded list of nodes or a YAML or JSON configuration. Similar-looking URLs don’t necessarily contain the same format.
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are proxy protocols, not subscription file formats. A client must be able to parse the subscription content and support the protocols it uses. Support for importing remote configurations doesn’t mean an app supports every node the server provides.
Find and verify your subscription link in your account dashboard
Open the account dashboard from the service’s official website. Don’t copy supposed universal links from search ads, forwarded messages, or tutorials from unknown sources. VPNTQ keeps its account access separate from its marketing pages. To check the client and setup steps, start with the quick start guide, then open the account dashboard to find the current configuration options.
- Check your account status. Make sure your plan is active and you still have data available. Repeated imports usually won’t help if your account has no active benefits.
- Choose the client first, then the format. If the dashboard offers client-specific options, select the one for your app. Don’t mistake a generic node list for a complete configuration file.
- Copy the full URL. Keep all query parameters and tokens intact. Avoid messaging apps that may insert line breaks, spaces, or smart punctuation, and don’t copy only the portion shown in the browser.
- Use the official import method when available. If automatic import doesn’t open the app, add a remote subscription from within the client and paste in the URL.
A subscription QR code is simply another way to share the URL; it doesn’t make the URL any less sensitive. After scanning and importing it, check that the right configuration was added. Don’t post QR code screenshots in public threads or run the link through an online shortener to make it easier to share.
Choose a client and import method for your platform
The options below are common client types, not a statement that VPNTQ supports every app or protocol. Use the client and format currently recommended in the dashboard. Third-party apps can change their menus, engines, and features, so check the documentation for your installed version. Download apps from the links provided by the service or from the client project’s official release channel.
| Platform | Common client options | Import and checks |
|---|---|---|
| Windows | Mihomo GUI clients such as Clash Verge Rev | Add a remote configuration on the Profiles page, then select and enable it after updating. Check that System Proxy or TUN mode is appropriate for your needs. |
| macOS | Desktop clients such as Clash Verge Rev | Add a compatible remote configuration and grant the required permissions when prompted. Check the menu bar connection status and system proxy settings. |
| Android | Mihomo or sing-box clients that support the required protocols | Import a configuration supported by the client and approve the system VPN permission when prompted. Check app exclusions and background restrictions. |
| iOS | Shadowrocket or a sing-box client with compatible configuration support | Add the subscription or remote configuration in the appropriate format, then allow the app to add a VPN configuration when prompted. |
| Linux | Mihomo GUI client or a manually managed core configuration | Add the remote configuration in the GUI. For command-line setups, handle configuration downloads, service reloads, and permissions separately. |
Desktop: select the configuration after importing
A common issue on Windows and macOS is that the configuration downloaded but the old one is still active. After importing, check the active configuration name, node list, and proxy groups, then enable the proxy mode you need. System Proxy affects only apps that follow system proxy settings. TUN mode routes traffic through a virtual network interface, but its actual coverage still depends on routing, exclusions, and permissions.
Mobile: system permission doesn’t mean the app is connected
Android and iOS show a VPN permission prompt. Here, VPN refers to the system’s ability to route network traffic; it doesn’t mean the app uses a traditional VPN protocol. After granting permission, select a configuration and route in the client, then test with the app you want to use. Whether an iOS client is available in the App Store and what it costs depend on the app and store region. The service plan does not include fees for third-party apps.
Linux: make sure local apps use the proxy
Command-line cores and desktop clients work quite differently. Starting a core alone won’t route traffic from every terminal program. An app may need its own proxy settings, or traffic must be routed through a correctly configured TUN interface. After successfully downloading a remote configuration, reload it as described in the software documentation. Don’t leave download commands containing tokens in shared shell history or public script repositories.
Subscription update frequency and configuration storage
There’s no fixed update interval that works for every service. Follow service notices and the client’s default settings. Update manually when routes are added, node addresses change, authentication details are updated, or the list is clearly out of date. Whether automatic updates run in the background depends on the client and operating system—not just on whether the setting is enabled.
Updating a subscription usually fetches the configuration again; it doesn’t buy a new plan or reset your plan’s data allowance. VPNTQ monthly subscriptions reset their monthly data on the activation date each month. Data packages remain valid until used and never expire. Plan status and subscription updates are separate, so check the plans page for the specific allowance.
Also distinguish between updating a node provider and updating an entire remote configuration. The former may replace only the node list; the latter may overwrite rules, proxy groups, and DNS settings too. If you need to keep custom routing rules, use the client’s override, merge, or local rules features and read the relevant documentation first. Don’t maintain long-term changes directly in content that remote updates may replace.
Troubleshooting import failures and connection issues
Start with the error message. Is the file failing to download, failing to parse, or imported successfully but unable to connect? Each stage points to different causes, so repeatedly retrying the same fix is unlikely to help.
- ✅ Download timed out: Check your local network, confirm that the dashboard is accessible, and make sure the subscription download isn’t set to use a proxy route that’s already down. If needed, follow the client’s instructions to change the outbound route used for subscription requests.
- ✅ Authentication failed or access denied: Check that the link is complete, hasn’t been reset, and that your account is in good standing. The response status can offer clues, but check the server message for the specific reason.
- ✅ Format or field error: Make sure you selected a subscription format compatible with the client, and check the client version. If the browser receives a login or error page, the client may report a parsing failure.
- ✅ Nodes appear, but won’t connect: Try another available route first, then check the active proxy group, proxy mode, your device’s clock, and whether other network tools are interfering.
- ❌ Don’t delete all your configurations right away: Keep the error details and any necessary local settings. Clearing everything blindly can make recovery harder and remove useful troubleshooting clues.
If you need help, provide your platform, client name, the stage where the error occurred, and what you’ve already tried. Before sharing logs or screenshots, hide the full subscription URL, tokens, node authentication details, and sensitive account information. Contact support through the Help Center or the support ticket portal.
Connection checks, DNS, and routing rules
After importing, open the website or app you actually want to use and check the client’s connection log to see which rule matched and which outbound route it used. Routing rules may send local sites directly while routing international sites through a proxy, so seeing a local exit IP on one page doesn’t necessarily indicate a problem. Conversely, a working browser connection doesn’t prove that a terminal, game, or other app is using the same route.
Use this site’s IP check to help confirm your browser’s current exit IP, but a single IP check can’t reveal the path of every DNS request. A DNS leak occurs when lookup requests leave the intended DNS route. Check the client’s DNS mode, system resolver settings, and the browser’s Secure DNS settings together; the resolver’s location alone isn’t enough to draw a conclusion.
Encrypted DNS enabled in the browser may bypass the resolver configured in the client, or it may still travel through the proxy, depending on the rules and traffic routing setup. Check each setting separately instead of changing everything at once. Whether streaming services or AI tools work also depends on the service’s regional policies, account requirements, and risk controls. A successful subscription import doesn’t guarantee access to those services.
How to reset a leaked link
If the full link was posted publicly, submitted to an unknown online conversion site, or shared in a screenshot, treat it as a compromised credential. Online subscription converters may have access to the original link and the node authentication details it returns. Unless you understand and trust how a converter handles that data, use a compatible format provided by the service instead.
- Look for a reset or revoke option in the official dashboard. Confirm that the action applies to the subscription credentials. If you can’t find it, contact support; changing the local configuration name won’t help.
- Check what happens to the old link. Some systems reset the link by revoking download access but don’t rotate node credentials that have already been downloaded. Check the service instructions to see whether you also need to change node authentication details.
- Update every device still in use. Replace the old link with the new one, fetch and enable the configuration again, and check that automatic update tasks no longer reference the old URL.
- Remove public copies and check usage. Delete visible links and QR codes, and watch for unusual data usage. Deleting a post doesn’t invalidate credentials that have already been copied; revoking them is what matters.