VPNGQ
Complete User Guide

About the Service and Cross-Border Connections

VPNGQ is a subscription service for cross-border connectivity, with 90+ countries / 240+ routes. It supports Windows / macOS / iOS / Android / Linux and unlimited simultaneous devices. Before setup, it helps to distinguish your account, plan, subscription and client: your account holds your access and orders, your plan determines billing and data, your subscription delivers available routes to the client, and the client establishes a connection on your device. These parts work together, but they are not interchangeable.

Understand how traffic flows

When you visit a website, an app sends a request. Your system then uses its proxy settings or routing rules to decide whether the request goes through your local network or a selected route. The route’s exit point connects to the destination service. A successful connection message only confirms that the client completed its own connection process; it does not prove that every app is using that route. Browsers, desktop apps and command-line tools may handle proxy settings differently, so verify the connection in the apps you actually use—not just by checking the client status.

Your local network is still the foundation of the connection. If your device cannot connect to Wi-Fi, is waiting for network authentication or has no working internet access, switching to an international route may not help. Check in this order: make sure the device can access the internet, review the client setup, then check the destination service. Treating problems at different layers as one issue can lead to repeated subscription imports without addressing the actual cause.

A route’s location does not determine service eligibility

The country or region in a route name helps identify its exit location and potential use cases. IEPL, transit and direct routes describe how a connection is arranged. Names are no substitute for testing, and they do not guarantee that a website will offer a particular content library. Streaming, AI tools and other online services may also consider account region, payment details, client status and their own policies. VPNGQ provides network connectivity; the destination platform manages access to its own accounts and services.

Distance is not the only factor when choosing a route. A nearby region is often a sensible place to start, but your local carrier’s routing, peak-time congestion and the destination service’s location can all affect performance. A more reliable approach is to choose the app you want to use, try a few candidate regions, then compare them using real tasks such as loading pages, streaming continuously or completing normal work requests. Avoid switching exits repeatedly to chase a single test result.

Privacy policies and credential security have different limits

VPNGQ describes its privacy policy as anonymous and no-logs. No email address is required to create an account; a username and password are all you need. Minimal account details do not mean an account can be shared casually: protect your password, account-panel session and subscription link. The link lets a client retrieve route configuration, so anyone who obtains it may gain access to related service capabilities. Never post the full link in public discussions, screenshots or public code repositories.

Using international routes does not replace website sign-in, file encryption or device security settings. Content you submit to a destination website remains subject to that site’s own policies, and browser extensions and software on your device still have their own permissions. For more on data handling, read the Privacy Policy. For the limits of service use, read the Terms of Service. Do not interpret brief feature descriptions as additional technical guarantees.

Before you begin, consider which devices and apps you use most and how often. Regular work, occasional research and extended video streaming put different demands on data and connection continuity. The next chapter covers plans and usage before account and client setup. This helps you avoid mistaking a plan issue for an installation problem and makes it easier to understand what you’re comparing when you check data use later.

Choose a Monthly Plan or Data Package

VPNGQ offers monthly plans and data packages. Monthly plans are suited to regular use, with data resetting each month on the activation date. Data packages last until used and never expire, making them a fit for intermittent use when you want to draw on your remaining data as needed. “Never expires” describes the package’s data validity; it does not mean unlimited data or guarantee that a destination website’s features will remain available. Before comparing prices, distinguish data allowance from billing type.

Usage depends on what you do online

Don’t choose a plan based only on how many hours you’re online each day. Browsing text pages, video calls, continuous streaming and syncing large files can use very different amounts of data—even with the same time online. List the apps you use regularly and note which ones transfer data continuously. Your client or system’s app-level data stats can help, while the account panel shows your service allowance. These tools may measure different things, so don’t assume all local network traffic counts toward your plan.

When you start, follow your normal routine and observe data use instead of repeatedly downloading large files to estimate your allowance. Connect what you see to specific activities, such as a video, cloud sync or background system task. If usage rises later, you can check which apps were active rather than assuming the route changed. Data allowance is not a speed tier; a larger package does not by itself mean a faster connection.

Understand resets and upgrades

Monthly plan data resets each month on the activation date, not necessarily at the start of the calendar month. To check your allowance, review your current plan, remaining data and reset notice together in the account panel. If you have just placed an order, confirm it is complete before refreshing the overview. If the page has not updated yet, don’t submit the same request repeatedly; that can turn a display delay into an order-reconciliation issue.

When you upgrade mid-cycle, the price difference is converted into remaining days. Before upgrading, read the order confirmation and make sure you understand how the updated term and allowance will be displayed. Don’t try to calculate the final charge with simple subtraction. This guide does not assume a specific date after an upgrade or a fixed order for using an existing monthly plan and data package. For plan combinations, change timing or existing balances, rely on the confirmation page and contact support through a ticket if anything is unclear.

Consider plan choice separately from service assurances

VPNGQ supports Alipay / WeChat Pay / USDT and offers 30-day refunds. See the Terms of Service for refund details. Full pricing and billing information is on the Pricing page. A refund policy does not add data to your plan, and different billing options do not imply discounts or terms that are not listed. Before paying, check the product name, price and billing type—not just the headline data allowance.

Unlimited simultaneous devices lets you set up your own devices as needed, but keep an eye on actual data use when they share an account. A computer syncing in the background and a video playing on a mobile device can use data at the same time, and a data package will decrease as it is used. Once you choose a plan, note why it fits—for example, monthly use for regular work or a data package for occasional browsing. You can use that note to reassess your needs later instead of starting the comparison from scratch.

Create your account and confirm your order

Once you’ve chosen a plan, go to the account panel to create an account. VPNGQ does not require an email address; you can create an account with a username and password. Your username identifies the account and your password verifies your identity, so use credentials that are different from those you use on other websites. Before submitting, check your keyboard settings, spaces and input method. Be especially careful not to include trailing spaces when pasting. Save your credentials securely before moving on to the plan.

Save your credentials before setup

Because an email address is not required, email recovery should not be assumed to be available. Store your username, password and the site address using a password-management method you trust, and make sure you can retrieve them. Don’t rely only on a browser’s saved session or put your password and subscription link together in notes intended for public sharing. On a shared device, avoid saving credentials in the browser and sign out of the account panel when you’re done.

After creating an account, if you land on the overview page, first confirm that it belongs to the account you just created, then place your order. If the browser already has a session for another account, check which account is currently signed in so the payment goes to the right one. To set up another device, sign in with the same account; you do not need to create another account just to import the client. Orders from separate accounts are not automatically combined just because they use the same device.

What to check on the order confirmation page

Open the Plans section of the account panel and select the option you’ve chosen. On the confirmation page, check the plan name, data, billing type and price. Make sure the action is to start a new plan, renew or change an existing plan, as intended. Read any on-screen details before continuing. Don’t infer the next step from where a button appeared on the previous page, and don’t treat an order still awaiting confirmation as paid.

Choose whichever payment method is actually shown: Alipay / WeChat Pay / USDT. Follow the instructions on the relevant page. A closed external payment page, a browser back action or a reloaded account panel does not necessarily mean the order failed. After paying, return to your account’s order history and check that the order is complete, then confirm the plan status in the overview. Payment flows can look different, so verify both the order record and plan status rather than relying on whether the payment window closed.

Check first if the status doesn’t match

If the payment provider shows the payment as complete but the account panel still says pending, keep your transaction receipt and order details, then refresh the order list. Don’t create the same order again just to “try once more,” and avoid switching accounts repeatedly, which can scatter the records. If you need help, use the support ticket system to share the plan, order status and payment method, along with an order reference that can be checked. Hide any unnecessary personal details on the payment receipt.

If the order is complete but the plan in your overview has not changed as expected, first confirm that the order belongs to the current account and check what type of action it was. A plan change and a renewal may appear in different status fields, so don’t judge by a date in just one place. Make sure your credentials are saved before signing in again, then refresh and check. If the mismatch remains, describe the difference between the order and overview pages and note what happened. Don’t delete your local client configuration to try to fix a display issue.

You’re ready to get your subscription when you can sign in, find the completed order and identify your current plan in the overview. The next steps will then be easier to follow. You can also sign in to view client downloads before paying: Android, Windows, macOS and Linux clients are available after sign-in. iOS access requirements are covered in the platform setup chapter. Download access and eligibility to use routes are separate things.

Get and protect your subscription

A subscription is how a client obtains route configuration; it is not a regular website bookmark. The subscription link in the account panel typically contains account-related credentials. The client uses it to request configuration and refresh routes. Importing it does not turn on the system proxy, and updating it does not renew your plan. Keep these distinctions in mind: if an import succeeds but a webpage does not change, or a payment is complete but the list has not updated, you’ll know which step to check.

Get the link from your account panel, not a chat history

Sign in to the account panel overview, check your plan status, then look for the subscription or client import option. If the panel offers an import method for your client, choose the matching option. An import button may open the app on your device. If your browser asks to open an app, check that it’s the right one before continuing. If no prompt appears, the subscription may still be valid; the client might not be installed, or the system may not have an app associated with that import link.

If you copy the link, copy it in full, then open the client’s subscription or configuration management screen. Add a remote subscription, paste the link into the address field and give the configuration a recognizable local name. The name only helps organize your list; it does not change your routes or account access. If the client offers separate fields for a subscription URL, configuration text and a local file, choose the remote URL option. Don’t import the link as if it were a full configuration file.

After importing, check more than the success message

Save the subscription and refresh or fetch the configuration. Check that a route list, groups and selectable exits appear. If you see a success message but no content, make sure you’re viewing the configuration you just imported, not an empty one the client had saved earlier. Some clients let you save multiple configurations, but only one is active at a time. Check separately that the configuration is saved and that it is the one in use. Don’t repeatedly add the same subscription before confirming which configuration is active.

If parsing fails, check that the link is complete, has no extra quotation marks and is being imported with the correct type. A webpage address, account-panel login address and subscription link serve different purposes and cannot be used interchangeably. If the client cannot fetch the link, first make sure your current network can reach the relevant account-panel resources, then check your account status. Successful copying only means the clipboard contains something; it does not prove the address is accessible. Changing many settings at random can obscure the original problem.

Know the difference between updating, resetting and exporting

Updating a subscription fetches the configuration provided by the service and is useful when you need to sync the route list. Resetting subscription credentials affects access through the old link; do this only if the account panel offers the option, and read its notice first. If you discover that a link was shared publicly, address the exposed credentials before updating your own devices. Renaming a local configuration does not deactivate a leaked link; local names do not change service-side credentials.

Exported configurations for migration or backup may also contain route credentials and sensitive fields. Save files somewhere you control, not in a public repository or an untrusted online conversion tool. If you’re moving to a new device, you can usually sign in to the account panel there and get a fresh import link instead of sending the old device’s full configuration around. If you share a screenshot to ask for help, keep the error message and interface state visible, but hide addresses, keys and account details that could identify you.

By the end of this chapter, you should be able to find the active configuration in your client and see selectable routes. Don’t judge yet whether apps are using it; operating-system permissions, system proxy settings and network routing modes are covered next. Complete configuration retrieval separately from enabling the connection to reduce the number of things that change at once. If something goes wrong, stop at that step and note the message instead of starting over with account creation.

Set Up the Client on Each Platform

Download clients only from the client section of the account panel, not from unverified sources. Sign-in is all that’s needed to download clients for Android, Windows, macOS and Linux; you do not need a purchased plan. For iOS, you need a purchased plan that has not expired. Follow the entry shown in the account panel. Getting the app and establishing a working connection are separate steps: using routes still requires a valid plan and a correctly imported subscription. The platform instructions below cover differences in installation, permissions, import and connection setup.

Windows: Verify with a browser first

After installing the VPNGQ client, open it normally and import your subscription from the account panel, or add a remote address in configuration management. When the update succeeds, select that configuration, choose a candidate route and connect. If you use system proxy mode, check that the client successfully applied the system proxy settings. Grant extra permissions only if the app explicitly requests them; you don’t need to change every system network option before a normal import.

First, open the website you want to use in a browser, then check your work apps and other desktop software. Some apps do not automatically use the system proxy and may need their own proxy settings or another network mode offered by the client. If the browser cannot connect after you close the client, check whether the system proxy setting was left behind instead of reinstalling network drivers. For more on app compatibility, see Windows System-Wide Proxy and Split Tunneling.

macOS: Installation and network permissions are separate steps

Get the client from the account panel, complete the installation steps required by your system and open the app. The first time you connect, macOS may ask to add a network configuration or allow a network feature. Confirm that the request comes from the client you just installed before approving it. If permission was denied or interrupted, check the relevant setting in System Settings. Seeing the app in your Applications list does not mean network routing is enabled.

After importing your subscription, check that the configuration is active before choosing a route and connecting. If you see repeated permission requests, read the feature name carefully and distinguish app startup, network configuration and extension permissions. Don’t keep cancelling and retrying different prompts. Check permissions again after an OS upgrade or device migration. For the full process, read Mac Installation, Permissions and Subscription Setup, keeping permission issues separate from subscription parsing problems.

iOS: Get the client through the account panel and allow configuration

Find the iOS option in the account panel’s client section. A purchased, unexpired plan gives you access to the corresponding link. If the page says your plan must meet certain conditions, check its status in the overview instead of looking for another static download address. Follow the entry instructions to install the client, return to the account panel and try importing it. If your browser asks to open an app, confirm the target client. If that does not work, paste the full link into the client’s remote subscription field, if supported.

The first time you connect, iOS asks permission to add a VPN configuration. Approve it in the system prompt, then return to the client to check the active configuration and route before opening the target app. The connection indicator in the status bar or Settings only shows that the network feature is enabled; check content access or account eligibility in the target app itself. If the connection has problems after you switch Wi-Fi networks, reconnect to the current route and check the exit again instead of immediately deleting the imported subscription.

Android: Check connection permission and background activity

Download and install the client from the account panel, open it and import your subscription. When Android first asks for VPN connection permission, confirm that the request comes from the VPNGQ client before allowing it. Choose a route and connect, then check for the corresponding network indicator. If other apps on the device also take over network traffic, check how they are configured to avoid competing for the same system capability and leaving you unsure which route is active.

If the client works in the foreground but disconnects when the screen locks, check the system’s battery optimization, background activity and auto-start settings for the app. Allow the background activity it needs in the device’s actual menus; there is no need to disable all device management features to fix one app. If the client supports per-app proxying, make sure the target app is included. Use Android Background Activity and Per-App Settings to check each option, then test whether the connection recovers after locking the screen.

Linux: Test desktop apps and terminal tools separately

Choose a client in the account panel that suits your system environment and install it using the available package format. Once the graphical app opens, import the subscription, update the configuration, select a route, then set up the desktop proxy or another routing option. Read any permission prompts carefully. Never paste account passwords or subscription details into unrelated terminal commands. Menus and permission systems vary between distributions, so follow the instructions for your current client.

Linux desktop proxy settings may not be inherited by every terminal program, and terminal environment variables may not affect graphical apps that are already running. Test your browser and the command-line tools you actually use separately. Get a simple setup working before configuring your development toolchain. If you need to enter a proxy address manually, use the listening address and port shown by your client; don’t copy values from another device. Keep a record of the original settings so you can restore them after disconnecting.

On every platform, return to the same checklist after importing: the right configuration is active, a route is selected, required permissions are granted and the target app is actually using the route. Complete this loop on one familiar device before setting up others. It makes troubleshooting much easier than dealing with settings from several operating systems at once.

Check Your Connection and Troubleshoot

The aim of a connection check is not to collect impressive-looking test results; it’s to confirm that the app you need works through the expected exit. Before testing, note your current route, proxy mode and app scope. Keep the network environment steady and avoid changing Wi-Fi, routes and DNS at the same time. Change one setting that affects the path at a time, observe the result, then decide what to do next. That’s how you find out which setting made a difference.

Check each layer, from local network to target app

Disconnect the client first and make sure your local network can access the internet. If the network requires authentication, complete it before connecting to VPNGQ. Then connect and check that the active configuration, connection status and selected route are as expected. If the client reports a configuration load error, return to the subscription chapter before troubleshooting the destination website. If your local network itself is unavailable, don’t assume the international route is why a website won’t open.

Use a trusted method in your browser to check your current exit region, or review the connection source in information provided by the destination service. Never submit your subscription link to an online tool just to check the exit. Note your current mode before testing: with rule-based routing, different websites can use different paths. A regular webpage showing a local exit does not prove that the target app is bypassing the route; check which rule applies to that website before interpreting the result.

How to distinguish DNS issues from app proxy settings

DNS translates domain names into addresses a device can connect to. The DNS resolution path and the actual data-connection path need to be considered together. If a domain fails to resolve, check the error category in the client log, then confirm whether the current configuration routes DNS requests. Not every site that fails to open has a DNS problem, and you should not enter an unfamiliar DNS service without a reason. Save the original value before changing DNS so you can compare and restore it if needed.

If a browser works but an app does not, check whether the app supports the system proxy, is excluded by per-app routing rules or had an old connection open before you changed settings. Fully quit and reopen the app so it can read the new settings. If it has its own proxy field, make sure it does not conflict with the client. Before using a network-takeover mode, read the client documentation and confirm it will not disrupt existing work-network settings.

Separate service restrictions from network failures

If a webpage loads but says your account region is unsupported, asks you to sign in or reports that you do not have the required access, this is usually more than a connectivity issue. The destination platform determines streaming availability and AI tool eligibility; switching routes cannot replace account requirements. Save the exact message and work out whether it appeared before a connection was established or after the page loaded. This helps avoid mistaking a normal account notice for a broken client and reinstalling it without making progress.

To compare candidate routes, use the same device and app and follow a similar sequence of steps. Check whether you can complete the actual task consistently, not just whether it opens once. If performance differs during peak hours, note the time, local network and target app. Don’t invent a fixed speed or treat a single experience as a long-term guarantee. For route types and locations, see the Route List.

After testing, you should be able to explain which app used which mode and route to complete a particular task. That is far more useful for troubleshooting than simply saying “it’s connected.” For more detailed exit and per-app checks, see How to Check Whether Your Connection Is Working. If you still need to open a support ticket, describe both what works and what does not, and include a redacted error message to help pinpoint the issue.

Routine Maintenance and Renewal Checks

Reliable everyday use doesn’t require reinstalling the client or rebuilding a subscription whenever the list looks unchanged. Focus on whether your account is active, how data is being used, whether the current configuration can still update and whether the connection recovers after you switch networks. Check at useful points—when starting work, changing a plan or setting up a new device—instead of repeatedly tweaking advanced options without a clear goal.

Check app activity when reviewing data use

Check your current plan and remaining data in the account panel overview. Monthly plan data resets each month on the activation date; data packages last until used and never expire. Don’t expect the two to renew in the same way. If your remaining data is dropping quickly, think about recent video streaming, file transfers or background sync, then check whether several devices are active at once. Client uptime alone does not tell you how much data was used: an idle connection and continuous data transfer are different kinds of activity.

Unlimited simultaneous devices makes it easy to switch between your usual devices, but keep track of which ones are still in use. An old computer, spare device or client in a shared environment may still be active. When you stop using a device, disconnect it and remove locally saved account details and configuration as appropriate. If you suspect a subscription link was shared improperly, check how its credentials are protected instead of assuming that a route in a particular country uses more data.

Check the order type before renewing

If you want to keep using a monthly plan, check your current plan and the available renewal options in the account panel. Make sure the order action matches what you intend. Don’t confuse “Update subscription” in the client with a renewal: it only fetches configuration and cannot process a payment or extend your plan. After payment, check in this order: order completion, plan status in the overview, then client update. If the page has not synced, refresh and check before submitting the same order again.

For an upgrade, remember that the mid-cycle price difference is converted into remaining days, and rely on the confirmation page. Don’t promise yourself a fixed difference to pay or a new expiry date. If you’re comparing a monthly plan with a data package, review the billing options on the Pricing page before following the change options shown in your account panel. For questions about how existing plans are used, overlap or special account statuses, open a support ticket rather than treating a guess as a confirmed rule.

Update clients and configurations in the right order

Before updating a client, make sure your account credentials are saved and note the active configuration, usual route and any essential local rules. Get the client for your platform from the account panel, then follow the system’s installation and permission prompts. After updating, test a simple setup that worked before, then check your custom features one at a time. If only one custom rule has stopped working, you don’t need to delete and rebuild the entire account configuration. Keep a clear record of changes to distinguish an update issue from a pre-existing settings conflict.

A subscription update may change the route list or rules. Locally edited settings may be overwritten, depending on how the client manages configurations. To keep custom rules long term, use a separate override or rule-management feature the client explicitly supports, and check how it combines those rules with the remote configuration. Don’t assume that changes made directly to a downloaded configuration will survive the next update.

Switch networks and prepare useful support details

When switching networks, first make sure the new network is authenticated and can access the internet, then reconnect the client. Sleep and wake cycles, system updates and background restrictions can all affect recovery. Try disconnecting and reconnecting, then check the target app. If the problem only happens after the screen locks, revisit the background settings in the platform chapter. If it happens with every network switch, note the before-and-after status instead of changing several settings while trying to reconnect.

For help, contact support through the Contact page or a support ticket in the account panel. Include your device platform, connection mode, affected app, error text and the checks you have already tried. Hide subscription credentials and unnecessary account details in screenshots, and check logs for sensitive information before sharing them. A reproducible sequence is more useful than “it doesn’t work.” VPNGQ offers 30-day refunds; see the Terms of Service for application details.

Split Tunneling, Developer Tools and Advanced Use

Once you’ve verified a basic connection, you can look at split tunneling and developer tool settings. Advanced features are useful when different apps need different routes—not because every switch should be turned on. Before making changes, save a working configuration and define the problem you’re trying to solve, such as keeping a work intranet on the local network or routing a command-line tool that does not use the system proxy. Without a clear goal, the default working setup is usually easier to maintain than a stack of custom rules.

System proxy, rule-based routing and network takeover

A system proxy provides proxy details to apps that choose to use them; it is straightforward, but not every app will necessarily follow it. Rule-based routing chooses a path based on domains, addresses or other supported conditions, which can help separate local resources from international services. Rule order and matching behavior affect the result. Network takeover may cover more traffic and require additional system permissions. Check which modes your current client supports; options on different platforms are not necessarily equivalent.

When writing routing rules, define what should match, choose an action and then check whether the rule is being applied. Adding a domain that looks right does not guarantee that it covers every request from an app; sign-in, resource loading and API calls may use different addresses. Start with a trusted existing configuration and make small changes for a clearly identified problem. Work intranets, local devices and managed corporate networks have their own requirements. Understand your organization’s policies before changing routing, so local resources are not mistakenly sent through an international exit.

Developer tools need their own proxy checks

A browser opening an AI website does not mean API requests, editor extensions or background tasks in your terminal use the same route. Developer tools may read environment variables, use their own settings or run in a background process. Check how your tool handles proxies, then enter the address shown by your client. Don’t copy a listening port from someone else’s guide or paste a subscription link into an HTTP proxy field: one retrieves configuration, while the other connects a program to a local proxy. They serve entirely different purposes.

In a compatible shell, use the command below to check whether common proxy environment variables are set. The output may include a proxy address or authentication details, so view it only on your own device and hide sensitive information before sharing. No output only means these variables are not set; it does not prove that the client is disconnected. Apps using the system proxy or network takeover may not rely on these variables at all.

printenv HTTP_PROXY HTTPS_PROXY ALL_PROXY NO_PROXY
printenv http_proxy https_proxy all_proxy no_proxy

Processes usually inherit environment variables when they start, so an editor or background task that is already running may keep using old values after you change terminal settings. Restart the relevant process as described by the tool, then test a real request. Correct proxy settings do not guarantee that an API account has access: authentication failures, insufficient quota, invalid request formats and network timeouts need to be diagnosed separately. Developers can also read Route Selection and Timeout Settings for AI API Calls. Don’t attribute every API error to the route.

Route continuity and retry limits

For sign-in sessions, development tasks or continuous streaming, try to keep the exit that you’ve already verified instead of switching regions mid-task. The goal is to avoid unnecessary changes; it is not a promise that VPNGQ provides a fixed IP. The destination service may still revalidate your session according to its own policies. If you need to change routes, pause the task, switch, check your account status and app connection again, then resume.

More automatic retries are not always better. If a request reached the destination service but its response was delayed, sending it again may create duplicate tasks or extra usage. Use the idempotency and retry mechanisms supported by the destination API. During troubleshooting, identify the error type before changing timeout settings; don’t use unlimited retries to hide a configuration problem. For AI tools, see the AI Tools hub; for streaming, see the Streaming hub to understand each type of app’s requirements.

To wrap up, keep the setup flow in mind: the account holds your access, the plan defines your allowance, the subscription provides configuration, the client establishes the connection and testing in the app confirms the result. Use this sequence for routine checks and you can break complex problems into steps you can verify. To repeat the basic setup, return to the Quick Start Guide. To compare routes or billing options, consult the route list and pricing page; there’s no need to redo steps you’ve already confirmed.