Help Center

No email address is required — a username and password are all you need. After logging in to the user panel, choose a monthly plan or a data pack; access is activated as soon as payment completes and the subscription link appears in the overview section. Use a username and password unique to this service rather than reusing ones from other sites.

The panel login page has a recovery entry point; follow the prompts to reset your password with the username you registered. Registration isn't tied to an email address, so the reset happens entirely on-site and no link is sent by email.

If self-service reset doesn't work, open a ticket with your registered username and support will verify and handle it; if you can't recall the username either, add your registration date and payment records to make verification easier.

Log in to the user panel and copy the subscription link from the overview or download section, then paste it into your client to import the route list. The subscription link is equivalent to account credentials — don't post it in public groups and don't share screenshots of the full link.

To use it on a new device, just log in to the panel again and copy a fresh link; there's no need to buy again. Both the client and subscription entry points live in the user panel — marketing pages never provide subscription addresses.

No. The subscription follows your account, isn't tied to a specific device, and there's no limit on simultaneous connections. After switching computers or phones, log in to the panel on the new device and re-import the subscription link — your existing subscription keeps working.

No limit. Windows, macOS, iOS, Android and Linux can connect at the same time, and you don't need a second subscription for a second device. If several people share an account, each should keep their own client configuration and not pass the subscription link around.

First confirm the subscription is imported and not expired, then try another route, then check that the system clock is accurate and the client has the system permissions it needs, and finally restart the client.

If all four steps fail, submit a ticket with the client name, OS version, selected route and a screenshot of the error — diagnosis is much faster that way. Error text is more useful than a description of symptoms, and a screenshot showing the time and selected route is even better.

There are three common causes: the client is in rule mode and that app's domain is being routed direct; the app has its own network stack and ignores the system proxy settings; or the app relies on UDP, which the current route or protocol doesn't support.

Switch to global mode and test once — if it works, the issue is the routing rules, so go back to rule mode and add a rule that proxies that app. If it still fails in global mode, the app almost certainly ignores the system proxy and needs its own in-app proxy settings.

You can't decline. That system prompt is required to write the VPN configuration; if you tap Decline, the configuration isn't installed and the client keeps showing as disconnected.

If you tapped it by mistake, check the configuration status under VPN & Device Management in system settings, delete the old configuration and import it again. On iPhone, the first connection shows the same confirmation once more, and you need to allow that too.

It's usually a system extension or network permission that hasn't been allowed. Go to Privacy & Security in system settings and check for any blocked extension, allow it, then restart the client; if it still fails, delete the old configuration and import it again.

Company-managed computers may have VPN configuration restricted by MDM policy; that requires an administrator to allow it, and the client itself can't get around it.

First check that security software isn't blocking the client and run it as administrator if needed; then switch protocol and route in the client and retry — swapping WireGuard and OpenVPN often gets around a handshake problem on one particular path.

If only one route fails, switch routes; if every route fails, check whether your local network blocks the relevant ports.

Linux is one of the supported platforms. Log in to the panel, copy the subscription link and import it into a client that supports that subscription format. On a command line, keep the client process running in the background, otherwise the connection drops when the session ends.

Switch route type first rather than reconnecting to the same route over and over. IEPL dedicated lines run on a separate channel and are least affected at peak hours; relay comes next; direct routes are most sensitive to local egress quality.

Then look at your own side: move Wi-Fi to 5GHz or go wired, pause bandwidth-heavy downloads and cloud-drive sync, and test again. Comparing two routes in the same time window says more than a single speed test.

IEPL dedicated lines run on a separate channel from entry to exit with no competition from other traffic — highest cost, best stability. Relay stitches two links together with one forwarding hop at an intermediate node — price and experience sit in the middle. Direct routes connect straight into the exit data centre, so latency depends on the public internet quality between your local network and that data centre — a good fit when your local conditions are solid and cost matters.

What decides speed is the public link from your local egress to the entry data centre, not the exit end. On the same server, users on different ISPs and in different cities take different paths, so the experience naturally differs.

When choosing a route, look at the link quality from your own region to the entry rather than the route name alone. The full list of regions and route types is in the route list.

Not necessarily. 4K playback is sensitive to both bandwidth and link stability; packet loss and jitter cause buffering more often than peak bandwidth does. Choose an IEPL dedicated line and stay on a wired connection.

If the platform says the region is wrong, switch to a route in that platform's region instead of reconnecting to the current node repeatedly.

The base part of latency is set by physical distance — intercontinental access is naturally higher than same-city access. Judge route quality by stability: whether latency on the same route holds steady over time, and whether there's packet loss or spiking. A single latency reading is only a reference and can't be used to rank routes on its own.

Monthly plans come in three tiers: ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Data resets monthly on your activation date, not on the 1st of the calendar month — the day you activate is your monthly reset day.

The three tiers differ only in data allowance; routes and platform support are identical. See plans and pricing for the full comparison.

Upgrades are prorated by the remaining days; pay the difference and it takes effect immediately, with no need to wait for the next reset day. The amount due is calculated on the upgrade page in the panel before you confirm.

A monthly plan resets its data every month and suits steady long-term use; a data pack is prepaid quota that lasts until it's used up and never expires, which suits occasional business trips or irregular usage.

Data packs come in three tiers: ¥158/300GB, ¥358/1000GB and ¥658/3000GB.

Three: Alipay, WeChat and USDT. After placing an order, pick one on the payment page to complete the payment, and the order status updates in the panel. If the status doesn't change right away after paying, refresh the order list first.

60-day no-questions-asked refund. Submit a ticket in the user panel with the order number and the reason, and support will verify it and refund to the original payment channel.

How long it takes depends on the payment channel's processing speed, and the order status in the panel updates accordingly. Refund requests are matched to an order number, so if your account has several orders, say which one it is.