What a Subscription Link Is: A Configuration URL, Not a Plan
What is a VPN subscription link? It’s the address a client uses to retrieve route configuration. The client reads the address and parses the configuration supplied by the service into selectable routes. Your plan determines which resources are available to your account; the subscription link delivers the relevant configuration to your client. Copying the link does not activate a plan.
A subscription address often looks like a regular URL, but its path or query parameters may contain credentials. When a client requests the address, the server uses it to return configuration data. This may be an encoded list of routes or a client-specific configuration file, depending on the server and client. It may not display as a normal webpage in a browser.
A subscription address is different from a share link for a single node. The former typically retrieves and refreshes a collection of routes; the latter usually describes one route and may not stay in sync with later changes. A QR code is simply another way to represent an address or configuration. Importing it by scanning does not change its access rights or sensitivity.
Key takeaway: Treat a subscription link as a configuration source that contains access credentials. It is not a client download link, proof of payment, or an ordinary URL to share publicly.
Get It from Your Account Dashboard: Check Your Plan and Client First
To use VPNQI, sign in to the account panel to get your subscription. VPNQI does not require an email address; you can create an account with a username and password. You need an active plan to access the corresponding client download link. Don’t paste a marketing page URL into your client’s subscription field.
Before retrieving the address, check which client, operating system, and import format you’ll use. Windows, macOS, iOS, Android, and Linux each have different client environments, and different apps on the same system may accept different configurations. The same operating system does not guarantee the same subscription format, proxy permissions, or import process.
- Sign in to your account and check your plan status and remaining data. For billing details, see the plan details.
- Get the relevant information from the client downloads section of the panel, then check the client documentation and supported subscription formats.
- Copy the subscription address that matches your client. If the panel offers format options, choose the one your client requires rather than guessing based on the protocol name.
- Import the address directly into the intended client. Don’t send it through public chats or third-party web services first.
Panel button labels may change as the interface evolves. Look for the feature to retrieve a subscription address or import a configuration, rather than a specific button label. If you can’t find it, check through a support ticket. Don’t use replacement addresses from unknown sources.
Client Import: From Link to Working Configuration
A typical import flow starts in the client’s configuration, subscription, or profile management screen. Choose the option to import from a URL, paste the complete subscription link, then save it and retrieve the configuration. Some clients save the URL separately from downloading its configuration. After saving, make sure the route list actually appears—not just an empty profile name.
Keep the full path and query parameters when pasting. Avoid including trailing punctuation, line breaks, or spaces, and don’t remove parameters just to make the address look simpler. If an app accepts single-node share links, don’t assume it can also parse a regular subscription URL as a single node.
After importing, select the new configuration and enable the connection. The client may ask to create a system network extension, virtual network interface, or VPN configuration; review the system prompt and confirm its source and purpose. System proxy mode mainly affects apps that follow system proxy settings. TUN and similar modes route traffic through a virtual network interface, but coverage still depends on rules, routing, and platform permissions.
- ✅ The subscription address is saved, and the client has successfully retrieved the configuration.
- ✅ The newly imported configuration is active—not an old or empty one.
- ✅ A route is selected, and proxy or network-routing mode is enabled as required by the client.
- ✅ Test with the intended app and check that regular internet access still works.
On macOS and iOS, check network extension or VPN configuration permissions. On Windows and Linux, check system proxy, routing, and app-specific proxy settings. On Android, check VPN permissions and which apps are included. Avoid running proxy tools with overlapping roles, as they may override each other’s settings. For more setup guidance, see the getting started guide.
How Often Should You Update? Follow Configuration Changes, Not Your Data Cycle
Updating a subscription means requesting the address again to retrieve the routes and configuration currently provided by the server. This may add or remove routes, change connection parameters, or adjust rules, but it only syncs what the server actually returns—it won’t automatically fix every network issue. Some clients update only the node list, not local rules or scripts; check how your client handles configuration.
There is no fixed update interval that works for every client. After importing for the first time, confirm that the update succeeds. Update manually when a service announcement mentions configuration changes, an old route stops working, or you renew a plan. If your client supports automatic updates, enable the feature according to its instructions. Don’t use frequent refreshes as a substitute for troubleshooting; some services may limit request frequency.
| Action or event | What changes | What not to confuse it with |
|---|---|---|
| Update subscription in client | Retrieve the current configuration from the server again | Does not restore used data or extend a plan |
| VPNQI monthly plan data reset | Data resets monthly on the activation date | Not based on when you tap Update in the client |
| Mid-cycle VPNQI plan upgrade | The upgrade price difference is converted into remaining days | Plan changes are confirmed on the account side, not determined by the local configuration name |
| VPNQI data package | Use it whenever you need; it never expires | The monthly plan’s data reset rules do not apply to data packages |
After updating, check the client’s update timestamp or status message, then review any changes to the route list. If the client retains an old cache, seeing routes in the interface doesn’t prove that this request succeeded. Check account status, configuration retrieval, and the actual connection separately.
Import Errors vs. Connection Failures: Troubleshoot Separately
No Configuration? Check the Address and Response
A “format error” usually means the client couldn’t parse the returned content as expected; it doesn’t necessarily indicate a route problem. Possible causes include an incomplete address, an incompatible subscription format, or a response containing a login page or error message. A webpage opening in your browser doesn’t prove the client received valid subscription data.
Copy the address again from the panel and check your account and plan status. Then make sure your local network can reach the subscription domain. If the client reports a certificate error, check your system clock and client version, and verify the address through the official panel. Don’t disable certificate verification to dismiss the warning, and don’t post full error logs publicly—they may contain subscription credentials.
Routes Listed but No Connection? Check the Connection Path
A successful import only confirms that the configuration was parsed. Connecting also depends on protocol support, server reachability, system permissions, DNS, and routing rules. First check whether the client is actually running. Then try another route in the configuration and compare the results. Finally, check whether the rules send the target app’s traffic direct or block it.
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC are different protocol names, not synonyms for subscription file formats. A client must support both the configuration format and the protocols and transport methods it uses. Recognizing a protocol name does not mean the client supports every related parameter. These protocols are mentioned here to explain compatibility; this does not mean VPNQI claims to support them all.
Similarly, IEPL, transit, and direct connections describe route paths or network arrangements. They are separate from whether a subscription address can be parsed. A dedicated-line label does not replace an actual connectivity check or guarantee access to any particular website. For background, see the protocol reference.
Traffic Routing and DNS: A Connection Icon Isn't the Final Check
Even after the client shows a connected status, test the app you actually want to use. Rule-based mode directs traffic according to factors such as domain, address, or app. If the target is routed directly, access may not behave as expected even when the proxy route works. Temporarily changing modes can help identify a rules issue. Once confirmed, restore a suitable everyday configuration rather than relying indefinitely on unchecked global routing.
A DNS leak occurs when domain lookups that should follow the proxy policy are sent through an unexpected resolution path. Possible causes include the client’s DNS settings, the system resolver, encrypted DNS in the browser, or routing rules. Enabling a proxy does not automatically send every domain lookup through the same path, and remote DNS resolution does not make browsing completely anonymous.
To troubleshoot, first understand how your client handles DNS, then check for separate browser and system settings. Don’t treat a resolver name shown by a testing website as conclusive; assess it alongside your expected exit route, rules, and query path. VPNQI’s privacy policy is not to log activity. That policy does not replace managing device permissions, choosing a trusted client, or checking local settings.
After a Link Leak: Revoke the Credential, Then Replace It on Every Device
Anyone with the complete subscription address may be able to retrieve the route configuration authorized for your account and use its data or resources. Treat it as sensitive credentials, even if it doesn’t directly contain your account password. Hiding only your username in a screenshot may not be enough: the URL path, query parameters, and QR code may still grant full access.
- Remove the link and QR code from public pages, chat attachments, and shared documents, and check for forwarded copies.
- Look in the account panel for an option to reset the subscription address or revoke old credentials. If there’s no clear option, request help through a support ticket.
- Confirm that the old address and its associated credentials are no longer valid. Generating a new address alone does not prove that the old one has been revoked.
- Replace the address in the clients on all your devices and retrieve the configuration again. Check for leftover old configurations and remove them as needed.
- Check for changes in account data usage. If your account password was also exposed, change it separately; that does not revoke subscription credentials.
Giving a complete subscription address to an online conversion tool means allowing that tool to access your credentials. Use the matching format provided in the account panel where possible. If conversion is necessary, first check the tool’s source, data handling, and ability to process locally. Don’t assume a page is trustworthy just because it says “converter.”
Whether a downloaded configuration can still connect after you change the address depends on whether the server has also revoked the associated route credentials. The key is not just to change the URL in the client, but to confirm that the old access has been withdrawn server-side.
Routine Maintenance: Keep the Official Access Point and Avoid Reconfiguring
Give each configuration a name that identifies its source. Keep the official panel link handy, but never put subscription credentials in a name or note. When using multiple devices, check the import and update results on each one. VPNQI has no device limit, but that doesn’t make it safe to share your personal subscription credentials publicly.
Before switching clients, check format compatibility and permission requirements, then import and test the configuration. When removing an old client, follow its instructions to clear leftover system proxy or network settings. Otherwise, your system may continue using old settings after the app has closed. In a support ticket, include your operating system, client name, error message, and the step where the issue occurred. Redact the address and any sensitive parameters.
Recommended order: Get the matching format from your account panel, import it, and test app access. Update when the configuration changes. If something fails, distinguish between “configuration won’t load” and “route won’t connect.” If a link leaks, confirm the old credentials are revoked before replacing the subscription on each device.