When you first use a VPN, it is easy to confuse the account, subscription, nodes, and connection. The account manages plan and subscription details; the subscription link supplies nodes and configuration to the client; a node is a selectable route entry point; and the client’s connection state and routing rules determine where traffic actually goes. Keeping these layers separate resolves many problems without repeated reinstalls.
What unlimited devices means
LeeVPN plans support unlimited simultaneously connected devices, so one account can be used on Windows, macOS, iOS, Android, and Linux. A “device” here means an endpoint running the client and establishing a connection, not the subscription link itself. After importing the same subscription on multiple devices, each device still selects nodes, stores routing settings, and generates traffic independently.
Unlimited devices does not mean every device must use the same client or protocol. Desktop systems usually offer fuller system-proxy, virtual-network-adapter, startup, and rule-management options. Mobile systems depend more on system VPN permissions and are affected by battery-saving policies in the background. On Linux, the client may run through a graphical interface, command line, or system service. As long as the subscription format is compatible with the client, choose the implementation that fits each platform.
Managing subscriptions across devices
- Treat the subscription link like an account credential. Do not post it on public pages, in chat groups, or in screenshots.
- After importing it, update the subscription first, then check that node names and protocols appear correctly.
- Clients may handle rule groups, node ordering, and automatic selection differently. Do not assume settings sync across devices.
- After changing subscriptions, obtain a valid link again from the service panel instead of continuing to share an old configuration.
- Delete the subscription and local configuration after using a shared device, so the next user cannot read the connection details.
If one device connects while another does not, do not assume the device limit is the cause. Compare the client version, system permissions, subscription update time, selected protocol, and current network environment. On mobile systems especially, a client may be suspended in the background: the interface can still show the previously selected node even though the underlying tunnel has disconnected. Restart the connection in that case.
When data resets and how usage is measured
LeeVPN monthly subscription data resets each month on the activation date rather than on a shared calendar-month schedule. Check the plan cycle shown in the account panel instead of estimating from the end of the month. Data packages do not expire, making them useful when usage varies and you prefer to plan around actual consumption. Since the two products are calculated differently, confirm whether the account is using a monthly subscription or a data package.
Data usage generally counts data transmitted through the proxy or tunnel. Web images, video caches, app updates, cloud-drive sync, and background system tasks can all consume data. The client’s local statistics are useful for spotting trends, but they may reset after reinstalling, clearing data, or changing devices. The plan record in the account panel is therefore better for checking remaining data.
| Usage mode | Data behavior | What to check |
|---|---|---|
| Global proxy | Most system and app traffic passes through the selected route | Check whether app updates, sync tasks, and local services are also being proxied |
| Rule-based routing | Only requests matching proxy rules pass through the route | Confirm that the target domain, app, and DNS queries match the intended rules |
| On-demand connection | A connection is established only when a specific service needs to be accessed | Check the connection status after finishing to avoid misreading background usage |
If data is being consumed faster than expected, temporarily disable cloud sync, automatic app-store updates, and video autoplay, then watch how the account record changes. If the client supports connection logs, check whether an overlooked app is continuously making requests. Logs can reveal domains and local network details, so do not publish them in full.
Data usage and network speed are different metrics. Data measures how much was transferred; speed measures how much can be transferred per unit of time. A faster route does not automatically increase total usage, but high-definition video, fast downloads, and background sync may finish more easily because they spend less time waiting, resulting in more data being transferred in practice.
How to judge VPN route speed
You cannot judge route speed from a node name alone, nor draw a conclusion from a single browser speed test. The real experience depends on the local access network, distance to the entry point, international exit, route type, protocol overhead, target-service location, and congestion at the time. For a repeatable comparison, keep the device, local network, and target service the same and change only one variable.
Direct, transit, and IEPL routes compared
A direct route usually means the client reaches an overseas node through the public internet. The path is simple, but quality depends more heavily on the local carrier and cross-border public routing. A transit route first connects to a nearby entry point, then the service forwards traffic to an exit node, reducing the impact of unstable public-internet paths. IEPL generally refers to an international Ethernet private-line connection. Its route organization differs from ordinary public-internet access, but the final experience still depends on the local entry point, exit load, and target-service network.
Start by choosing a nearby entry point based on geography, then compare the route type and the region where the target site is hosted. For a Japanese service, the most prominent node name is not necessarily the best choice. Check connection stability, continuous page-resource loading, video buffering, and whether long-lived connections drop. Low latency suits interactive tasks; high bandwidth suits downloads and video. They are not interchangeable.
| Route type | Path characteristics | How to evaluate it |
|---|---|---|
| Direct | Connects directly to the exit through the public internet | Compare route quality from the local carrier to the exit region |
| Transit | Reaches an entry point first, then forwards traffic to the target exit | Observe peak-time stability and sustained-transfer performance |
| IEPL private line | Uses a private-line structure for cross-border transmission | Evaluate it together with entry quality, target region, and real-world applications |
How protocols affect connections
Shadowsocks is a widely used encrypted proxy protocol with relatively simple configuration. VMess is part of the V2Ray ecosystem, and client compatibility depends on the specific core. Trojan commonly uses TLS for transport. VLESS does not provide complete encryption by itself and needs to be paired with TLS or another secure transport. Hysteria2 and TUIC use QUIC and UDP, so they may perform differently from traditional TCP transport on lossy or unstable networks, provided the current network allows reliable UDP communication.
A newer protocol is not automatically faster. If an Hysteria2 or TUIC route cannot connect while other protocols on the same node work, check whether the network restricts UDP, whether the client core supports the protocol, and whether the system clock is accurate. If Trojan or VLESS fails during the handshake, verify that the subscription is current and that certificate-related details were delivered correctly. Do not guess server parameters manually.
Do you need to keep the VPN connected?
Whether to stay connected depends on the use case and routing setup. Keep the connection active when you need continuous access to international websites, notifications from cross-border services, or a persistent remote session. For specific tasks, turn it on only when needed. The key issue is not connection duration, but knowing which traffic uses the route and how apps behave after a disconnect.
Global mode sends more app traffic through the VPN and is simple to manage, but it may affect services intended only for local networks. Rule-based routing chooses direct or proxied access by domain, address range, or app rule, making it better for using local and international services together. If the rule set is outdated, a target domain may be incorrectly sent direct; if it is too broad, local apps may take an overseas route. When routing behaves unexpectedly, check rule matches first instead of repeatedly switching nodes.
Kill switch and automatic connection
Some clients offer disconnect protection, commonly called a kill switch. When enabled, the client blocks eligible traffic from falling back to the regular network if the tunnel drops unexpectedly. This suits tasks that cannot tolerate automatic fallback, but it can also temporarily prevent internet access if the client exits abnormally. In that situation, disable disconnect protection normally or exit virtual-network-adapter mode, then check the system network instead of deleting all network settings.
Automatic connection re-establishes the tunnel after startup, wake, or a network change. Desktop clients can usually pair it with launch-at-startup settings; mobile clients depend on the system’s on-demand connection support and background scheduling. When a device switches from Wi-Fi to another network, the existing connection may need a new handshake. A brief interruption then reflects a path change, not an invalid subscription.
How to import a subscription into a client
A subscription link is not a single node address; it is the entry point a client uses to retrieve a set of configurations. Usually, copy the subscription from the account panel, then choose “Import from link” or “Add subscription” in the client. After importing, update it, confirm that the node list appears, and test a connection with one node. If the client supports only individual configuration files, use an export format compatible with that client.
- Get the currently valid subscription link from the account panel. Avoid links forwarded by others or stored in public locations.
- Add the subscription in the client and give it a recognizable name.
- Update the subscription and check that the expected regions, routes, and protocols appear.
- Connect through a nearby node, then visit a network-check page to verify the exit result.
- After enabling split tunneling, check separately that services requiring proxy access and direct access follow the intended rules.
If a subscription update fails, first confirm that the browser can open the service panel, that the plan is valid, and that the client has not incorrectly sent the update request through a proxy that is not connected yet. Some clients support updating subscriptions through a proxy, while others update directly by default. The right option depends on the current network. If the update succeeds but the nodes do not change, check whether the client cached the old subscription or imported the new content into another configuration group.
How to check DNS leaks and routing rules
DNS converts domain names into network addresses. A DNS leak usually means that business traffic has entered the VPN or proxy while domain lookups are still sent to the resolver specified by the local network. This can produce results that do not match the exit region or prevent routing rules from working as expected. It does not always make a site completely inaccessible; more often, some resources fail to load, the same service opens in different regions, or the main page works while images and APIs fail.
Check the exit address and DNS resolution results together. If the client offers remote DNS, proxy DNS, or rule-based DNS, follow its documentation and choose the option that matches the current mode. With system proxy mode alone, not every app automatically sends DNS queries through the proxy. Virtual-network-adapter mode can take over more system traffic, but it is also more likely to conflict with firewalls, container networks, or enterprise network policies.
Routing rules usually match domains, address ranges, apps, or fallback rules. When rules have an order, place specific rules before broad ones. If a target service uses multiple domains, proxying only the main domain may not be enough; static assets, login APIs, and media domains must be handled consistently. If a site works in a browser but not in its app, check whether the app bypasses the system proxy or uses its own network stack.
What order should you follow when a connection fails?
The most effective troubleshooting principle is to change only one thing at a time. Confirm that the local network works, then check the plan, subscription, client, protocol, and node. Reinstalling the client immediately can erase logs and rules, leaving less evidence to work with. The sequence below covers common cases such as connection failures, no internet after connecting, and only some services being inaccessible.
- Disconnect the VPN and confirm that the current network can access local websites and the service panel normally.
- Check the plan status and remaining data in the account panel, then copy the subscription link again.
- Update the subscription and verify that nodes and protocols are complete instead of continuing to use an expired cache.
- Leave all other settings unchanged and switch only to another route in the same region for comparison.
- If a specific protocol fails, use one the client explicitly supports, and check UDP availability and the system clock.
- If the connection succeeds but access does not work, check whether the system proxy, virtual network adapter, DNS, and routing rules conflict.
- If the cause is still unclear, save the error time, node name, protocol, client version, and redacted logs, then describe the symptoms in a support ticket.
An error message is more useful for diagnosis than “it won’t connect.” A handshake timeout usually points to a path, protocol, or server-connection issue. An authentication failure is better investigated by checking whether the subscription and configuration are valid. If the connection succeeds but no traffic passes, focus on routing, DNS, the system proxy, and disconnect protection. Before submitting logs, remove subscription links, access tokens, and other account credentials.
How should beginners choose a configuration?
For a stable starting setup, use an officially supported client, automatic subscription updates, nearby routes, and rule-based routing. There is no need to adjust every advanced parameter at once. On desktop devices, understand the difference between a system proxy and a virtual network adapter. On mobile devices, allow the system VPN permission and check background policies. On Linux, identify whether the current setup is a system-level tunnel or an application proxy.
LeeVPN covers 90+ countries and 200+ routes. With more choices available, narrow them down by entry-point distance, route type, and target service instead of switching randomly. An account can be created without an email address, plans support unlimited simultaneously connected devices, and a 7-day no-questions-asked refund is available. In practice, keeping clear test conditions and troubleshooting notes is more reliable than relying on a supposedly universal node.