Reproduce the issue
Record the target service, exit region and network environment, and confirm that the issue can be reproduced consistently.
SUPPORT / ROUTE CHECK
Organized by account, connection, routes and billing. Confirm the symptoms first, then perform the relevant checks one at a time so you can identify whether the issue comes from the subscription, client, network or target service.
ACCOUNT / SUBSCRIPTION
Handle registration, subscription access, configuration updates and device migration. Subscription details are account-delivery information and should be obtained from the user panel and stored securely.
No email address is required. Create a username and password to register. Use the username to sign in to the user panel, and store the password separately rather than reusing it elsewhere. After registration, sign in to the panel to choose a monthly subscription or data package based on your usage. Get the client and subscription from the panel as well.
Sign in to the user panel and open the client download page to get the client and subscription for your current system. Do not copy subscription details into public chats, screenshots or shared documents. After importing, update the subscription once, then choose a route and connect. When the client shows that you are connected, check that the exit region is the one you expect.
Find the UVvpn profile in the client’s subscription manager and run an update or refresh. If the update fails, return to the user panel, copy the current subscription again and replace the old content saved in the client. You can remove duplicate profiles first so the client does not keep reading an outdated route list. After updating, choose a route again and connect.
You do not need to buy again when changing devices; UVvpn supports unlimited devices. Sign in to the user panel on the new device, get the client and subscription for its platform, and import them again. If the old device is no longer in use, sign out and delete the local subscription so it is not left on a device handed to someone else.
Windows / macOS / iOS / Android / Linux are supported. Sign in to the user panel and open the client download page to view the available option for your system. Permission prompts and import locations may vary by platform, but the process is the same: get the client, import the subscription, update routes, allow the system connection configuration, choose a route and verify the exit location.
CONNECTION / LOCAL CHECK
For connection issues, start with the latest subscription, current route, system permissions and local network. Do not change several settings at once, or you will not know which adjustment worked.
First confirm that the client is using the latest subscription, then check that a specific route is selected rather than an empty or unselected profile. Disconnect, switch to another route and connect again. If no route works, restart the client, correct the system time and try a different network to rule out local cache issues, clock drift and network egress restrictions.
This is usually related to the client’s routing mode, app exclusion rules or system connection permissions. Switch the client to a mode that covers all traffic for comparison, and check whether the target app is on a direct-connection or exclusion list. After changing the setting, fully close and reopen the app so it does not continue using a connection created before the change.
On the first connection, the system usually asks you to confirm the connection configuration or grant network permission. Once you confirm that the prompt comes from the client you are using, follow the system instructions to allow it. Otherwise, the client can import routes but cannot manage network traffic. If permission was previously denied, open the system’s network or connection settings to authorize it, then return to the client and connect again.
When moving from one network to another, the existing connection may still be tied to the old network exit. Disconnect in the client, wait until the system confirms that the new network can access websites normally, then connect again. If there is still no response, switch to another route or fully quit and restart the client. Avoid clicking Connect repeatedly in quick succession, as multiple requests may remain pending.
Open a few other ordinary websites first to determine whether all access is failing or only the target site is affected. If everything fails, check that a valid route is selected and disconnect and reconnect. If only the target site fails, clear its cache and old session, or try again with a different exit region. Also pause other tools that may be changing system network settings at the same time, so their rules do not overwrite one another.
ROUTING / PERFORMANCE
Route selection should not rely on a single metric. Validate the target region, interactive response, sustained transfer and local access separately, then choose based on the actual use case.
Record the target service, exit region and network environment, and confirm that the issue can be reproduced consistently.
Switch routes on the same network and with the same target, rather than mixing results from different environments.
Reopen the target service and check whether page response, continuous playback or file transfer has recovered.
Pause background downloads, cloud-drive syncing and system updates, then compare other routes in the same region. Peak-hour issues may come from either the local access network or the target service, so do not repeatedly reconnect to only one route. Reopen the target content after switching and check whether ordinary websites, video and file transfers recover together to identify the bottleneck.
Filter by the region required by the target service first, then compare the connection experience among routes that meet that requirement. Latency helps assess interactive responsiveness but does not by itself represent sustained transfer performance. Web browsing and AI Tools benefit more from stable responsiveness, while video and downloads depend more on sustained transfer. Use the target service’s actual loading and playback results as the final measure.
Latency describes request round-trip speed, while downloads are also affected by local access, route congestion, target-server throttling and client status. Stop other bandwidth-heavy tasks first, then compare another route in the same region. If ordinary websites respond normally but one download source is slow, the source itself may be the issue. Test another source rather than judging the entire route from one result.
Choose an exit matching the region of the account’s content, then close and reopen the player so the platform can reassess the region and create a new session. Pause background transfers during playback to avoid sustained network usage. If buffering continues, switch between routes in the same region and test continuous playback at a lower quality first. Restore the target quality once stable to distinguish regional detection from transfer issues.
A page loading only confirms that basic access is established; conversation requests may still be affected by an old session, an exit change or route instability. Save any unsent content, refresh the page and sign in to the target service again. If it still waits, switch to another route in the same region and start a new session. Avoid switching routes repeatedly while a request is processing, or existing connections may be interrupted.
BILLING / REFUND
First distinguish monthly subscriptions from data packages, then verify the current order, activation period and remaining data. Submit order-related issues through the user panel rather than scattering transaction details across channels.
Data resets monthly on the activation date; a mid-cycle upgrade converts the price difference into remaining days.
Available until used and never expires. Plan usage around actual consumption; it does not follow the monthly subscription reset.
Monthly subscriptions are ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Check actual usage on your usual devices first, then choose a tier based on how heavily you use the service. Monthly data resets each month on the activation date, making these plans suitable for sustained, relatively consistent usage.
Data packages remain available until used and never expire. Options include ¥158/300GB, ¥358/1000GB and ¥658/3000GB. They suit usage that is irregular or best managed according to actual consumption. Before purchasing, distinguish their no-reset structure from monthly subscriptions so you do not estimate package usage as if it reset each month.
Monthly subscription data resets each month on the activation date rather than on a shared calendar-month schedule. Check the subscription period shown in the user panel when reviewing remaining data. Data packages remain available until used, never expire and do not follow the monthly reset. The two products use different calculation rules, so keep them separate when checking usage.
For a mid-cycle upgrade, the price difference is converted into remaining days. Before proceeding, check the current tier, remaining period and target tier in the user panel, then confirm the upgrade. If you only need more data occasionally, compare a data package first to see whether it better fits your needs, rather than changing plans without checking the remaining period.
Alipay / WeChat Pay / USDT are supported, with a 7-day no-questions-asked refund policy. To request a refund, sign in to the user panel and submit the relevant order details and refund request through a ticket, identifying the transaction to review. Before submitting, confirm that the order matches the current account and keep the order record in the panel for ticket processing.
TICKET CHECKLIST
Include the platform, the client’s current status, target service, selected region, steps already tried and final result. For order issues, include the order details shown in the user panel; do not submit the subscription text for connection issues.