If your only goal is to make your first connection as quickly as possible, start with the Quick Start. It keeps only the essential steps, while this page explains why each step matters, how to choose between branches, what differs across platforms, and how to maintain your subscription after connecting. First-time users should read it in order; users who are already connected can jump to the relevant stage through the contents below.
This guide does not provide static installers or public subscription URLs. Clients, orders, and personal subscriptions are all obtained from the user panel. A subscription link is a connection credential and should be stored only on your own devices or in controlled backups. Do not paste it into public speed-test sites, chat groups, screenshots, or shared documents.
Service, Subscriptions & Cross-Border Routes
Understand what is delivered first
VPNQG provides a set of route subscriptions that clients can read, not a fixed exit point or a publicly downloadable file. The account stores order status; the subscription passes available routes, route names, and connection parameters to the client; the client then establishes a local connection to a remote exit. Keeping these three layers separate makes troubleshooting more direct: inability to log in belongs to the account layer, failed subscription updates belong to the delivery layer, and a successful import with no access to the target service belongs to the client or route layer.
A subscription is not the same as a single route. VPNQG covers 100+ countries / 170+ routes, and one subscription can include different regions and route types. You do not need to create a new account or place a new order every time you switch. Just update the subscription in the client and choose a route suited to your current destination. Unlimited devices means one account can cover your personal Windows, macOS, iOS, Android, and Linux devices, but subscription credentials should still be managed by the account holder to avoid losing track of unusual activity after they spread.
What route names tell you
Route lists usually identify both the destination region and the path type. The destination region determines the exit location, while the path type describes how data reaches that exit. IEPL dedicated lines focus on cross-border path design and peak-time stability; relay routes pass through an intermediate entry point before reaching the target exit; direct routes travel straight from the local network to the target node. None is universally best outside its context. For nearby services, matching the region is often more important than chasing a distant exit; when the local carrier has a poor path to an entry point, a relay route may be smoother.
Define your goal before choosing a route instead of selecting every capability at once. For ordinary browsing and research, prioritize stability, geographic distance, and reliable DNS resolution. Streaming also requires a matching content region; see the Streaming Access Guide. AI Tools depend more on whether the exit region is supported by the target service and whether the exit remains stable during a long connection. Games and real-time calls are more sensitive to jitter and packet loss. Continue with the Latency and Packet-Loss Testing Guide, rather than judging a route from a single page-load speed.
Where the client fits in the system
The client takes over part of the system's traffic and decides which requests use accelerated routes according to its current mode. Common modes include system proxy, rule-based, and global modes. A system proxy mainly affects apps that follow system proxy settings; rule-based mode directs traffic by domain or address; global mode hands a wider range of connections to the client. For first-time use, keep the client's default rules and avoid running multiple similar networking tools at once. They may compete for the system proxy, virtual network interface, or DNS settings, leaving you with a successful import but no access to websites.
Connections also involve the local network, DNS resolution, system time, firewall rules, and the target service itself. A client showing “connected” only means that the local connection process has advanced; it does not prove that every destination is reachable. Conversely, one inaccessible website does not prove that the entire route has failed. The right approach is to verify the basic network, subscription, route, DNS, and target service one layer at a time. The connection chapter later in this guide provides the full sequence.
Usage boundaries and information storage
Your account name, password, and subscription link serve different purposes. The account password gets you into the user panel; the subscription link lets the client retrieve routes. Neither should be made public. After a subscription link is copied to another device, that client may periodically request updates; if the credentials are later changed, the old device must be imported again. On public Wi-Fi, first confirm that the network itself can open ordinary pages before starting the client, or a captive portal may be hidden by proxy settings. For basic risks involving public networks, subscription links, and account information, also read the VPN Security Basics for Beginners.
You should now have a clear chain: the user panel stores the account and orders; the order determines current entitlements; the subscription delivers routes to the client; the client processes app traffic according to its rules; and the route sends requests to the target region. Every later chapter follows this chain. When something fails, trace it backward instead of broadly blaming the client or the route.
Plans, Data, and Usage Periods
Monthly subscriptions vs. data packs
VPNQG offers monthly subscriptions and data packs, designed for different usage patterns. A monthly subscription follows a monthly data cycle starting on the activation date, making it suitable for steady use and a predictable recurring allowance. A data pack lasts until its data is used and never expires, making it better for irregular usage, occasional access, or keeping data available for later. Consider how you use the service before comparing prices. Video, system images, and large files consume data continuously, while text pages, code searches, and light communications have a different usage profile.
Monthly subscriptions come in three defined tiers: ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Data resets monthly on the activation date, and mid-cycle upgrades are prorated by the remaining days. The activation date is key to understanding the cycle: do not assume every account refreshes on the same calendar day, and do not treat the local date shown on one client as the only source of truth. Check the user panel for remaining data and order status instead of relying on an old screenshot from a particular device.
Data packs also come in three defined tiers: ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. They last until used and never expire. The main difference from a monthly subscription is not route coverage, but how the data remains available. If your usage is concentrated in a few periods, a data pack lets you keep unused data; if you need steady daily access, the monthly reset makes budgeting easier. Full plan cards, payment options, and details are on the Plans Page. When ordering, rely on the current order information in the user panel.
| Type | Price and Data | Data Rules | Best For |
|---|---|---|---|
| Monthly Subscription | ¥9.9/month with 60GB | Resets monthly on the activation date | Light, ongoing use |
| Monthly Subscription | ¥18/month with 250GB | Resets monthly on the activation date | Regular multi-device use |
| Monthly Subscription | ¥28/month with 500GB | Resets monthly on the activation date | Higher data needs |
| Data Pack | ¥158/300GB · ¥358/1000GB · ¥658/3000GB | Lasts until used; never expires | Irregular usage or backup data |
How to estimate the right tier
When estimating data needs, do not simply convert “hours online per day” into a number, because different activities consume data at very different rates. A better method is to list your main tasks: Do you often watch high-resolution video? Sync large files? Run automatic backups on multiple devices? Download development dependencies or system updates? Then check the data statistics built into your operating system and apps, distinguishing route traffic from local-network transfers. Leave some headroom on your first selection; there is no need to maintain the highest tier for one occasional large download.
Unlimited devices does not mean data is calculated separately for each device. When multiple devices use the same subscription, their network activity draws from the same account allowance. Background tasks are easy to miss: desktop cloud sync, system updates, photo backups, autoplay video, and app-store downloads may start automatically after connecting. If data usage does not match your active use, inspect background tasks on each device first, then check whether the client has remained in global mode. Rule-based mode usually makes data usage easier to control by handling only the destinations that need it.
Upgrades, renewals, and refunds
When a monthly subscription is upgraded mid-cycle, the price difference is prorated by the remaining days. An upgrade is therefore not simply a second allowance added on top; the remaining order period is part of the calculation. Before making the change, check the current plan, remaining status, and target tier in the panel. After submitting, refresh the order page to confirm the result. Do not click repeatedly on the payment page or submit the same change from multiple devices. If the page does not update promptly, keep the payment record and recheck from the orders area.
VPNQG offers a 60-day no-questions-asked refund. This policy reduces uncertainty when choosing for the first time, but routine troubleshooting should still begin by preserving essential details such as the current plan, payment method, affected platform, and route type. Payment methods are Alipay / WeChat Pay / USDT. Check the order amount and panel status before paying. Do not transfer funds through temporary links sent in chat, and never include your account password or subscription link in a payment note.
Final checks before ordering
When confirming a plan, check the type, data allowance, cycle rules, and payment method in that order. Monthly subscribers should remember that data resets monthly on the activation date; data-pack users should confirm that they need an allowance that lasts until used and never expires. If you already have an active plan, first decide whether you are renewing, upgrading, or adding a data pack so that different actions are not mixed together. Once these checks are complete, move on to the account and ordering process for a smoother client import later.
Account Creation and Order Confirmation
What to prepare before creating an account
VPNQG does not require an email address; a username and password are enough to create an account. This reduces the number of registration steps, but it makes credential management more important. Choose a username you can recognize without making it identical to a public social account. Store the password separately and do not reuse it on other sites. Because account creation does not rely on an email address, save your account details in a trusted password manager immediately after creation rather than assuming you can recover them later.
Enter the user panel through the site's navigation, the plans page, or an on-site link provided in this guide. The browser address should remain on the vpnqg.com domain. The registration page only requires username- and password-related actions. If a browser extension, system prompt, or another overlaid page asks for additional information, verify where the request came from first. After registration, do not close the page immediately. Confirm that you are in the account area and can see entries for plans, orders, client downloads, or subscriptions.
Choose a plan and create an order
In the user panel, open the plans area and compare the type and tier selected in the previous chapter. Monthly subscriptions are ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB; data packs are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Before submitting, check again whether you selected a monthly subscription or a data pack. Do not focus only on the data figure and overlook the cycle rules. Monthly data resets on the activation date; data packs last until used and never expire.
After an order is created, check its status and amount first, then choose Alipay / WeChat Pay / USDT to complete payment. The payment page and order page have different roles: the payment page handles the transaction, while the order page records the service status. After paying, return to the orders area and confirm the status instead of relying only on the payment provider's success page. If the provider shows completion but the order has not updated, refresh the order list or re-enter the panel rather than creating the same order again.
When using USDT, verify the order information currently shown in the panel and follow the page's process. Do not guess payment details or use forwarded screenshots instead of the panel. When using Alipay or WeChat Pay, likewise start the payment flow from the current order. Whichever method you use, never send your login password, subscription link, or full client configuration to a payment channel. A payment receipt verifies a transaction; subscription credentials establish a connection.
Post-order checks
After the order status updates, confirm the current plan name and active status first, then check whether the subscription entry is available. Next, verify that the data information in the panel matches the selected plan type. Monthly subscribers should check the activation date and monthly reset rules; data-pack users should check the remaining allowance rather than looking for a fixed monthly refresh date. If you upgraded an existing monthly subscription, confirm that the panel prorated the mid-cycle price difference by the remaining days instead of treating an old screenshot as the current status.
An account can be used on an unlimited number of devices, but it is not advisable to log in to the user panel directly on every device. A safer approach is to manage orders and subscriptions on one controlled device, then import the subscription into your other personal clients. This reduces password exposure and makes future subscription changes easier to handle consistently. Public computers, borrowed devices, and browsers you do not control are not suitable for long-term account management.
Common account-layer issues
When login fails, first confirm that you entered your username rather than a plan name. Also check whether your password manager filled in credentials for another site. Watch for leading or trailing spaces when copying the username, and verify keyboard layout and capitalization when entering the password. If the browser has kept an old page open for a long time, reopen the user panel and sign in again. Do not try to solve an account problem by repeatedly changing client settings; client import and panel login are separate chains.
If an order is complete but no subscription entry is visible, leave the current account area, sign in again, and check that you used the correct username. When different accounts have been created on multiple devices, it is easy to pay from one account and look for the order in another. Organize troubleshooting around the username associated with the order. When submitting a ticket, describe only the order status, time of occurrence, payment method, and reproducible steps. Do not submit your password or full subscription link.
Moving from the account stage to the subscription stage
Proceed to the next chapter to copy the subscription only after the order status, plan type, and current account have all been confirmed. This prevents “entitlement not active yet” from being mistaken for “client incompatibility.” If you installed a client before the order was complete, having no personal subscription to import is normal. Once ready, stay signed in to the user panel and open the subscription area on a controlled device.
Get, Import, and Protect Your Subscription
What is a subscription link?
A subscription link is the entry point the client uses to retrieve a route list and connection parameters. It is usually a long URL containing credentials tied to your account entitlements. Once saved by the client, it can retrieve routes again when needed, so you do not have to enter 170+ routes manually. A subscription link is not a public webpage or a promotional URL. Anyone who obtains the complete address may be able to try using the associated subscription in a client, so protect it almost like a password.
When obtaining a subscription from the user panel, use the panel's copy or client-import option. Do not manually cut off part of the URL or guess the subscription path from the browser address bar. After copying, paste it directly into the client's subscription field rather than routing it through an instant-messaging app. If you must transfer it between your own devices, use an end-to-end controlled password manager or the operating system's secure sync feature, then delete any temporary plaintext copy after importing.
Direct import vs. manual paste
Desktop and mobile platforms may offer two entry points: one launches the client from the user panel, while the other copies the subscription URL and creates a subscription inside the client. Direct launch is shorter but requires the browser to be allowed to open the client. Manual paste is more universal and makes it easier to see which subscription you are importing. Either way, the final result should be a subscription entry inside the client, not just a temporary route.
When creating a subscription, name it “VPNQG” or use a local name that makes its purpose clear. The name exists only inside your client and does not change the panel account. Copy the subscription URL in full, without leading or trailing spaces, quotation marks, or line breaks. After saving, run one update and wait for the route list to load before selecting a route. If the client reports an unsupported format, return to the user panel and choose the import method suited to the platform instead of editing the URL.
subscription: "https://example.com/sub?token=YOUR_TOKEN"
profile_name: "VPNQG"
mode: "rule"The snippet above only demonstrates the relationship between fields. The URL is an obvious example value and cannot establish a real connection. A real subscription must be obtained from the user panel. When placing the example in a configuration file, follow the actual format used by the client. Some clients use a graphical interface and do not require handwritten configuration. Manual editing is for users who already understand the configuration structure; first-time imports should use the client's subscription-creation interface.
Subscription updates and local cache
After import, the client stores a local route list. When routes change in the panel, the local cache may not update immediately. If route names are missing, old routes keep appearing, or a new region is not visible, start with “Update Subscription” rather than placing a new order. Updating requires a working basic network. If the current route has failed, disconnect first, confirm that ordinary connectivity works, then update the subscription and choose a route again.
Some clients support automatic updates. Even when enabled, learn where manual updating is located, because sleep states, background limits, or battery-saving policies may delay automatic tasks. When an update fails, determine whether the subscription request was never sent or whether it was downloaded but could not be parsed. The former is often related to the basic network, a system-proxy conflict, or an incomplete URL; the latter may indicate a mismatch between the import method and the client. Keeping the original error message is more useful than simply saying “it won't update.”
What to do if a subscription is exposed
If a complete subscription URL is posted publicly, entered on an unfamiliar webpage, or stored on an uncontrolled device, do not simply delete the chat message and continue using it. Open the user panel and look for an option to reset or retrieve a new subscription, then switch your own clients to the new credentials. If old devices still store the original subscription, update or re-import it on each device. Afterward, review data usage and device scope to make sure no old terminal remains connected.
Screenshots can expose subscriptions too. Client detail pages, QR codes, import dialogs, and logs may show the full URL or its credentials. When submitting a ticket or asking someone for help, cover the subscription body and retain only the error text, client platform, steps taken, and route type. A link that looks like an ordinary URL should not be treated as non-sensitive text.
Status before configuring the client
By the end of this chapter, the client should contain an updatable VPNQG subscription entry with visible regions and route types, not just unsaved text. Do not change DNS, system proxy, rules, and virtual network interfaces all at once. The next chapter covers the minimum viable setup for each platform. Enable advanced features one at a time only after the basic connection works, so every change has a clear cause.
Client Import on Five Platforms
VPNQG supports Windows / macOS / iOS / Android / Linux. Interface labels differ by platform, but the workflow is the same: obtain the platform-appropriate client and subscription entry from the logged-in user panel, install it, create a subscription, update routes, choose a node, enable the connection, then return to the browser for verification. Clients should be obtained from the signed-in panel; marketing pages do not provide static installers or public personal subscription URLs.
| Platform | Import Focus | System Permissions | Common Conflicts |
|---|---|---|---|
| Windows | Update routes after saving the subscription | System proxy or virtual network interface | Old proxies, other network tools, firewall rules |
| macOS | Make sure the client remains in an accessible location | Network configuration permission | Duplicate proxies, restricted background access |
| iOS | Choose the mobile import method through the panel | Add VPN configuration | Old configurations, regional availability limits |
| Android | Remove excessive background restrictions on the client | Establish a VPN connection | Battery-saving policies, Private DNS, other VPNs |
| Linux | Confirm the proxy scope for desktop sessions and command-line environments | Grant permissions according to the client mode | Environment variables, service processes, and desktop proxy settings differ |
Windows: From Subscription to System Proxy
On Windows, sign in to the user panel and open the client-download area to obtain the VPNQG client, then copy the subscription or launch the import from the subscription area. Open the client after installation and do not run another similar tool at the same time. Create and save the subscription, update it, and confirm that the route list appears. Then choose a nearby route or one matching the target region and enable the system proxy or the client's recommended default mode. For the first test, keep rule-based mode enabled so unrelated downloads and system updates do not all use the route.
If the browser connects but a desktop app does not, first check whether the app follows the system proxy. Some apps use their own network settings and require you to select “Use system proxy” inside the app or restart it before the setting is read. If no apps can connect, close the client and check Windows proxy settings for a leftover address, then start the client again. Incorrect system time, a faulty network adapter, or firewall restrictions created for an old client can also cause a new connection to fail.
For a more complete desktop walkthrough, read Windows: From Installation to Launch at Startup. Configure launch at startup only after the first connection has been verified. Otherwise, an untested configuration will take over the network at every system login and make troubleshooting harder.
macOS: Network Authorization and Background Operation
After installing the macOS client, import the subscription from the user panel and update the routes. When establishing the first connection, macOS may ask for permission to add a network configuration. Confirm that the request came from the VPNQG client you just opened, then complete the authorization in the system dialog. Return to the client, choose a route, and do not create duplicate configurations from both System Settings and the client. If the menu bar shows a connection but the browser does not respond, disconnect first and check for settings left by another tool in the system proxy.
After desktop sleep, the connection status may become inconsistent between the system and the client. If access is abnormal after waking, disconnect and reconnect once, then update the subscription; there is no need to delete the entire client. Some apps cache the network environment at launch, so reopen them after switching routes. If the issue occurs only under one user account, compare that account's proxy settings, login items, and network-extension permissions rather than changing the subscription on every device.
iOS: Regional Availability and Configuration Authorization
iOS users should first check the current acquisition method in the user panel, then install the client and import the subscription. The App Store region may affect client availability; see iOS Client Selection and Regional Availability for details. During import, prefer the mobile entry provided by the panel. If the browser asks whether to open the client, verify the app name and current action before continuing.
The first connection will request permission to add a VPN configuration. After approval, the system status area will show the connection state. If the import succeeds but the route list is empty, return to the client and update the subscription manually. If the connection drops immediately, check System Settings for another old configuration that is still taking over the connection. iOS background policies may pause a client that has not been used for a while; when returning to it, open the client and refresh its status before accessing the target service.
Android: Background Policies and Connection Conflicts
The Android installation and import process also starts in the user panel. After saving the subscription, update the routes, choose a node, and accept the system prompt to establish a VPN connection. Device manufacturers manage background processes differently. If the connection stops frequently when the screen is locked, allow the client to keep running in the system's battery and background settings. Limit the change to this client; there is no need to disable the system's overall security or power-saving features.
On Android, normally only one VPN-type connection should control the network at a time. If the connect button does nothing, disconnect other similar apps and clear old connection states first. If ordinary pages work but DNS resolution fails, temporarily restore the system default Private DNS setting to check for a custom-resolution conflict. After confirming the basic connection, restore your preferred DNS strategy if needed, changing one setting at a time.
Linux: Desktop Proxy and Process Environments
The most common difference on Linux is that desktop apps, terminal programs, and system services may read different proxy settings. After obtaining the client and subscription from the user panel, complete the import in the graphical interface or client itself, update, and choose a route. If the browser works but terminal tools do not, check whether terminal processes inherited the correct environment. If the terminal works but desktop apps do not, check the system proxy for the desktop session. Do not change system-wide forwarding rules for a single program.
When verifying from the command line, first check whether old proxy environment variables are present:
env | grep -i proxy
curl -I https://example.comThe example command only checks the current environment and a basic HTTP response. example.com is an example domain and not a VPNQG service address. If old environment variables are found, clear them in the current terminal session and test again before deciding whether to edit shell configuration files. Background service processes do not automatically inherit desktop-session settings; configure networking according to the service itself.
Connection Verification and Layered Troubleshooting
Build a repeatable verification sequence
Start connection verification with the most basic conditions. Disconnect the client and confirm that the current network can open ordinary pages. Then start the client, choose one clearly identified route, open a new browser window, and visit a familiar destination. Test a specific app, streaming service, or long-lived connection only afterward. Change one condition at a time. This shows whether the issue existed before the connection started or was introduced by the route, rules, or app itself.
Do not use one website as your only test. The target site may be under maintenance, restrict the current region, or retain an old session. A safer approach is to test an ordinary webpage, the target service, and another type of network application separately. If ordinary pages all fail, check the client and system network first. If ordinary pages work but the target service fails, check region matching, login state, and target-service rules. If only one app fails, check whether it uses the system proxy.
Check the exit region and DNS
After switching routes, use a trusted exit-information page to confirm whether the region changed, but do not paste your personal subscription into a testing site. Exit checks only require the browser to open a page normally. If the displayed region does not match the selected route, confirm that the client is actually enabled, that the current mode covers the browser, and that the browser is not using a separate proxy or extension. Close old tabs and open them again after switching routes to reduce the effect of connection reuse and caching.
DNS issues often appear as unresolved addresses, slow access to some domains, or a browser message saying that the server cannot be found. First compare domain access with basic network connectivity and see whether both fail. Do not stack multiple custom DNS settings immediately. Restore the client's defaults, disconnect other network tools, reconnect, and test again. If the issue occurs only on one network, it may involve captive-portal authentication, resolution policies, or an IPv6 path. Compare with another basic network.
The shortest troubleshooting path when you cannot connect
First check the order and subscription: Is the plan in the user panel active? Can the client update the subscription? Does the route list appear normally? Second, check local conflicts: Are other proxies or VPN-type tools running? Is an old address left in the system proxy? Is the firewall blocking the current client? Third, try another route in the same region with a different path type to determine whether the issue affects one route or all routes. Fourth, compare another basic network, such as switching from the current Wi-Fi to another available network.
If every route fails on one device but the same subscription works on another, the issue is usually concentrated in that device's configuration. Do not reset the subscription or buy the plan again. Check client permissions, system time, proxy settings, network extensions, and background restrictions. If every device fails on the same basic network but works after switching networks, check the local router and network-side policies first. If only one route fails, update the subscription and switch routes while keeping the other available paths.
Connected, but speed is unstable
Separate sustained throughput, latency, jitter, and packet loss when investigating speed. A page loading quickly does not mean a large transfer will remain stable, and a fast download does not guarantee smooth real-time calls. Close background sync and concurrent downloads, use a route near the target region as a baseline, then compare IEPL dedicated lines, relay routes, and direct routes. Test on the same device, basic network, and target to avoid mistaking a network-environment change for a route difference.
When performance fluctuates during peak hours, update the subscription first and test other path types in the same region. Use an IEPL dedicated line as an initial stability baseline; a relay route may avoid some local path issues, while a direct route helps assess the direct quality from the local network to the target node. See the Routes Page for the full route range and type descriptions. Do not permanently lock in a route based on one speed test; sustained performance in real use is more meaningful than a momentary peak.
Streaming and AI Tools issues
If a streaming service opens its homepage but cannot play content, first confirm that the account, content region, and route region match. Then clear the old session and sign in again. For regional catalog differences and access stability, see Disney+ Regional Differences and Stability Comparison. After switching regions, close the original playback page so the old exit is not reused. Reduced quality may also result from basic-network throughput, device decoding, or the app's adaptive behavior.
If an AI tool shows a login loop, interrupted responses, or a regional notice, first lock in one route that supports the target region instead of frequently switching exits during the session. Long conversations, file uploads, and streamed responses depend more on connection continuity. If ordinary pages work but long responses are interrupted, compare different route types and disable browser extensions that alter request paths. Investigate account restrictions or target-service status only after confirming that the basic route is stable.
When to submit a ticket
If you still cannot locate the issue after updating the subscription and comparing routes, devices, and networks, open the ticket area from the user panel. Include when the issue began, which platform is affected, whether all routes are affected, whether changing networks made a difference, and which steps you have already tried. Clear layered information reduces repeated checks. Do not submit only “it doesn't work,” send screenshots without context, or include your account password and an unredacted subscription URL.
Routine Maintenance, Data, and Renewals
Build a stable update routine
Routine use does not require frequent client reinstalls. More effective maintenance is to open the client periodically, confirm that the subscription can update, check that frequently used routes remain listed, and reverify the connection after changing networks. If a route name changes or a route is temporarily unavailable, update the subscription before drawing conclusions. Delete-and-reimport should be a later option because it also removes local selections and some custom rules, increasing recovery effort.
The client-download entry is in the user panel. When changing devices or reinstalling, sign in to the panel again to obtain the VPNQG client instead of using installers from unknown sources. After installation, copy your personal subscription from the panel again. When an old device is no longer in use, sign out, delete the subscription entry, and remove the stored client configuration, especially before transferring or returning the device.
Manage data across devices
Unlimited devices make it easy to switch between Windows / macOS / iOS / Android / Linux, but data management remains account-wide. On desktops, watch large sync jobs, development downloads, and video tasks; on mobile devices, watch photo backups, app updates, and hotspot sharing. When data usage changes unexpectedly, pause background tasks on each device one by one, then check whether any terminal has remained in global mode for a long time. Simply closing one browser is not enough to confirm that a device has stopped generating traffic.
Monthly subscription data resets monthly on the activation date. Follow the cycle shown in the panel rather than inferring it from the calendar month. The three monthly tiers remain ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. If usage stays close to the current tier, evaluate an upgrade in the panel; mid-cycle upgrade differences are prorated by the remaining days. For occasional high-data tasks, compare the data packs: ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. They last until used and never expire.
Checks before and after renewal
Before renewing, confirm the username currently signed in, the existing plan, and the intended action. If you have multiple accounts, do not rely only on the browser's automatic sign-in. Open the orders area, verify the amount, and then use Alipay / WeChat Pay / USDT. After payment, return to the panel to confirm the order status and entitlement changes, then update the subscription in the client. Renewal normally does not require reinstalling the client; if the subscription URL remains valid, updating it should sync the current routes.
If the order status has changed but the client still shows old information, manually update the subscription, close and reopen the client, and check whether multiple subscriptions with the same name were imported. Multiple subscriptions are a common source of confusion: you may update the new entry while continuing to select routes from the old one. Give the active subscription a clear name, then delete unused entries after confirming them.
System updates and network changes
Operating-system updates may reset proxy permissions, network extensions, or background policies. If the connection becomes abnormal after an update, first check that the client still has the required permissions, then disconnect and reconnect instead of resetting the account. On Android, check whether background limits returned to their defaults. On iOS and macOS, confirm that VPN or network configurations remain allowed. On Windows, check the system proxy and network adapter. On Linux, compare the desktop session with the service environment.
After switching to a different router, corporate network, campus network, or public Wi-Fi, first verify the basic network without the client enabled. For networks requiring web authentication, complete the captive-portal page before establishing the route. If an old proxy blocks the portal, temporarily disable the client and system proxy, complete authentication, and restore them afterward. Networks may handle UDP, IPv6, DNS, and long-lived connections differently, so “works at home, fails elsewhere” does not automatically indicate an account problem.
Credential rotation and device sign-out
When a device is lost, a subscription is shared accidentally, or account information may be exposed, update the relevant credentials promptly. After changing the account password, save the new record and sign out of uncontrolled browsers. After changing subscription credentials, re-import or update the subscription on each of your clients. Changing only the account password may not change a subscription already saved in a client, so handle the two credentials separately.
When retiring an old device, stop the connection, delete the subscription, sign out of the user panel, remove the client configuration, and then clear local data according to the device-management process. If the device cannot be accessed, update the subscription credentials from the panel and re-import them on devices you still control. Monitor data usage afterward to confirm that the old credentials are no longer being used.
Keep your own operation log
Record only what is necessary: store the account username in a password manager, use the panel as the source of truth for plans and orders, note the platform and local subscription name in the client, and keep the route region and type in troubleshooting records. Do not store the full subscription URL in ordinary notes. This makes recovery faster when changing devices and helps you explain exactly what changed without repeating the same experiments.
Advanced Route Selection and Rules
Rule-based mode vs. global mode
Once the basic connection works, choose a mode based on the task. Rule-based mode lets the client route traffic by domain or address. It suits everyday use and keeps local services, LAN devices, and traffic that does not need an accelerated route on their normal paths. Global mode sends a wider range of traffic through the current route, which is useful for briefly checking whether an app is missing the proxy, but it also consumes data on background sync and unrelated downloads. Know the task before switching modes and restore your everyday settings afterward.
More rules are not necessarily better. As custom rules accumulate, domain matching, app-level resolution, and the client's default rules may override one another. Start with a specific goal, such as keeping one work service in a fixed region, rather than forcing broad domain ranges through one route. Test both the target service and ordinary pages after each addition and record the rule's purpose. If something breaks, disable the most recently added rule before deleting the entire subscription.
Choose route types by task
IEPL dedicated lines, relays, and direct routes represent three different path structures. For tasks sensitive to peak-time stability, test an IEPL dedicated line first. When the direct path from the local network to the target region is poor, compare relay routes. When you want to observe the most direct network behavior, test a direct route. The target region still matters; a distant “premium route” is not a substitute for regional matching. View route details and regional coverage together on the Routes Page.
When creating your own route-selection order, keep one primary route and a backup in the same region. Use the primary for everyday browsing, development, or communications, and switch to the backup during maintenance or when the basic network changes. Avoid jumping across multiple regions in one session, because login systems, streaming services, and AI Tools may treat frequent exit changes as an unusual environment. Keeping the region fixed and reducing unnecessary switching is usually more stable than chasing momentary speed.
Per-app routing and LAN exceptions
If the client supports per-app rules, include only apps that genuinely need international routes and leave local file sync, printing, and LAN administration on their normal paths. Before configuring this, confirm the app process name and its actual network components. Some desktop programs send requests through helper processes, so selecting only the main process may not cover them. After setting the rule, test app login, file transfers, and updates separately instead of checking only whether the home page opens.
When LAN devices become inaccessible, first check whether the client allows local-network access rather than changing the router. Printers, storage devices, and router-management pages should usually remain on a local direct path. Global mode or a virtual network interface can change the path to LAN addresses. If restoring default rules fixes access, create a clear exception for local addresses. Before changing router settings, back up the current configuration and make sure you still have a way to enter the management interface.
Browsers, terminals, and development environments
Development environments often include a browser, package manager, containers, and background services at the same time. A browser may follow the system proxy, terminal tools may read environment variables, and containers have their own network space. Verify each separately; a working browser does not mean the command line is using the route. On Linux and macOS, use environment-variable checks to find old settings. On Windows, check both the system proxy and the app's own configuration.
A proxy address, port, and subscription URL in a configuration file serve different purposes. The subscription retrieves routes; the client's local listening address lets an app hand requests to the client. Do not put a subscription URL in a field that accepts only a local proxy address, and do not treat the local listening address as a subscription import. If the client offers automatic configuration, let it manage these parameters. When setting them manually, record where you made the change so you can restore the settings after closing the client.
Strategies for streaming and long-lived connections
For streaming, choose an exit by content region first, then compare stability among routes in that region. After switching routes, reopen the app or browser session so the old connection is not reused. For high-resolution playback, check the basic network and background tasks as well; not all buffering is caused by the route. See the Streaming Comparison Article for Disney+ regional differences, and the site's Streaming Access Page for regional matching and common statuses.
Long-lived connections include remote collaboration, streamed responses, continuous uploads, and real-time communications. These tasks prioritize continuity, so avoid switching routes, modes, or basic networks after they begin. If interruptions are frequent, compare different path types in the same region and check device sleep and mobile background restrictions. Peak speed is not the only metric; steady transfer and whether the connection repeatedly has to rebuild better reflect real-world performance.
Infer the layer from the symptom
If every app fails, check the basic network, client permissions, and system proxy. If only one app fails, check its proxy and rules. If only one domain fails, check DNS, region, and the target service. If only one route fails, update the subscription and switch routes. If only one device fails, check platform permissions and local conflicts. If every device fails on the same network, compare with another basic network. This decision matrix is more effective than reinstalling, restarting, and switching routes without a sequence.
If an issue appears only during high-load tasks, pause background transfers, fix the route and test target, then compare path types. If it occurs while updating the subscription, there is no need to adjust app rules because the request has not entered normal usage. If the order status is abnormal, do not keep changing the client. Always return to the chain “account—order—subscription—client—route—target service” and find the earliest layer that failed.
Create a recoverable personal configuration
A mature configuration is not defined by complexity, but by being explainable, verifiable, and recoverable. Keep the subscription source, commonly used route regions, backup route types, and necessary app rules. Do not store a complete subscription URL where it can be seen publicly. After a system update, know how to recheck permissions with this guide. When changing devices, know how to obtain the client and subscription again from the user panel. This lets you recover quickly with the same layered method even when the network environment changes.
The full workflow is now complete: understand the service delivery model, choose a plan based on data usage, create an account with a username and password, complete an order through Alipay / WeChat Pay / USDT, obtain a personal subscription from the panel, import it on Windows / macOS / iOS / Android / Linux, verify the exit and apps, then maintain long-term use through subscription updates, data management, and rule configuration. Return to the Quick Start to reproduce the basics, see the Plans Page to compare prices, and visit the Routes Page to choose a region and path.