Help Center

No email address is required. Set a username and password, then store them in a trusted password manager instead of relying only on temporary browser storage. After registration, open the user panel to choose a plan, then download the client and subscription for your platform.

Open the user panel and retrieve your current subscription again. Then find Subscription Management or Configuration Management in the client and run the update. If the route list does not change, delete the old subscription entry from the client and import it again from the panel. Before making changes, confirm that you are using the current subscription provided by the VPNXA panel, rather than editing an expired local configuration.

You do not need to buy again when changing devices, and VPNXA does not limit the number of devices. Install the appropriate client on the new device, retrieve the subscription from the user panel, and import it again. If the old device is no longer in use, remove its saved subscription and sign-in session. Do not keep a session that can directly access the user panel on a shared device.

Get the client and subscription from the user panel; no public static subscription address is provided. VPNXA supports Windows / macOS / iOS / Android / Linux. Open the Downloads area in the panel, select the instructions for your current system, and import the subscription as prompted. Complete any system permissions, network extensions, or background-execution approvals requested by the client.

First confirm that your local network can open commonly used websites normally, then return to the user panel and update the subscription. Next, switch to another route in the same region and check that the client has the required system network permissions. If no route connects, quit and reopen the client. If the issue persists, submit a ticket with your system name, the client’s message, the selected route, and what you were doing when the failure occurred.

This usually requires separating route connectivity from DNS resolution. Switch to a backup route and reopen the page, then try closing stale browser tabs. If the result is the same in different browsers, check whether the client’s system proxy is enabled and whether another tool is also changing network settings. If the issue continues, include the client connection status and the type of website you cannot access in your ticket.

First check whether the client is using Rule mode or Global mode. Rule mode determines the traffic exit according to its rules, and some apps may not match the expected rule; temporarily switch to Global mode for comparison. If the app works in Global mode, the connection itself is fine, so update the subscription rules or review custom routing entries. If neither mode works, check whether the app has its own network settings or private DNS feature enabled.

First check whether the system restricts the client’s background activity and allow it to maintain a continuous network connection. Battery-saving policies may pause background tasks after the screen locks, so add the client to the list of apps allowed to run in the background. Reopen the client and check whether the connection recovers automatically. If this happens only on a particular network, test another local network to determine whether the cause is the system’s background policy or the current access network.

Do not edit the subscription manually. Open the VPNXA user panel, copy the subscription again or use the subscription import option, and confirm that the client’s correct import entry point is selected. If the client retained an old configuration, delete the old entry and import it again. If it still fails, include the client name, system name, and complete error message in your ticket. Do not paste the subscription publicly or forward it to a public discussion forum.

First check whether the local network is already slow with the accelerated connection disconnected, then connect to another route in the same region for comparison. Downloads, video, and web browsing have different route requirements, so test with the app you actually need rather than relying on a single speed test. You can also pause system updates, cloud-drive syncing, and other tasks that continuously use bandwidth to determine whether local concurrent traffic is the cause.

When buffering occurs during peak evening hours, switch first to a backup route in the same target region instead of repeatedly reinstalling the client. If a video has already failed to buffer, close the current playback page after switching routes and reopen it to avoid continuing with the old connection. If routes in different regions perform differently, keep the more stable route as your regular choice and include the time, content platform, selected region, and local network type in your ticket to help identify differences along the path.

For ordinary websites and everyday tools, start with a nearby, stable route. For services whose content varies by region, prioritize the region where the content is available. A shorter distance is not always better: cross-border path quality, the local carrier network, and the target service entry point all affect the result. Choose the target region first, then compare the available routes there based on actual performance.

An accessible page only confirms that the basic connection is established. Content authorization may still depend on the account region, exit region, cache, and platform policies. First confirm that the selected route region matches the target content region, then leave and reopen the streaming platform. If the browser and app behave differently, test them separately to rule out stale cache or an in-app region state. Whether specific content is available ultimately depends on the platform’s authorization at that time.

Switching routes does not change your subscription plan, and you do not need to buy again. The client changes the exit route from the imported route list. An active download, call, or playback session may briefly reconnect, so switch routes before changing tasks when possible. If every route disconnects frequently, update the subscription and check local network stability instead of switching rapidly over and over.

Monthly plans are ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Choose based on your actual usage for everyday browsing, video, file transfers, and similar activities rather than a single use case. Data for each monthly plan resets every month on the activation date. The Plans page in the panel shows the currently available options.

Monthly data resets each month on the activation date, rather than clearing on the first day of the calendar month. For a mid-cycle upgrade, the price difference is prorated by the remaining days. Before upgrading, check your current plan and usage in the user panel, then open the Plans area and choose the required tier. Do not create another account to handle an upgrade, as this can split your subscriptions and orders.

Data packages remain available until used and never expire. Available options are ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. Data packages suit users with irregular usage who prefer to consume a fixed total allowance; monthly subscriptions reset each month on the activation date. Before purchasing, distinguish between the two product types so you do not apply monthly reset rules to a data package.

VPNXA supports Alipay / WeChat Pay / USDT. When placing an order, enter the payment flow from the Plans area of the user panel and complete payment on the original order. Do not create duplicate orders for the same need. If the payment result does not appear promptly, check the status in the Orders area first, then submit the relevant order details through a ticket.

VPNXA offers a 30-day no-questions-asked refund. To request one, open the Tickets area in the user panel, specify the relevant order and refund request, and keep the order and payment records shown in the panel for verification. Handle refund issues through an account ticket. Do not submit subscription content or payment credentials on public pages; the ticket outcome determines the current status.