VPN Beginner's Guide: 10 Common Questions Answered

What actually trips up VPN beginners usually isn't the install step — it's the string of questions that follows: can one account run several devices at once, how is data counted, why do some sites still fail to load once you're connected. This guide lines up the ten questions beginners ask most in the order they tend to come up, with an answer you can act on for each. Anything about pricing, billing periods or refunds follows the VPNDH plans page and terms page.

How to read this: you don't have to go top to bottom. Skim the three figures below for a baseline, then jump to the section that matches the problem in front of you. Each section stands on its own, and the last one is worth coming back to once your setup is done.

How many devices can one account run at once?

The answer is no device limit. VPNDH subscriptions aren't priced per device: Windows, macOS, iOS, Android and Linux can each import the same subscription, and running desktop and mobile at the same time costs nothing extra.

That said, no device limit doesn't mean you can pass the subscription around. The subscription link is itself the account credential — anyone who has it can import it into their own client. Posting it in a public group, on a forum or in a screenshot is effectively handing over your account. The safe habit is to import it only on your own devices, and remove the profile from the old device before moving to a new one.

One more thing people overlook: bandwidth is shared. The more devices online under the same account at once, the less throughput each one gets, especially at peak hours. When two or three devices at home are on calls, streaming and downloading at the same time, that's usually where the slowdown comes from — not from the account being individually throttled.

A note on sign-up: you only need a username and password, no email address, so you never get stuck waiting for a verification mail that doesn't arrive or a link that has expired.

How is data counted, and what happens when it runs out?

VPNDH has two kinds of data: the monthly allowance included with a subscription, and standalone data packs. The rules differ, so start with the table.

Resets monthly on your activation date deserves unpacking: the reset day is the same date you signed up, not the 1st of each month. Sign up on the 8th and your next cycle starts on the 8th of the following month. The only way to change that rhythm is to start a new subscription — there's no toggle for it in the client.

When you upgrade mid-cycle, the price difference is prorated by the days remaining and takes effect the same day; you don't wait for the current period to end. For beginners, it's safer to start on a small tier, confirm the routes and your use case work, then upgrade based on real usage rather than picking the biggest tier on day one.

Data packs suit a different pattern: a business trip, exam prep, a short project — heavy use for a stretch, then almost nothing. They last until used up and never expire, so a month away from the client doesn't wipe them.

Are speeds throttled?

No provider can promise no throttling, because speed is never decided by one party. At least four layers affect what you feel: your local upload bandwidth, congestion on the cross-border route, the route type (dedicated / relayed / direct), and the response of the destination server itself. Cross-border routes slowing down at peak hours is normal everywhere — it isn't specific to one provider.

Three things you can control:

• Route choice: dedicated lines are usually steadier than relayed ones at peak times, at the cost of fewer regions to choose from.
• Protocol choice: UDP-based protocols (Hysteria2, TUIC) do better on lossy routes, but simply won't connect on networks that block UDP.
• Usage habits: let split tunneling rules send domestic sites direct — it saves both data and route bandwidth.

To judge whether you're being throttled, don't rely on a single speed-test page. A more practical approach is to retest with your real workload: join the same video call at 8 p.m. and again at 10 a.m., pull the same large file in both windows, and see whether it feels the same. Speed-test results shift with node, time of day and protocol; a single number proves nothing.

Do I need to leave it on?

No. A VPN is a route you switch on when you need it: for international sites, overseas AI tools, cross-border work. For local banking, your company intranet or casting to a device on your own network, turning it off is simpler.

On desktop, split tunneling rules are a better habit than switching on and off all day: set domestic domains and IP ranges to direct and let everything else go through the proxy, and the client decides for you. That way even with the VPN left on, domestic sites don't take a detour.

On mobile, battery matters. On Android, add the client to the battery-optimization allowlist so the system doesn't kill it in the background and drop the connection; iOS manages background network extensions more strictly, so disconnecting manually when you won't need it for a while saves more power than leaving it running.

One last reminder: turning it on over public Wi-Fi is worth it, but encryption protects the transport link, not the site itself. On a login page of unknown origin, don't enter your credentials even with the VPN on.

How do I import a subscription link into the client?

The five platforms have different client interfaces but the same import logic: you give the client the subscription link and the client pulls the node list. Follow the five steps below, in order.

1. Copy the subscription link from the user panel. This link works like a password — don't post it in a group and don't share it in a screenshot.
2. Open the client, find the 'Subscription' or 'Profiles' entry, and choose import from clipboard.
3. Run 'Update subscription' once and check that the node list shows regions and route types (dedicated / relayed / direct).
4. Pick a route and connect. Windows and macOS ask for network permission on first connect, iOS shows a VPN configuration prompt, Android requests VPN permission — all of them need you to allow it.
5. Open an international site to confirm it's working. If it isn't, go back to step 3 and update the subscription again before trying a different route.

Platform differences come down to permissions and background policy: Windows and macOS need the client's network extension allowed; Android needs the battery allowlist handled separately; Linux usually imports the subscription in a terminal and takes over all traffic in TUN mode. On iOS the configuration is managed by the system — deleting it means re-importing the subscription, and the client's 'Reconnect' button won't bring it back.

Connected but some sites won't load?

This is the most common complaint from beginners, and the cause usually isn't the route itself. Work through the checks below in order; most cases you can fix yourself.

Start with split tunneling. In rule mode, some domains get classified as domestic and go direct; a site that needs the proxy but isn't in the rules shows up as connected but won't load. Rules match top to bottom, so put specific domains before GEOIP:

rules:
  - DOMAIN-SUFFIX,openai.com,PROXY
  - DOMAIN-SUFFIX,github.com,PROXY
  - DOMAIN-SUFFIX,cn,DIRECT
  - GEOIP,CN,DIRECT
  - MATCH,PROXY

Next, DNS. If the system DNS is still handed out by the local network, a domain can resolve to the wrong address, which shows up as a page that spins forever or a connection-reset error. Point the client's DNS at proxy-side resolution, or set a trusted DNS manually — that usually fixes it.

Then confirm the proxy is actually carrying your traffic. In browser-only proxy mode, other apps don't use the route; switch to TUN or virtual network adapter mode when you need it system-wide.

Only then suspect the destination site. Some services restrict access by the account's registered region or payment method, and no route will change that.

Free VPN vs paid VPN: what's the difference?

Free options aren't unusable — you just need to know what you're paying with. Lay the four dimensions out side by and the choice gets much clearer.

The real problem with free options usually isn't speed but uncertainty: a route that works today may be gone tomorrow, rules change after a client update, and the terms are vague about how your data is used. For the occasional lookup, that's an acceptable trade. Once daily meetings, long file transfers or a dashboard you need to log into reliably are involved, uncertainty itself is the cost.

Which protocol should I choose?

That row of protocol names in the client is really a set of different transport methods. Beginners don't need the parameters — knowing which link each one suits is enough.

A few practical conclusions:

• The protocol the client selects by default usually already matches the route — no need to change it by hand.
• When it won't connect, change the route first and the protocol second; doing it the other way round wastes a lot of time.
• UDP-based protocols get throttled or blocked outright on some networks, which shows up as connects, then drops immediately.
• Whichever you pick, traffic is encrypted locally before it leaves, and the transport layer is handled with military-grade encryption throughout.

If you remember one line: the protocol decides how traffic travels, the route decides where it travels from. Most beginner problems come from the second one.

Payments, refunds and data packs: how do they work?

There are three payment methods: Alipay, WeChat and USDT. The first two credit instantly; USDT suits cases where regular payment channels aren't convenient, and the time to credit depends on on-chain confirmations.

The refund policy is 60 days: a full refund, no reason required, within 60 days of your first payment. This is the most useful part for beginners — picked too large a plan, the routes don't suit you, used it for a week and found it doesn't fit your workflow: you're still inside the window. Note the terms limit it to within 60 days of the first payment, so think about your usage before renewing.

Data packs follow different rules from monthly subscriptions: they last until used up, never expire, and don't reset with the monthly plan. After purchase, check the remaining balance in the user panel rather than relying on the client's estimate.

When you upgrade, the price difference is prorated by the days remaining. After the change, confirm in the user panel that the new data allowance is active before you start using it.

The five mistakes beginners make most

Once your setup is running, come back and check these five — they save a lot of back-and-forth.

• ❌ Forwarding the subscription link like an ordinary URL. The subscription link is an account credential; passing it on is lending out your account.
• ❌ Testing once at a single time of day and drawing a conclusion. Cross-border routes vary noticeably by hour — test again at peak time to get an accurate picture.
• ❌ Switching routes without updating the subscription. The client is still using the old node list, so it looks like switching did nothing.
• ✅ Set up split tunneling before talking about speed. Sending domestic sites direct saves a lot of data and takes pressure off the route.
• ✅ Remember the refund window. A full refund, no reason required, within 60 days of first payment — don't force yourself to stick with something that doesn't fit.

Ten questions down, and only three things really shape day-to-day experience: whether the route matches your use case, whether your data tier is enough, and whether you can troubleshoot in order when something breaks. For everything else, the defaults are usually fine.