VPN Help Center

No email address is required. Create an account with a username and password. After setup, save your login details in a trusted password manager and make sure you are on the VPNUE website. Your account login details and client subscription link serve different purposes: the former gets you into the dashboard; the latter imports route settings into a client. They are not interchangeable. Since no email address is required, do not expect to recover your account by email. If you cannot log in, check the username spelling, capitalization, and whether your input method changed any characters. Then review the dashboard message and the available contact options on the support page. Before sharing a screenshot, hide your password, subscription link, and other sensitive account information.

Sign in to the user dashboard and look for subscription details under Account Overview or Downloads. Import the subscription into your client using the method shown in the dashboard. When routes change, open the client’s subscription or configuration manager, choose Update Subscription, and wait for the update to finish. Then check whether route names or groups have changed. If the client still shows the old configuration, make sure you updated the configuration you are currently using, not another one imported earlier. If the dashboard says the link has changed, get the new link from the dashboard and replace the old source. Do not post the link in public forums or use online conversion tools from unknown sources. Button names may vary by client.

VPNUE supports an unlimited number of devices and works with Windows / macOS / iOS / Android / Linux. When switching devices, sign in to the same account, find the client and import instructions for your platform under Downloads, and import your current subscription on the new device. You do not need to choose a new plan just because you changed devices. Device limits and plan data are separate: unlimited devices does not mean unlimited data, so keep an eye on the usage and plan status shown in the dashboard. If you no longer use the old device, remove its saved subscription configuration so your access credentials are not left on a device you hand to someone else. See the Guides page for installation and permissions help.

A route list in your client only confirms that a configuration was imported locally at some point; it does not mean your current plan is still active. Sign in to the dashboard and check the plan status and remaining data under Account Overview. Then make sure the subscription used by the client belongs to the same account. If the plan is active, try updating the current subscription and check that your device’s date and time are correct. An incorrect system clock can affect network authentication or secure connections. Do not repeatedly create accounts or add old configurations just to clear the message. If the issue persists, note the exact message, device operating system, client name, and steps that triggered the problem, then submit a ticket through the dashboard. Hide the full subscription link in any screenshots.

A connected status usually means the client has enabled the connection feature; it does not confirm that every app’s traffic is using the selected route. Disconnect first and check that your local network can still reach websites that normally work. Reconnect and test the site in question. Then check that the client has a working route selected, the current configuration is enabled, and any required system proxy or network permissions are active. If other websites load and only one service fails, check that service’s access requirements and the route’s exit rather than assuming the whole network is down. Change one setting at a time and keep the error message so you can identify the cause without changing the configuration, route, and network all at once.

Apps may use different network paths. Some do not automatically use the system proxy, or may be excluded by per-app settings or client routing rules. Check the client’s current mode and which rules are being applied, then confirm the target app is not set to connect directly. If the client supports per-app proxying, make sure the app is included in the proxy list. After changing settings, fully quit and reopen the app so it does not keep using an existing connection. If the client requires a tunnel feature, grant the necessary permissions as described for your platform. Avoid changing unfamiliar advanced settings. A working network connection does not guarantee that your account or the target service meets its regional requirements.

Device sleep, network changes, and system background management can all interrupt an existing connection. Return to the client to check its status; if needed, disconnect and reconnect to establish a fresh connection over the current network. On Android, check the system’s background activity and battery restrictions for the client. On other platforms, make sure the client is still running and that required network permissions have not been disabled. If the issue only occurs on one Wi-Fi network, compare it with another available network to distinguish a local network restriction from a route issue. Avoid running multiple clients that manage network traffic at the same time, as their system proxy or tunnel settings may conflict. When submitting a ticket, describe what you did just before the connection dropped; that is more useful than a screenshot showing only that you are disconnected.

Sign in to the dashboard and open the ticket page. Describe what happened in order, including your platform and client, selected route name, current network, target app or website, and the exact error message. Say whether the issue is ongoing or only occurs after actions such as switching networks or running the app in the background, and list the troubleshooting steps you have already tried. You can attach screenshots with sensitive details hidden. Before sharing logs, check that they do not contain your subscription link, password, or other sensitive information. Avoid reporting only that it does not work, and never send full access credentials as proof. Keeping the details in one thread helps support follow your troubleshooting. The support page also links to dashboard tickets.

First check whether downloads, syncing, or video streaming are using your local network, then see if the issue affects multiple websites. If your local connection is still noticeably slow after disconnecting, troubleshoot the local network first. If only traffic using the selected route is affected, try another route in the target region and compare using the same page or video clip. Streaming can also be affected by the service’s status, playback quality, and buffering, so one instance of buffering is not enough to judge route quality. Keep the network and content the same during tests, and avoid changing every setting at once. If the issue continues, submit a ticket with the time, route name, and symptoms instead of relying only on the client’s status label.

These labels describe route paths; the label alone cannot predict performance on every network. IEPL routes generally use a dedicated link, relay routes pass traffic through an intermediate node, and direct routes connect to an exit directly. Check the route details in the dashboard for the specific configuration. Start by considering the region required by your target service, then compare connection stability, page response, and sustained performance on your current network. A shorter geographic distance does not always mean a better experience; inter-network routing, the exit, and the target service also matter. VPNUE covers 100+ countries / 220+ routes, so you can compare candidate routes for the same region. See the Global Locations page for route type details and selection tips.

Switching regions may change the exit, but it cannot guarantee access to every service. AI tools such as Claude may depend on account status, supported service regions, and session verification. Streaming services such as Disney+ may also depend on the content library available in a region, membership permissions, and how the exit is identified. First confirm the service is available and your account meets its requirements, then test a route that matches the target region. After switching routes, quit the app or end the previous session before trying again, so cached connections are not reused. Avoid repeatedly moving an account between regions for testing, and remember that a network subscription does not include membership benefits for third-party platforms. If you see a specific error code, submit it with the route name in a ticket and judge the result by actual access or playback.

Latency and download throughput measure different things. Latency mainly reflects the round-trip response to a test request. Actual download speeds also depend on your local network, route, destination server, file source, and other tasks running at the same time. The client’s test destination may not be the service you are accessing. Low latency can help compare routes, but it does not translate directly into download speed or streaming performance. To troubleshoot, compare the same content from the same source on the same network, and check whether background syncing or downloads are using bandwidth. If only one download source is slow, consider the source server as well. Do not draw long-term conclusions from a single speed test; consistent everyday performance is a better measure of how well a route suits your needs.

Monthly plans: ¥9.9/month includes 60GB · ¥18/month includes 250GB · ¥28/month includes 500GB. Data resets monthly on your activation date, not on the first day of the calendar month. Before choosing a plan, consider how you use the web, AI tools, video, and file transfers, then review the full details on the Plans page. Data used on different devices is not a separate allowance for each device. After activation, use the plan status, data usage, and reset information shown in the dashboard as your reference. If the usage looks wrong, first check whether another device is downloading or syncing in the background, then submit a ticket with the relevant screen and a description of the issue. Do not estimate the reset date from calendar months or treat a monthly plan as a permanent data package.

Data packages: ¥158/300GB · ¥358/1000GB · ¥658/3000GB. They remain valid indefinitely until used. Monthly plan data resets on your activation date each month. The difference is how data is used and reset: do not apply a monthly billing cycle to a data package or assume unused monthly data rolls over. If you upgrade a monthly plan mid-cycle, the price difference is prorated against the remaining days. Check the dashboard for the result of the change. Before confirming, review the target plan, order, and account status after the change takes effect. If you have questions about the proration, ask through a ticket first rather than repeating an action before you understand the prompt. See the Plans page for full pricing and plan details.

VPNUE accepts Alipay / WeChat / USDT. Choose a plan in the dashboard and check the order before following the payment instructions shown for that transaction. For USDT, carefully verify the required network and recipient details on the page; do not pay using an old screenshot or information forwarded by someone else. If your account status has not changed after payment, check the order status in the dashboard, confirm you are signed in to the account used to place the order, and check whether the payment service shows the transaction as complete. Do not pay again just because the page has not updated. If the payment is complete but the order has not updated, submit the order details and a redacted payment receipt through a ticket. Keep the original records so support can verify the same transaction.

VPNUE offers a 60-day no-questions-asked refund. To request one, sign in to the account used for payment and submit a refund request through a dashboard ticket, including the relevant order details so the account and transaction can be verified. You do not need to report a connection issue to qualify for a no-questions-asked refund. If you also want help troubleshooting, describe the issue separately so it is clear which part is the refund request and which is technical support. See the Terms of Service for full eligibility details. Track progress through ticket replies and the payment provider’s records; do not assume a specific processing time. Do not share your password or full subscription link. Redact sensitive details from payment records that are not needed for verification, and keep follow-up messages in the same ticket.