VPN Use & Troubleshooting

No email address is required. Create an account with a username and password. Keep your login details safe, avoid reusing passwords from other sites, and never post them in public forums. Treat your subscription link as sensitive information, not as an ordinary URL to share. If you forget your login details, first check your password manager and browsers where you have signed in, then use the help options currently available in the dashboard; do not assume you can recover access by email. Your account name is not your subscription link. When adding a subscription to a client, use the subscription details provided in the dashboard, not the login page URL.

Sign in to the user dashboard and check your account’s subscription status, then get the currently available link from the subscription section. Find the relevant entry in your client’s configuration or subscription manager, update it, and check the result. Don’t paste the link into a route search box. If the link in the dashboard has changed, edit the existing subscription URL and update it again. Once the new configuration appears and connects successfully, remove the old one carefully so you don’t delete rules still in use. If the update fails, first check whether you can reach the dashboard and note the error message. Reimporting the same link repeatedly usually won’t fix an expired URL or a failed network request.

This service allows unlimited devices to be online at the same time, so switching devices alone doesn’t require choosing a new plan. Supported platforms include Windows / macOS / iOS / Android / Linux. Sign in to the user dashboard on your new device, follow the instructions in the download section to get a client, and import your current subscription. Client downloads are available after sign-in on all platforms except iOS. The iOS download option is shown according to your dashboard permissions and requires a purchased, unexpired plan. Unlimited devices does not mean unlimited data, so check your account’s data balance before use. Before you stop using or hand off an old device, remove your account details and subscription configuration from it.

First, make sure you imported the current subscription for your account—not a plan page or dashboard login URL—then check whether the subscription update succeeded. Clear any client search filters and check whether the list is showing favorites only or a group with no entries. If it’s still empty, check your plan status and remaining data in the dashboard, get the subscription again, and import it according to the platform instructions. Don’t share a screenshot containing your full subscription link. When contacting support, provide the client name, operating system, update result, and steps you’ve tried. Redact any credentials in the subscription before sending them.

A “connected” status means the client has started the local connection process; it doesn’t guarantee that the destination website is reachable. Disconnect and check whether your local network can open everyday websites. If your local connection is having problems, resolve those first. Then reconnect, confirm that system proxy or virtual network routing is enabled as described by your client, and try routes in other regions. Keep the destination website the same during testing so you can tell what changed. If no websites work, focus on client routing and your local network. If only one site fails, check its regional requirements, account status, and app routing rules.

Browsers and apps may use different network paths. Some apps ignore the system proxy, or client routing rules may send them directly, so a working browser doesn’t mean every app is routed through the client. First check the rules and policy group for the app, then follow the client’s instructions to see whether virtual network routing and system permissions are needed. After changing settings, fully quit and reopen the app so it doesn’t keep using an old connection. Don’t run another proxy client at the same time while troubleshooting, as their routes may conflict. If the issue continues, note the app name and exact error, and distinguish a network connection failure from platform account or regional restrictions.

Handle failed subscription requests separately from configuration parsing errors. For a request failure, check whether you can open the dashboard, confirm the link is complete, and make sure there are no extra spaces or line breaks. For a parsing error, confirm that the subscription format is supported by your client; don’t randomly edit configuration fields to dismiss the warning. Keep any working configuration, then reimport using the method provided in the dashboard. If your client version doesn’t match the configuration requirements, check the download section of the dashboard for the current method. When submitting a ticket, include the exact error and where it appeared, and redact credentials in the link. This makes the issue easier to diagnose than a general report that it doesn’t work.

Waking a device from sleep or switching networks can interrupt the current connection. Usually, reconnect first rather than reimporting the subscription. Make sure the device is online, then disconnect and reconnect in the client. If the route list is still there and the subscription hasn’t changed, there’s no need to add the same configuration again. If reconnecting doesn’t work, check whether the system restricts the client’s background activity or has revoked its network permissions. If needed, quit and reopen the client, and check that the system clock is correct. Note whether the issue started after waking from sleep or switching networks, and whether reconnecting fixed it; that helps distinguish a local state issue from a route issue.

Identify the bottleneck before changing plans. Use the same device and content, pause background downloads and other data-heavy tasks, check that your local Wi-Fi is stable, and compare playback on different routes. Peak-hour congestion can occur on your local connection, cross-border links, or the destination platform, so a larger data plan may not improve speed. Try routes in other regions or with different connection types, and judge by sustained playback rather than the client’s probe results alone. If a route repeatedly has problems, note the time, region, and destination service and report them through a ticket. There’s no need to keep reinstalling the client.

These terms describe how a network path is arranged; the name alone doesn’t determine how it will perform. IEPL typically refers to a dedicated transport path across the cross-border segment. A relayed route connects to the destination exit through another access point, while a direct route depends more directly on routing between your local network and the exit. First check which region the destination service requires, then compare connection quality and sustained performance on your current network. Don’t rank routes by geographic distance alone or assume one type is always faster. This service covers 100+ countries / 230+ routes. The options available to you are shown in the dashboard and client; test routes against your actual use case.

Changing routes may change your network exit, but it doesn’t guarantee that the destination platform will allow access. Platforms may also consider account region, subscription eligibility, app cache, and their own risk checks. Check the platform’s published regional requirements, choose a route in a matching region, then fully quit and reopen the app before testing again. Confirm that traffic is using the selected policy group. If the website opens but sign-in or playback is still restricted, note the exact message rather than assuming every issue is a speed problem. This service’s route coverage isn’t a guaranteed list of platforms that will work. Results can vary between routes in the same region and should be checked for each feature you need.

A latency test measures the round trip for a single request; it doesn’t directly show sustained transfer performance. Downloads and video can also be affected by packet loss, link congestion, the destination server, local Wi-Fi signal, and background tasks. Low latency doesn’t necessarily mean smoother playback. When comparing routes, keep the device, network, and content consistent and check whether the actual task improves. If only one download source is slow, compare it with another source. If everything is slow, check your local network and the client’s routing status. Don’t judge long-term route performance from a single test, or treat dashboard status figures as a speed guarantee for destination websites.

Monthly plans: ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data packs: ¥158 for 300GB, ¥358 for 1000GB, and ¥658 for 3000GB. Data packs last until used and never expire. If you use the service regularly and your monthly needs are fairly consistent, choose a monthly plan based on your actual usage. If your usage varies, compare how data packs are billed. Before choosing, consider whether your typical use includes sustained data transfers such as video streaming or downloads; don’t estimate based only on the number of devices. Device limits and data allowances are separate. Check the pricing page for plan details, then choose in the dashboard.

Monthly plan data resets each month on the plan’s activation date. For a mid-cycle upgrade, the price difference is prorated for the remaining days. Resets don’t all happen at the start of the calendar month, and you shouldn’t assume a fixed upgrade payment amount. Before making a change, check your current plan, data usage, and the result shown on the upgrade page in the dashboard. If you’ve noticed a drop in data, first confirm whether you’re using a monthly plan or a data pack: data packs last until used, never expire, and don’t reset monthly. For plan changes or combinations with other options, follow the dashboard and confirm details through a ticket.

Supported payment methods: Alipay / WeChat Pay / USDT. Before paying, check the plan, amount, and payment method on the order in your dashboard, and follow the instructions on that order page. Don’t use payment details forwarded by someone else. If your status hasn’t updated after payment, check the order record and plan status in the dashboard before paying again; the page may simply not have refreshed. If you still need help, submit a ticket with the order ID, payment time, and a screenshot of the payment result. Hide account details that aren’t relevant. For USDT, carefully check the network and payment instructions on the order page. Don’t rely on an older order or share complete payment credentials in a public forum.

This service offers a 30-day, no-questions-asked refund. To request one, sign in to the user dashboard and use the ticket option to explain your request and provide the relevant order ID so the payment can be checked. See the refund section of the Terms of Service for full eligibility details. You don’t need to keep trying complicated troubleshooting steps before submitting a request, and you shouldn’t send your password or full subscription link as proof. If your payment went through but the plan hasn’t taken effect, explain that clearly in the ticket so it isn’t confused with a routine connection issue. Check the ticket replies in your dashboard for refund progress, the outcome, and related details; no processing or arrival time is promised on this help page.