Six Steps to Cross-Border Access

VPNDX keeps accounts deliberately simple: no email address is needed — a username and password are enough. The upside is a short flow and no handing your email to a third party; the trade-off is that password recovery has no email channel, so keep your password safe. Use 6 to 20 letters and digits for the username, which also identifies you in support tickets, and at least 10 characters for the password, mixing upper and lower case with digits.

Click the button below to open the registration page in the dashboard. Fill in the two fields and submit — you land in a logged-in state straight away, with no “go check your email for a confirmation link” step. If you already registered and simply switched browsers or cleared your cache, use the login page and sign back in with the same username and password. The dashboard keeps your session in the browser, so a new device means logging in again — your plan is unaffected.

After registering you land in the Account Overview section. Your account has no active plan yet, so the subscription details there are empty — that is expected. The next step is choosing a plan.

VPNDX offers two billing models. Work out which one fits you before ordering and you can skip a refund later. The first is a monthly subscription, with data resetting every month: ¥9.9/month for 60GB suits light browsing and research; ¥18/month for 250GB suits everyday work plus the occasional video; ¥28/month for 500GB suits regular 4K streaming and several devices at once. Data resets each month on your activation date, and if you upgrade mid-cycle the price difference is converted into the remaining days, so you do not pay twice.

The second is a data pack: it lasts until used up and never expires — ¥158/300GB, ¥358/1000GB, ¥658/3000GB. It is for people who do not connect often but need it to be there when they do: two or three months of travel a year, for example, or a backup server. If your monthly usage is steady, the monthly subscription has the lower unit price; if it comes in bursts, a data pack will not waste anything when the month rolls over. Not sure how much you use? Start with a rough estimate — two hours of browsing a day plus two shows a week — and match it to the tiers above.

How to order: open the plans section of your dashboard, select a tier and click buy. The checkout page lists the amount and billing period; confirm it to continue to payment. Three payment methods are supported: Alipay, WeChat and USDT. Do not close the page after paying — the dashboard polls the order status automatically, and your plan activates within seconds to a minute, with the expiry date updating on the overview page. Your first payment is covered by a 30-day money-back guarantee, which is set out in the Refund Policy — worth a look before you order.

If the overview page does not update after you pay, refresh it once. If the plan still is not active, open a ticket in the Tickets section with your order number and payment time — that is the fastest way to get it sorted.

Once your plan is active, go back to the Account Overview section and find the subscription card. It shows your remaining data, expiry date and a subscription URL. That URL is how clients pull the server list, so copy it — you will need it on every platform. Some clients want a specific format; the card offers a switcher. If you are not sure which to pick, start with the universal format, which almost every client accepts.

Three things are worth remembering about this link. First, it contains your access credentials — anyone who has it can use your servers, so do not post it on public forums, in group chats or in screenshots. Second, it is long-lived: you do not need to replace it while your plan is active, and clients re-fetch it on a fixed interval, so servers added or removed are synced automatically without you changing anything. Third, if your subscription URL leaks, you can reset it from the same card; the old URL stops working immediately, and you just import the new one into your clients.

https://example.com/sub?token=YOUR_TOKEN

The line above is a format example, not a working URL. Copy your real one from your own dashboard, and paste it only into your own clients.

The idea is the same on all four platforms: install a client, give it your subscription URL, and let it pull the servers. Only the menu location and system permissions differ. VPNDX offers clients for Windows, macOS, iOS, Android and Linux; downloads all live in the Downloads section of the dashboard, which requires a login and an active plan. This site never hosts direct installer links.

Windows

In the Downloads section of the dashboard, choose Windows, then install and open the client. On first launch it asks you to log in with your dashboard account; once you do, the subscription is written automatically and the server list appears. If your client version has no one-click login, go to the Subscriptions / Profiles page manually, choose “Import from URL”, paste the address you copied in the previous step, save and hit update once. If the first connection fails, check that you allowed the network permission prompt from Windows — it appears the first time a virtual adapter is created, and if you decline, the client looks fine but traffic never goes through the server.

macOS

macOS works much the same as Windows: choose macOS in the Downloads section, install and open it, then log in or paste the subscription URL manually. The difference is that macOS asks you to approve a network extension and enter your local password — this step is mandatory, or the Connect button does nothing. Once approved, the client sits in the menu bar, where you can switch servers from the icon. On an Apple silicon Mac, pick the build for your architecture so it does not run through a compatibility layer and start slowly.

Android

On Android, first install a client that supports subscription import from the system app store. Open it, find the Profiles or Subscriptions page, choose “Import from URL”, paste the subscription URL and save — the client pulls the server list immediately. The first time you connect, Android shows a “VPN connection request” dialog; you must tap OK, since Android requires it and the tunnel cannot be established otherwise. It is also worth adding the client to the system's battery optimisation whitelist, or the system will reclaim it in the background and the connection will drop a few minutes after the screen locks. The exact path lives under Settings → Apps, and the wording varies by manufacturer.

iOS

On iOS, install a client from the App Store and paste the URL into its subscription page. When you connect, iOS asks to add a VPN configuration and requires Face ID or Touch ID to confirm — this happens only once. A common iOS pitfall is the “Connect on Demand” switch: with it on, the system reconnects whenever it sees fit, including times you thought you were disconnected, so data can drain faster than expected. Leave it off at first and turn it on later once you know your usage. iPad works exactly the same as iPhone.

Once the import finishes, the client lists every server. Servers are grouped by region and labelled by type: IEPL dedicated lines run on their own path and hold up best at peak hours; relay servers forward through an entry point in mainland China and are the most broadly compatible; direct connections have the lowest latency but are the most sensitive to your local network. For a first run, pick an IEPL line close to you. To see which cities and server types each region has, check the full list on the Servers page.

Never download a so-called “VPNDX client” from a third-party site. Clients are only available from the Downloads section of the dashboard; installers from uncontrolled sources come with no security guarantee.

Pick a server in the client and click Connect. A “Connected” status only means the tunnel is up — it does not prove your traffic is going through it. Per-app rules, system proxy settings and a browser's own proxy can all send traffic around the tunnel. Spending a minute on the three checks below saves a lot of wondering why a site still will not load.

Step one: check your exit IP. Open the My IP page, which shows your current exit IP and its location. Look before and after connecting: if the location changes to the country or region of the server you picked, your traffic really is leaving through it. If it still shows your local location, the tunnel is not in effect — go back to the client and check whether your per-app or routing rules exclude the browser you are using. Step two: check DNS. The same page reports your DNS resolution; if the resolver still shows your local ISP, you have a DNS leak and web traffic may still be resolved locally. Change the client's DNS option to “use tunnel DNS” or to follow remote resolution. Step three: run a real-world test — open a site that would not load before, or launch an AI tool that needs an international route. If it loads, you pass.

Once all three checks pass, do two small things: mark the server as a favourite in the client for one-tap switching next time, and, on mobile, confirm the client is on the battery optimisation whitelist. After that you can leave the configuration alone — server changes sync automatically through the subscription.

That is the main path done. The sticking points below are the ones beginners hit most; try them in order and most problems clear up on the first try.

• No servers in the client: the subscription did not load. Check that the URL was copied in full (a missing tail is the usual culprit) and that no line break cut it short, then click “Update subscription” manually. If the list is still empty, confirm your plan is still active.
• Connected but pages will not load: usually DNS or per-app rules. Run the three checks from step 5 to narrow it down, then adjust accordingly.
• Noticeably slower at peak hours: switch to an IEPL dedicated line. Dedicated lines run on their own path, and the difference at peak times is most obvious against standard relay servers.
• Mobile drops a few minutes after the screen locks: add the client to the system's battery optimisation whitelist and allow it to run in the background in system settings.
• One device will not connect: first confirm your account is in good standing (there is no device limit, so you cannot be over one), then check that the device's clock is accurate — a large system time offset makes the encrypted handshake fail.

If you have worked through the list in order and still cannot connect, open a ticket in the Tickets section of the dashboard and include your client name and version, operating system, the server you picked, and the exact error text or a screenshot. With complete details, most cases are diagnosed in one round. A more systematic guide — organised by symptom, covering no connection at all, connected but pages will not load, slow speeds, frequent drops, failed subscription updates and DNS problems — is in Troubleshooting, and the common questions about accounts, billing and connections are in the Help Center.