VPN Beginner's Guide: Account, Subscription Link & Public Wi-Fi Safety

How to store a subscription link, what risks public Wi-Fi carries, and which details not to hand over at signup — a starting point for beginners. Below is the full walkthrough: signup, link storage, client import and verification.

The trouble beginners hit with a VPN is rarely a misinstalled client. It usually comes from two places: handing over information at signup that was never needed, and treating the subscription link like any ordinary URL that can be forwarded. Both share one trait — nothing warns you when it goes wrong. By the time connections break or the dashboard refuses your login, it is usually late. The same holds for risks on public Wi-Fi: no popup will ever announce them.

How to create an account: username and password are enough

Signup is where services most often ask for more than they need. Typical forms want an email, a display name, a birthday, even a backup contact 'for recovery'. ZaraVPN asks only for a username and a password — no email address required. That is one less entry point for credential stuffing and phishing, and one less piece of personal data to look after long term.

The trade-off is that the password itself becomes your only credential, so set it to that standard:

Payment follows the prompts on the page — Alipay, WeChat Pay and USDT are all available, and there is no need to send order details or payment screenshots to anyone in a chat app.

What a subscription link really is

A subscription link is a URL. The client requests it and the server returns a configuration list: node addresses, ports, encryption methods, UUIDs or passwords, and transport parameters. The client reads that list as individual nodes, then uses routing rules to decide which traffic goes through the international routes and which connects directly.

Common protocols include Shadowsocks, VMess, VLESS, Trojan, Hysteria2 and TUIC. They all solve the same problem — encrypting traffic and delivering it to a route entry point — and differ in transport: Shadowsocks and VMess are mostly TCP, Trojan borrows standard TLS ports, VLESS is lighter and usually paired with TLS, while Hysteria2 and TUIC run over QUIC and UDP for faster handshakes on poor networks. The protocol itself does not determine how secure you are; whether credentials have leaked does.

The difference from a single-node link is worth spelling out: a long string like ss:// or vmess:// holds one node, whereas a subscription link is a whole list that the client refreshes on a schedule. So once a subscription link leaks, what you have given away is not one node but the entire list — and it stays valid until you reset it.

That is the key point: the credentials inside the link are directly usable, not a read-only description. Anyone who has the link can import it into their own client and spend your quota on your routes. It is more sensitive than a password — a password still needs a matching username, while a subscription link works on its own.

The short version Treat a subscription link like a password: not in group chats, not in screenshots, not in public repositories — only in the client's import field.

Checklist: storing your subscription link

The checklist below is meant to be followed directly. ✅ is what to do, ❌ is the trap beginners fall into most.

If the link has already leaked, the order is: reset the subscription in the dashboard first so the old link dies immediately, then import the new one. Don't keep using the old link, and don't assume nobody will bother to use it.

Public Wi-Fi risk checklist

Public Wi-Fi is not off-limits. The real question is whether what you plan to do on that network is worth the risks below.

Common risks in cafés, airports and hotels, and what to do about them
Risk How it works What you can do
Look-alike hotspot An attacker runs a hotspot with the same name as the venue, and traffic passes through it first Confirm the exact hotspot name with staff; turn off the system's 'auto-join open networks'
Unencrypted traffic intercepted HTTP pages and some app APIs are unencrypted and readable on the same network segment Check that the address bar shows HTTPS; stop immediately if a certificate warning appears
DNS hijacking or poisoning The DNS server handed out by the hotspot can return forged resolution results Send DNS resolution through the encrypted tunnel, then run a DNS leak test after connecting
Captive portal phishing page A 'sign in again' page pops up and asks for your email or payment account Enter only the Wi-Fi's own verification details on a portal page, nothing else
LAN sniffing and session hijacking Broadcasts and unencrypted cookies can be captured on the same network segment Turn off file sharing and AirDrop; switch to mobile data for sensitive tasks
Device auto-reconnects to an old hotspot A remembered open hotspot name can be impersonated Delete open network records you no longer use in system settings

Compress that table into one piece of advice: for research, video and reading documents, public Wi-Fi is fine; for online banking, a company admin panel or changing your primary email password, either switch to mobile data or connect to an encrypted route first. ZaraVPN carries traffic with quantum encryption, so once you are connected, at least the transport leg will not cross a stranger's router in plain text.

One more thing that gets overlooked: an encrypted route protects the transport, not what you type into a phishing page. However convincing the portal page looks, if you enter your account and password there, the route cannot save you.

Import into a client and verify it works

Once you have the link, run through the seven steps below; they cover the most common beginner cases of 'connected but not working'.

  1. Get the client. Windows, macOS, iOS, Android and Linux each have their own client — log into the dashboard and download the installer for your system from the download area. On iOS, App Store region restrictions apply, so pick an available client as the page instructs.
  2. Copy the subscription link. When copying from the dashboard, avoid picking up extra spaces or line breaks — paste it into a local text editor first and check that both ends are complete.
  3. Import. In the client, choose 'import subscription from link', paste, then update manually once and confirm the node list appears with a sensible number of entries.
  4. Pick routes and mode. Choose a route by purpose: AI tools, work meetings, international sites and 4K streaming each need something different. For mode, start with rule-based routing and set local sites to connect directly.
  5. Verify the exit IP. Open an IP check page and see whether the exit IP and its region have changed.
  6. Verify DNS. Run a DNS leak test and confirm resolution requests are not landing on the DNS servers provided by your local ISP or the hotspot.
  7. Verify routing. Open a local site and an international site at the same time: the first should connect directly, the second should go through the route. If both go through the route, the routing rules are not taking effect.

Browsers have one more exit that is easy to miss: WebRTC. Some browsers open connections directly and expose the local address, bypassing the proxy — turn WebRTC off in browsers that support the option, or check a test page to confirm it does not echo your local IP.

Common questions and final checks

Subscription link import fails — what to check first

First confirm the link is complete — automatic line wrapping in chat apps is the most common cause. Then check the client core version: QUIC-based protocols such as hysteria2:// and tuic:// need a newer core, and older clients simply report 'unsupported protocol'. Finally, confirm the system clock is accurate, since TLS handshakes are sensitive to time drift.

Connected, but pages won't load

Work through it in this order: is DNS leaking or failing to resolve → are the routing rules sending the target domain direct → is the route itself working (try another one). If all three are fine and pages still won't load, read the specific error in the client log instead of reinstalling over and over.

Already connected on public Wi-Fi — what else to watch

Still don't type any account or password into a suspicious portal page, and don't dismiss certificate warnings. The route protects the transport leg, but it cannot tell whether the page itself is a phishing site.

Can one account be shared by several people

There is no device limit, so several devices online at once is fine; but sharing in practice means sharing the subscription link, which means sharing credentials. If one person leaks it, everyone on that link has to reset, so separate accounts are actually less hassle.

What if it doesn't suit me after a few days

This service offers a 30-day no-questions-asked refund — submit it in the dashboard following the prompts. The monthly plan starts at ¥9.9 and includes 60GB, so spending one month checking whether the routes and clients suit you before moving to a longer term is safer than committing to a long period up front.

100+

Countries and regions covered

170+

International routes on sale

30 days

No-questions-asked refund

Unlimited

Simultaneous devices online

The closing check Username and password only for the account, a subscription link treated like a password, and an encrypted route before logging in on public Wi-Fi — get these three right and most beginner problems — can't log in, quota drained, connected but useless — simply won't happen.
Start Free Trial