Subscription & Connection Help

No email address is required. Create an account with a username and password. Store both in a trusted password manager, and use a password you don't use on other sites. After creating your account, make sure you can sign in to the dashboard before downloading a client or choosing a plan. Since your account isn't linked to an email address, don't rely on email recovery as your only recovery option. If you have trouble signing in, check your username, keyboard input and password autofill. If the issue persists, find the support ticket link on the Contact page and provide only the account and order details needed to investigate. Never send your password or full subscription link.

Sign in to your dashboard and find the subscription link in your account overview. Copy it or import it into your client as prompted. If you already have a subscription, find it in your client's subscription or configuration manager and update it, then check that the groups in your server list have refreshed. If the update fails, make sure your network can reach the dashboard and that you copied the full link. Don't use the dashboard page URL as your subscription link. If the dashboard has reset your subscription link, replace the old entry with the new one; repeatedly updating the old address usually won't fix the issue. Your subscription details and plan status are shown in the dashboard.

There is no limit on the number of devices that can be connected at the same time, so switching devices alone doesn't require a new plan. Supported platforms: Windows / macOS / iOS / Android / Linux. Sign in to the same account on your new device, get a compatible client from the dashboard, and import your subscription. Clients are available after sign-in on all platforms except iOS; check the dashboard for iOS availability. Installing a client and having an active subscription are separate things, so check your plan status before connecting. Keep an eye on your data usage as you add devices—unlimited devices doesn't mean unlimited data.

Treat your subscription link like an account credential and protect it as you would a password. If you send it to the wrong person, share it in a public screenshot or notice unexpected use, look for the subscription reset option in your dashboard and follow the prompts to replace the link. If you can't find the option, request help through a support ticket. After resetting it, replace the subscription address in your own client and update the configuration. Don't keep using the old address for routine imports. Also check whether your account password was exposed and change it if needed. Before submitting screenshots, hide subscription links, access credentials and private payment details. Support usually doesn't need your full subscription link to investigate.

Disconnect the client and check that your local network can access familiar websites. If your basic connection is having problems, fix that first. Then check your plan status, available data and whether the client subscription is up to date in the dashboard, and test a route in another region. If only a particular site won't load, note its error instead of assuming all routes are unavailable. Check that your device's clock is correct and that no other proxy or network-routing tools are running. Change one setting at a time and note the result to help distinguish account, route and local-device issues.

Your browser and app may use different network paths. Check whether the client only has the system proxy enabled and whether its current rules send the app or domain directly. Some apps don't use the system proxy and need another routing mode supported by the client; check the client interface for the relevant settings and permissions. After changing settings, fully quit and reopen the app so it doesn't keep using an existing connection. If the issue persists, note the app name, device operating system, client mode and error message, then contact support through a ticket. Avoid changing rules, protocols and routes all at once, so the cause remains clear.

First, make sure you're using the subscription link from your dashboard and that it wasn't truncated or copied with extra spaces or punctuation added by a messaging app. Check that your client supports the subscription format and protocols it contains. If the format isn't supported, switching routes usually won't help; choose the appropriate import method in the dashboard instead. If the subscription worked before but the server list is now empty, check your plan status and whether the subscription address was reset. Keep the exact error shown by the client, but don't post the full link publicly. When submitting a ticket, say whether you copied the link manually or imported it from the dashboard, and where the process failed.

Submit your issue through the support ticket link in your dashboard. Include your device operating system, client name, selected region, route type, protocol and the approximate time the issue occurred. Say whether all websites are affected or just a particular app or site, and list the troubleshooting steps you've tried and their results. If there's an error message, include a screenshot with sensitive details hidden or a relevant log excerpt. Don't send your account password, full subscription link or private payment details. A clear description of what you expected and what actually happened is more useful than simply saying it doesn't work. If the issue changes, add the new details to the existing ticket.

First, check whether the same buffering happens with content accessed directly over your local connection. This helps rule out congested Wi-Fi, background downloads and device performance issues. If the problem mainly affects international traffic, compare route types to the same website, then try other regions and see whether buffering or connectivity improves. Peak-hour performance depends on your local ISP, the international route and the destination service; a closer region isn't always faster. Keep the client mode and playback settings unchanged while testing so you don't vary several things at once. If the problem continues, include the time, region and comparison results in a support ticket to help with troubleshooting.

These terms describe different ways a route is set up, not different protocols. A direct route typically connects the client straight to the relevant exit. A relayed route forwards traffic from an entry point to a downstream exit. IEPL describes the use of a dedicated private link. Your experience still depends on your local network, the entry path, the exit and the destination service, so the route name alone can't tell you how fast it will be. For everyday use, choose a destination region first, compare the available route types and keep the option that is stable and suits your needs. For the difference between protocols and route topology, see the protocol guide. The dashboard and your client subscription show what's currently available.

The service covers 100+ countries and 180+ routes. Check the dashboard and your updated subscription for the regions and routes currently available. A region indicates a selectable exit location; it doesn't guarantee ongoing access to any platform or streaming library. Streaming availability can also depend on platform policies, account region, exit detection and licensing, so check the actual connection. After switching regions, close and reopen the app to make sure it isn't reusing an old connection. If only one platform is affected, include its name, the selected region and the error in a support ticket. Example route lists aren't guarantees of content availability.

Choose a protocol supported by both your client and the current route, and start with the import method recommended by the dashboard or client. A protocol's name alone doesn't determine speed; device performance, your local network and the route all affect your experience. If your connection works and the destination service is available, there's no need to switch frequently just to use a newer-sounding protocol. If a connection fails or performs poorly on a particular network, compare other supported protocols while keeping the region and test destination the same. See the protocol guide for design trade-offs; actual support depends on your client and current subscription.

Monthly plans: ¥9.9/month for 60GB · ¥18/month for 250GB · ¥28/month for 500GB. Data packages: ¥158 for 300GB · ¥358 for 1000GB · ¥658 for 3000GB. Data packages don't expire and remain available until used. If you use the service regularly, compare monthly plan tiers against your actual data use in the dashboard. If your usage is less predictable, consider a data package. Check both the billing model and data allowance when choosing: unused monthly data isn't retained indefinitely, and data packages don't renew each month. See the Plans page for full pricing. Your dashboard shows which options apply to your account.

Data resets monthly on your activation date. If you upgrade mid-cycle, the price difference is prorated for the remaining days. Check the reset date and account status in your dashboard; don't assume every account resets at the start of the calendar month. Before upgrading, confirm the target plan and order details in the dashboard rather than estimating the outcome from listed prices alone. If your data use differs from what you expected, check whether other devices, background syncing or downloads are still using the connection. If you have questions about your upgraded status, submit the relevant order details in a support ticket and keep your original order information for reference.

We accept Alipay / WeChat Pay / USDT. Start the payment through the Plans and Orders flow in your dashboard, and follow the instructions shown on the order page. After paying, return to the dashboard to check the order status and plan. Don't assume your plan is active just because the payment page closed. If payment is complete but the status hasn't updated, first make sure the order belongs to the account you're checking, then refresh the order page. If the issue persists, submit the order ID and redacted payment details through a support ticket. Don't pay again for the same order while its status is unclear, and never post private payment information publicly.

We offer a 14-day no-questions-asked refund. To request one, sign in to your dashboard, open a support ticket and clearly state that you'd like a refund, along with the order details needed for verification. Before submitting, read the refund policy in the Terms of Service to understand what's covered; the full eligibility requirements are set out there. You don't need to complete every network troubleshooting step before requesting a refund. You can describe connection issues and your refund request separately. Provide only the information needed to verify your order—never send your account password or full subscription link. Follow the request through your dashboard ticket, and don't assume a specific arrival date or payment provider processing time.