VPNTA Complete Handbook

What this subscription gives you

VPNTA is an international route subscription for cross-border access. It bundles three things: a network covering 120+ countries and 220+ routes, clients for Windows / macOS / iOS / Android / Linux, and an account panel for managing your subscription, traffic and orders. What you pay for is not a software licence but a quota of routes available for a period of time.

Three components

Break the service down and every successful connection depends on all three layers below — miss one and nothing connects.

• Routes. 220+ routes across 120+ countries. By access type they fall into three groups: dedicated, relay and direct. Dedicated lines hold up better at peak hours, relay lines cut latency on intercontinental hops, and direct lines suit nearby access. You don't need to memorise the types — just pick a region in the client.
• Clients. Each of the five platforms has its own client, all available from the download page in the panel. The client only builds the tunnel and handles routing; it does not store your username or password — you import the subscription details yourself.
• Account. A username and password is all it takes — no email address required. The account shows your current plan, traffic used, expiry date, order history and the support ticket entry point.

What it's for

The purpose is straightforward: local network requests are forwarded through an overseas route and reach the target service from that route's exit. That gives four direct uses.

• Reaching international sites and services. Search engines, developer docs, open-source repositories, overseas shops and forums.
• AI tools and streaming. Conversational AI, image generation tools, and region-specific catalogues on video platforms.
• Cross-border work. Corporate email, online documents, video meetings, code hosting and remote servers.
• Link protection on public networks. On shared networks in hotels, airports and cafés, the hop from your device to the route is protected with quantum encryption.

What it doesn't promise

Stating the limits is more useful than listing selling points. Three things are outside the scope of the service — better to say so now than to clear up the misunderstanding later.

• No promise that a given catalogue stays available. Streaming platforms keep changing their regional policies; what opens today may move region tomorrow. The streaming access page records the current situation per platform, but any record lags behind.
• No promise of connectivity on every network. Upstream policy, route quality and OS version all affect the result. The same route can behave completely differently in two buildings.
• No promise to replace the user's own judgement. How cross-border access is used is up to the user; the service only provides routes.

How this page differs from the quick-start guide

The Guides page is a single track: create an account, get to your first page, and you're set — compact, and the right place to start. This page is the reference manual: it covers the same flow but spells out the reasoning, the branches and the troubleshooting path at every stage. Longer, and meant to be read in pieces.

Think of it this way: use the guides page the first time, then come back here for the chapter that matches your problem. The chapter bar at the top jumps straight to the section you need — no scrolling from top to bottom.

Choosing a plan: monthly subscription vs data pack

The billing model decides which resource you're paying for. Get that straight first, then worry about tiers — you'll be far less likely to pick wrong.

Two billing models

There are two distinct ways to pay, and you can buy either on its own or hold both at once.

• Monthly subscription: pay by the month, and each month comes with a traffic allowance that resets on your activation date. Unused traffic does not roll over, and if you don't renew, the routes stop working.
• Data pack: pay once for a total capacity, use it until it runs out, and it never expires. No time pressure — when and how long you use it has no effect on the remaining balance.

The one-line difference: a monthly subscription buys "how much per month for this period", a data pack buys "how much is left in total". Heavy users go monthly, occasional users go for a pack. You can also stack them — once the monthly allowance is used up, the client keeps drawing on the data pack balance.

Three monthly tiers

The only differences between the three tiers are monthly traffic and price. Routes, device count, payment methods and the refund policy are identical — that matters: there is no such thing as "worse routes on the cheap tier".

If you're unsure, start on the lowest tier. Monthly plans can be upgraded mid-cycle, with the difference prorated by remaining days — you don't buy a second plan. If real usage shows the allowance isn't enough, upgrade then.

Three data packs

The larger the pack, the lower the cost per unit of capacity. The three tiers exist for different usage cycles: one pack is enough for a short trip, a bigger one is more convenient as long-term backup — it doesn't expire anyway. Full pricing and terms are on the plans page.

How mid-cycle upgrades are calculated

A monthly subscription can be upgraded to a higher tier while it's still active. The system takes the price difference between the new and current tier, multiplies it by the days left in the billing cycle, and charges that — the upgrade takes effect once paid. Traffic already used on the original plan keeps counting; it isn't reset. Downgrades aren't offered: if you need a lower tier, wait until the current cycle ends and choose it then.

An example of the proration: upgrade from Starter to Standard halfway through the cycle and you pay roughly half the price difference, not a full month's. So the later you upgrade, the less you pay — but the less time you get at the higher allowance.

What unlimited devices actually means

Device count is unlimited. The same account can import the subscription on any number of devices without paying extra for a second or third. The limit isn't device count, it's total traffic: every device draws on the same allowance.

In practice, keep the number of devices online at once within the range you actually use. Not to save quota, but because the more devices there are, the harder problems are to trace — one device's abnormal traffic thins out what the others have left, and when something goes wrong it's hard to tell which one is responsible.

The refund safety net

Within 14 days of your first payment you can request a refund, no reason needed. This matters most for first-time users: picked the wrong tier, routes don't suit you, the client won't run — all covered. Refunds go back through the original payment channel; the process is in Chapter 8.

Worth saying: the refund is a safety net, not a trial. A day or two is usually enough to judge whether a set of routes works for you — no need to wait until day 14.

Signing up and ordering: no email address needed

By the end of this chapter you'll have a working account and an active subscription. Only two screens are involved: creating the account and paying.

Creating an account

Open the login link at the top right of the site's home page to reach the panel, then switch to account creation. Two fields: username and password. There's no email field and no email to receive — that's deliberate: one less step, and one less place where your information is stored.

Once created, the username isn't meant to be changed — it's your unique identifier in the panel. There's no email-based password recovery, so store the password in a password manager or offline. The creation screen says this too; it isn't buried in the terms.

Choosing a plan and paying

Once logged in, go to the plans page — three monthly tiers and three data packs are listed together. Pick the tier you need, confirm the amount, and continue to payment. Three methods are supported: Alipay, WeChat and USDT. The first two are QR-code payments; USDT is an on-chain transfer.

Don't close the page during payment. The result comes back via a redirect, and if the page is closed the order may sit in a pending state until you refresh the panel manually.

After paying

Once payment succeeds, the panel's overview page shows your current plan, expiry date and traffic allowance, and the orders page gains a completed record. From there, just read the status.

• The overview page already shows a plan — activation is done, go and get the subscription.
• The order shows as pending — usually the payment callback hasn't come back yet. Wait a minute or two and refresh.
• Still pending after ten minutes but the account has been charged — open a support ticket with the order number.

Common snags

• The payment page didn't redirect back. Most often the browser blocked the redirect. Go back to the panel and refresh manually — the order status in the panel is authoritative, not the message on the payment page.
• The QR code timed out. Codes are only valid for a limited time; start a new order. Duplicate pending orders won't charge you twice, and unfinished orders can be ignored.
• USDT sent but not credited. On-chain confirmation takes time and block confirmations are what count. Don't send again before it confirms, or you'll end up with two transfers.

About account information

The panel only needs a username and password — no name, address or ID documents. That's not an omission; the account system is designed that way: there's nothing to verify, so there's nothing to fill in.

If you use several devices, you don't need a separate account for each. One account, one subscription, imported onto as many devices as you like. Device management is covered in Chapter 8.

Getting the subscription: one link across five platforms

The subscription is the most important piece of the whole flow. It's a link; the client reads it and pulls the route list automatically. Once you understand it, importing on all five platforms is really the same task.

That's why one account can use the same subscription across platforms — the clients on all five read the same list, they just render it differently. It's also why switching devices doesn't mean buying again: you paste the link once more.

Where to get it

After logging in, both the overview page and the download page offer the subscription entry. Click copy, the link goes to your clipboard, then paste it into the client. The link looks roughly like this, with the token part unique to each account:

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

That's a shape illustration, not a usable link. Real links only appear in the panel after login; no page and no article will ever publish a working subscription link. If you see a "universal subscription address" posted somewhere, don't use it.

Keeping it secret

The subscription link is equivalent to a credential. Anyone who has it can import it on their own device and spend your traffic allowance without knowing your username or password. It matters as much as your password, but it's easier to overlook, because the link just looks like a URL.

• Don't post the subscription link in public forums, group chats or screenshots.
• Don't commit the link to a public code repository or config file.
• If the link has leaked, reset the subscription in the panel to invalidate the old one, then re-import the new link on each device.

Subscriptions update

Route adjustments, new regions and protocol parameter changes all show up in the subscription content. Have the client pull the subscription again and the new list appears — no reinstall, no repurchase.

Each client updates differently: some have an update button on the node list page, some hide it in settings, some pull automatically at a fixed interval. On desktop, update manually after a long break from using it; on mobile, update after switching networks. Build the habit and a lot of "my nodes disappeared" problems vanish on their own.

If the import fails, check these three first

• The link is incomplete. It got line-wrapped or truncated when copied, so the pasted length is obviously wrong. Copy it again, and make sure the token segment at the end isn't cut off.
• The link is no longer valid. If you reset the subscription in the panel, the old link stops working by design — use the new one.
• The client is too old. Some newer parameters aren't recognised by older versions; update the client and try again.

Those three cover the vast majority of import failures. If you've ruled them all out and it still won't work, note the client's error text and include it in your support ticket — it makes diagnosis much faster.

Desktop setup: install paths for three clients

Desktop is where most usage happens. The flow is the same on all three platforms: get the client, import the subscription, pick a route, connect. What differs is system permissions and installation method.

Where the client comes from

Always from the download page in the panel. Log in, go to the download page, choose the build for your system, download and install. Don't search for it on third-party sites — a client of unknown origin may bundle extras or read your subscription link.

The download page separates system and architecture. Picking the wrong architecture usually shows up as "cannot open" or "file is damaged" — just download the matching build; the installer itself is fine.

Windows

Run the installer after downloading and follow the prompts. On first launch the system may show a firewall prompt; the client needs to be allowed through, otherwise the tunnel never comes up and it sits at "connecting" forever.

Once installed, open the client, find the subscription or config import entry, paste the link you copied from the panel, confirm, and wait for the node list to load. When it does, pick a route and click connect. A status of connected means the tunnel is up — whether traffic actually goes through it is separate check, covered in Chapter7.

If the client asks for administrator rights, run it again as administrator. Some systems' network stacks need higher privileges to create a virtual adapter; that's not a fault in the client.

macOS

The macOS build is a disk image — drag it into the Applications folder. On first open the system blocks unsigned apps; allow it once in Privacy & Security in System Settings and the prompt won't return.

When connecting, the system asks you to authorise adding a network configuration. That permission is required to build the tunnel — choose allow. If you decline, the client stays stuck at connecting, and you need to re-authorise in System Settings rather than clicking connect repeatedly.

Linux

The Linux build comes as an archive or self-extracting file. Extract it, make the executable runnable, then launch. Tray icon support varies between desktop environments; if there's no tray icon, start it from the command line so you can see the log output — easier to diagnose.

Creating the tunnel interface requires root. The client usually requests elevation — enter your local password when prompted. If you launch from the command line, run it elevated, or set the appropriate capability on the executable.

Desktop comparison

All three platforms are functionally identical: same routes, same protocols, same routing rules. Which one you pick depends on the machine you work on day to day — it doesn't change what the plan includes.

Mobile setup: configuration notes for iOS and Android

Mobile differs from desktop more than you'd expect: the system puts extra limits on background processes, network extensions and battery, and the configuration steps differ too. This chapter takes each platform in turn.

iOS

The iOS client comes from the App Store. The download page in the panel provides the entry point: accounts with an active, unexpired plan can open the relevant page directly; accounts without one see a prompt to buy a plan first and come back. The download page says this clearly — no guessing required.

On first connection the system asks to add a VPN configuration and a configuration profile appears in Settings. You must allow it, otherwise the client can't take over network traffic. Once allowed, a connection indicator appears in the status bar.

There are two ways to import the subscription: paste the link inside the client, or open the subscription link in the system browser to trigger a jump. The former is more controllable — pasting is recommended across the board, so the link can't be truncated during the handoff.

Android

The Android client is distributed as an installer package from the download page in the panel. During installation the system asks permission to install apps from unknown sources; grant it once and it won't ask again.

On first connection the system shows a connection request dialog — tick trust and confirm. This dialog can appear every time a new tunnel is created; it's system behaviour, not the client repeatedly demanding permissions.

Background activity and battery

The most common mobile complaint — "it connects, then drops after a while" — almost always comes down to the system's power-saving policy. To save battery the system freezes background apps, the tunnel process gets frozen, and the connection drops.

• iOS: allow background refresh for the client in Settings, and turn off the low-power restriction for that app in Battery settings.
• Android: set the client to unrestricted in battery optimisation, and lock the app in the recent-tasks list.
• Both platforms: after switching between mobile data and Wi-Fi, go back to the client and confirm the connection state once.

Platform comparison

One more mobile point that's easy to miss: after switching networks, the old tunnel isn't rebuilt automatically. Walk from Wi-Fi to mobile data and the indicator may still be there while the connection is actually gone. Get into the habit of reconnecting after a network change — it saves a lot of "it says connected but nothing loads" confusion.

Connecting and verifying: how to confirm it's really working

Clicking connect isn't the same as it working. A client showing connected only means the tunnel is up; whether traffic actually goes through the route needs a separate check. This chapter covers route selection, protocols and verification.

Three rules for choosing a route

• Nearest first. Pick the region where the target service lives. Japanese content, Japanese route; US services, US route. Choosing across regions adds an unnecessary detour.
• Type second. When a region has several routes, prefer dedicated, then relay, then direct. Dedicated lines are noticeably steadier at peak hours — the difference is easiest to feel between 8 and 11 pm.
• If it stalls, switch. When one route jams, try another in the same region before changing region. Most stalls are a single route's problem, not the whole service's.

The full region and route list is on the servers page, grouped by region with cities and route types. Have a look before choosing — faster than trying them one by one in the client.

Choosing a protocol

Each route in the client is labelled with its protocol. Common ones include VLESS, Hysteria2 and Trojan. They all solve the same problem — getting data reliably to the other end over an unreliable link — and differ in congestion control and obfuscation.

• Use the protocol the client recommends by default; don't change it by hand. The recommendation reflects the route's actual configuration.
• On links with heavy packet loss, UDP-based protocols usually perform better — go by what the client labels.
• When you need to get through a tightly controlled corporate network, protocols on port 443 are more likely to succeed.

Three ways to verify it's working

Method one: check the exit address. Look up your current exit address before and after connecting. If they differ, traffic really is going through the route. This is the most direct method and the hardest to misread.

Method two: check the target site. Open an international site that normally won't load; if it loads, treat it as working. The downside is that it only proves "this one thing works", not that the whole path is healthy.

Method three: read the client log. Most clients keep a connection log showing whether the handshake succeeded, which route was used and whether anything errored. When something breaks, the log is far more useful than the UI status.

From the command line, you can check the path with a request that carries no account information:

# Checks link connectivity and handshake time only; no account information involved
curl -sS -o /dev/null -w "%{http_code}  %{time_total}s\n" https://example.com

A 200 response with acceptable timing means the path is clear. Any other status code or a timeout — go back to route selection and pick another.

Checking the failure branches

Always troubleshoot from the near end outwards: first confirm the client itself is running, then that the subscription is valid, then that the route works, and only then suspect the target site. Do it the other way round and you'll usually waste the most time on the furthest link in the.

Day-to-day upkeep: traffic, renewals and refunds

Connecting is only the start. After a while of use, what matters is how much traffic is left, when it expires, and whether the subscription needs updating.

Reading your traffic

The panel's overview page shows traffic used and remaining in the current billing cycle. Every device shares that allowance — phone, computer and tablet alike. There's no per-device split.

A monthly subscription resets on your activation date each month, not on the calendar month. Activate on the 12th and the 12th is your reset day. Unused traffic doesn't roll over, so factor that in when choosing a tier.

Data pack capacity doesn't change with time — it goes down as you use it, until it's gone. The panel shows the pack's remaining capacity separately from the monthly plan; the two don't offset each other.

Expiry and renewal

If a monthly subscription expires without renewal, the routes stop working. The nodes are still in the client but won't connect — easy to misread as a client fault, so check the expiry date in the panel before troubleshooting anything else.

Renew in the panel's plans page; payment methods are the same as the first purchase: Alipay, WeChat, USDT. Renewing before expiry doesn't waste the remaining time — the new period extends from the original expiry date.

When to update the subscription

• After a long break, update the subscription once before using it again.
• If the node list in the client is clearly shorter than the regions shown in the panel, update once.
• If it won't connect after changing device or network, update first, then troubleshoot.

Updating doesn't consume traffic and doesn't affect the current connection. Most clients support manual updates and some pull automatically at an interval — the setting lives in the client's settings or node list page.

Managing multiple devices

Device count is unlimited, but it's worth keeping your own device list: which device is in use, when it was set up, which platform it runs. Once there are several, the thing that gets confusing when something breaks is which one is still connected.

Switching devices needs nothing on the old one — just import the same subscription on the new device. If the old device is retired, uninstall the client. If you're passing it on to someone else, clear the subscription details from the client before uninstalling.

How to request a refund

Within 14 days of your first payment you can request a refund, no reason needed. The process: log in to the panel, open a support ticket stating that you want a refund and including the order number; once processed, the money goes back through the original payment channel.

• The refund is calculated from the first payment — it doesn't apply to every renewal.
• USDT orders are returned to the original address, so include the receiving address in the ticket.
• Once the refund completes, the corresponding subscription is disabled immediately and used traffic is no longer settled.

If it's just that one tier doesn't suit you, consider a mid-cycle upgrade before a refund — the upgrade prorates the difference by remaining days, which is less hassle than refunding and buying again, and you don't lose the time you've already paid for.

Advanced usage and troubleshooting quick reference

This chapter is for people who are already up and running and want things to go more smoothly. The first half covers a few settings that make a visible difference; the second half is a lookup table from symptom to cause.

Routing rules

Routing means sending some traffic through the route and letting the rest go direct. Configured sensibly, you get both at once: cross-border access through the route, local services at their original speed and latency.

• Route by domain: list the domains that need cross-border access and let everything else go direct. Good when your usage is well defined.
• Route by region: non-local addresses go through the route, local addresses go direct. Good for everyday mixed use.
• Global mode: everything goes through the route. Fine for temporary troubleshooting, not for long-term use — local services slow down noticeably.

You don't need to write all the routing rules at once. Start in global mode to confirm the route works, then add rules gradually — when something breaks it's much easier to tell which rule is at fault. Do it the other way round, starting with dozens of rules, and you'll have almost nowhere to start.

Household sharing and multiple devices

Device count is unlimited, so one account for the whole household is workable. What needs watching isn't the number of devices but the traffic: several devices streaming at once multiplies consumption.

If you have a router at home, you can import the subscription onto the router and let every device in the house go through the route automatically. That saves configuring each device, but it also means all traffic shares one allowance — best combined with routing rules. For a detailed comparison of multi-device setups, see the multi-device VPN recommendations hands-on test.

Streaming and AI tools

These two uses put different demands on a route. Streaming cares about bandwidth and region; AI tools care about stability and a consistent exit.

• Streaming: pick a route in the target region, dedicated if possible. 4K playback is bandwidth-hungry, especially at peak hours — avoid relay routes during that window.
• AI tools: pick a fixed route in one region and avoid switching exits often. Frequent exit changes can trigger risk controls on the other side, which shows up as repeated identity checks.

The streaming access page maps platforms to regions; when a specific platform won't open, check there first. For picking routes for Japanese content, see the Japan route test.

Troubleshooting quick reference

When to contact support

Before opening a ticket, have three things ready: the platform and client version you're using, the name of the route that's failing, and the client's error text or a screenshot. With those, diagnosis usually takes one round; without them, back-and-forth confirmation drags on.

The ticket entry in the panel is in the account menu. Tickets are handled asynchronously — after submitting, you can see replies and status on the ticket page, so there's no need to submit again.

One last thing: reading through this takes about twenty minutes, but it saves you re-figuring things out every time something goes wrong. If you don't have an account yet, start with the lowest monthly tier — if it doesn't suit you, you can refund within 14 days.