VPNKe Help Center

No email address is required. Set a username and password to create your account. Use the username to sign in to the user panel and the password to protect your account. After setup, store both securely, especially avoid saving login sessions on public devices or shared browsers. Subscription access, plan details, and support tickets are all managed through the same user panel.

Sign in to the user panel, open the download area, and copy the subscription information for your current account again. Return to the client and update the subscription or import it again. If the client continues to show old routes, do not repeatedly reconnect to the same nodes, as the local cache may not have refreshed. You can keep the original configuration while updating, then remove duplicates after confirming that the new configuration loads correctly. Subscription information is an account credential and should not be shared publicly.

You do not need to buy again simply because you changed devices. VPNKe supports unlimited devices and works on Windows, macOS, iOS, Android, and Linux. Sign in to the user panel on the new device, download the suitable client and subscription from the download area, and import them for your platform. When retiring the old device, remove the local subscription and sign out to prevent subscription information from remaining on a device you no longer use.

Registration uses a username and password, and no email address is required. First check login records saved in your browser or a trusted password manager. If you still cannot confirm your credentials, use the support ticket entry in the user panel to describe the account and provide information that can verify the order. Do not paste your full subscription, password, or payment credentials on public pages, as this could expose account access.

First confirm that the client is connected, then check whether it is using the system proxy, rule mode, or a broader connection mode. Some apps do not read the system proxy, while others retain their network state from startup. After connecting, fully quit and reopen the app, and check whether the client rules mark the target domain or process as direct. If the browser works but one app does not, investigate the app itself and the routing rules before repeatedly changing accounts.

First confirm that your current network can open the VPNKe user panel. Then copy the subscription information from the panel again instead of continuing to use truncated text, line-broken content, or an expired cache. During import, paste it into the subscription URL field, not the node name or notes field. If it still fails, delete the failed local subscription and import it again. Also check whether the system date, proxy chain, or security software is blocking the client's network requests.

Check several different websites first to determine the scope of the problem, rather than assuming a single site's outage means the entire connection has failed. Then disconnect from the current route, connect through another region, and fully close and reopen the browser. If no websites are accessible, check whether the system proxy still points to a client that has exited, whether the client has network permission, and whether another network tool is controlling the same settings. During recovery, keep only one connection tool active at a time to identify conflicts more easily.

First determine whether the local network itself is stable. Temporarily stop large file transfers and observe ordinary webpage connections. Changes in Wi-Fi signal, device sleep, power-saving policies, and network switching can interrupt long-lived connections. Then update the subscription and switch routes instead of repeatedly reconnecting to the same faulty path. On mobile devices, allow the client to maintain its connection in the background. On desktop devices, check that the system proxy matches the client status after waking from sleep.

During peak evening hours, compare different regions and routes instead of testing only one node. Prefer regions that are geographically closer and have more direct routing. If the target service has specific regional requirements, compare real-world performance among routes that meet them. Pause system updates, cloud synchronization, and large file transfers during testing, and use the same website or content for comparison. This helps distinguish local bandwidth usage, congestion at the target website, and changes in the cross-border route.

Start by selecting the target region based on your use case, then try nearby regions first. Everyday browsing and development tools generally benefit most from stable connections and responsive latency. For services with region-specific content, meet the regional requirement first. After choosing candidate routes, compare them on your usual network, at your usual times, and with your usual apps rather than relying on a single speed test. A route that reliably completes real tasks is more useful than a momentary peak speed.

AI websites and development tools often use long-lived connections, so brief network changes, device sleep, or route instability can interrupt generated content. Keep the client running in the foreground, switch to a stable route, and reopen the session. If the web version works but an IDE plugin or command-line tool does not, check the system proxy, terminal environment variables, and the app's own network settings separately. Avoid creating duplicate forwarding through multiple proxy entry points, as this makes the connection path harder to troubleshoot.

VPNKe covers 120+ countries / 150+ routes. The route list is provided through the subscription configuration in the user panel, and the refreshed list in your current client should be treated as the reference when choosing. Broader coverage provides more regional and routing options, but does not mean every region suits every task. For everyday use, start with nearby regions and adjust based on the target service's regional requirements, connection stability, and local network conditions.

Monthly plans are: ¥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 convert the price difference into remaining days. Estimate your needs based on your usual activities, since light browsing and frequent video use can consume very different amounts of data. View and select all plans through the user panel, and verify the amount and data tier again before submitting.

Data packages remain available until used and never expire: ¥158/300GB, ¥358/1000GB, and ¥658/3000GB. They use a different billing model from monthly subscriptions, which reset on the activation date, and are better suited to usage at irregular intervals with consumption based on total data. Before choosing, confirm whether you need a monthly subscription or a data package so the two data rules are not confused.

For a mid-cycle monthly plan upgrade, the price difference is converted into the remaining days. Before upgrading, verify the current plan, target plan, and order details shown in the user panel, then decide whether to continue. An upgrade does not turn a monthly subscription into a data package that never expires. Their data rules remain different: monthly subscription data resets on the activation date, while a data package remains available until used and never expires.

VPNKe supports Alipay / WeChat Pay / USDT. Start from the plan or order page in the user panel, and use the amount and status shown on the order page as the reference. After payment, do not submit the same order again; refresh the order status first. If the status remains unsynchronized for a long time, submit the order details through the user panel's support ticket entry for verification and keep your payment record, without providing unrelated sensitive credentials.

VPNKe offers a 30-day no-questions-asked refund. To request one, sign in to the user panel and submit the relevant order details through the support ticket entry. Explain which order should be handled and include the refund request so the payment record and account status can be checked. Keep the ticket record after submitting and avoid creating duplicate requests for the same order. The time for the refund to arrive depends on the settlement process of the original payment channel.