Help Center · Frequently Asked Questions

No. No email address is required: a username and password are all you need, and you can sign in to the dashboard as soon as you're done. Because the account isn't tied to an email, store your username and password in a password manager; if the credentials are lost, there's no email-based recovery.

A subscription link is the address your client reads route configurations from, and it's tied to your account. After signing in to the dashboard, copy the subscription link from the overview or download area and paste it into your client to import it. Don't share this link publicly; if you suspect it has leaked, regenerate it in the dashboard.

No. The service doesn't limit the number of devices, so one subscription works across Windows / macOS / iOS / Android / Linux. Sign in to the same account on the new device, fetch the subscription and connect; there's no extra charge.

If the route list in your client shrinks, connections keep failing, or the dashboard says the subscription has been updated, copy the subscription link again and run an update in the client. You don't need to buy a new plan. After route changes, an old configuration may not see the new routes.

Accounts aren't tied to an email address, so password recovery doesn't rely on email. Save your username and password in a password manager right after signing up. If the credentials really are lost, check the recovery options on the dashboard sign-in page first; if that doesn't resolve it, open a ticket with your sign-up date and the details of your most recent order.

First check whether another app has taken over the proxy: close other proxy tools and reconnect. Then try a route in a different region. Finally, check whether per-app proxying is on and leaving the browser out of the route. If it still fails, open a ticket from the dashboard with your OS version, client version and the route name.

There are two common causes: the app has its own network stack and ignores the system proxy settings, or the app uses UDP while the client is in system-proxy mode and doesn't capture that traffic. Switch the client to global or TUN mode and try again, or add a rule that sends that app through the route.

Most often a character was dropped or a space slipped in while copying. Go back to the dashboard, copy the full link again and use the client's import-from-clipboard option. If the client only accepts configuration files, pick that client's format in the dashboard and import again.

That means all traffic is being routed through the tunnel. Switch the client back to smart routing so sites in mainland China connect directly and overseas sites go through the route. If it's still off, check whether you've manually added rules that override the defaults, clear the custom rules and reconnect.

The client covers Windows / macOS / iOS / Android / Linux. Whether a router, TV box or game console works depends on whether its firmware supports subscription import. If it does, the same subscription is all you need; if not, connect at the router level instead.

Peak-hour congestion mostly hits relay routes. In the client, switch from a relay route to an IEPL dedicated line, or move to a direct route in another region. Also check that no other device on the same network is running a large download. See the global nodes page for route types.

IEPL dedicated lines run on a private channel, so latency and jitter are steadier, which suits peak hours, real-time voice and gaming. Relay routes connect through forwarding nodes and cover more regions, which suits everyday browsing. Direct routes land nearby on the shortest path but depend more on local network quality. Pick by use case rather than fixating on one type.

Disconnect the client and first test ordinary browsing speed on your local network. Then connect to two routes in different regions and test each one. If only one route misbehaves, it's the route; if every route is slow and a direct local connection is slow too, the problem is your local network or your ISP.

90+ countries / 160+ routes across North America, Asia-Pacific, Europe and other commonly used regions. The global nodes page lists countries and cities grouped by region. Routes are adjusted according to how they perform, so the dashboard's available list is the authoritative count.

These apps are sensitive to latency and jitter, so prefer an IEPL dedicated line and turn on the client's TUN mode to make sure UDP traffic is captured. If voice breaks up, switching to a route that's geographically closer usually helps; avoid large downloads during calls.

Three monthly tiers: ¥9.9/month with 60GB, ¥18/month with 250GB, ¥28/month with 500GB. Traffic resets monthly on your activation date; if you upgrade mid-cycle, the price difference is prorated over the remaining days.

Two options: upgrade to the next monthly tier, with the price difference prorated over the remaining days; or buy a data pack, ¥158/300GB, ¥358/1000GB, ¥658/3000GB, which lasts until used up and never expires.

Alipay / WeChat / USDT. After ordering, choose a payment method on the order page in the dashboard to complete payment; the plan activates automatically once the payment clears. If it hasn't activated after a long wait, open a ticket with your order number.

The service offers a 7-day no-questions-asked refund. Open a ticket in the dashboard with your order number and what you'd like refunded; once it's verified, the money goes back through the original payment channel. How long it takes depends on that channel's processing speed.

Data packs last until used up, never expire, and are deducted in the order you bought them. If you want a refund after purchase, open a ticket under the same 7-day no-questions-asked policy and include the data pack order number.