What restrictions apply when using multiple devices?
Device limits are often the first question beginners ask about VPNs. The key distinction is between how many devices can install the client and how many can connect at the same time. Some services allow unlimited installations but restrict concurrent connections; others apply rules by account, subscription, or route. YRVPN has no device limit, so you can use the same account configuration on your computer, tablet, and other personal devices without a separate plan for each one.
Having several devices does not mean each one constantly uses large amounts of data. An idle client typically generates only keep-alive traffic and background system requests. Video streaming, file syncing, system updates, cloud backups, and large downloads have the greatest impact on usage. When a home router handles the connection, traffic from every connected device is counted toward the same subscription.
Does data usage include uploads and downloads?
Usually, yes. Text, images, and scripts downloaded while browsing count as downstream usage, while submitted forms, uploaded attachments, cloud sync, and the return traffic from video calls count as upstream usage. The total shown by a client generally combines uploads and downloads rather than counting downloads alone. Proxy protocols also generate a small amount of handshake, encapsulation, and keep-alive traffic, so server totals and an app's own figures may not match exactly.
Background activity is the easiest usage to overlook. Operating-system updates, automatic photo backups, cloud sync, game updates, and browser preloading can transfer data even when no window is open. If usage rises quickly, check system network statistics to identify the responsible apps, then see whether the client is running in global mode. Web browsing alone rarely explains all consumption.
- ✅ Check system network usage first to find apps that are continuously uploading or downloading.
- ✅ Pause cloud sync, system updates, and automatic backups, then see whether usage stabilizes.
- ✅ Use split tunneling for sites that need international access, so local services do not take an unnecessary international route.
- ✅ After updating the subscription, verify the plan name and active status to rule out stale client data.
Monthly subscriptions and data packages also use different accounting methods. YRVPN monthly-subscription data resets each month on the activation date, while data packages do not expire. The former suits regular, ongoing access; the latter is better when usage varies. A reset affects the plan allowance but does not automatically clear historical statistics stored locally by the client, so the two figures may cover different periods.
Does slower speed always mean throttling?
Not necessarily. Speed depends on the local access network, Wi-Fi signal, carrier gateway, entry node, international route, destination website, and protocol. Only when different routes show a similar stable ceiling under the same device, network, destination, and roughly the same time should you investigate plan or server-side policies further. A single low speed test does not prove throttling.
Evening congestion often appears as higher latency, more packet loss, video buffering, or fluctuating download speeds. Wireless interference can make the local network the bottleneck first, while a destination site may limit a single connection. If only one website is slow and other sites work normally, the issue is more likely with the destination service or its upstream network.
- Disconnect the acceleration connection first and confirm that the local network can reliably reach commonly used services.
- After connecting, try direct, relay, and dedicated routes in the same region rather than testing only one route.
- Keep the test file, device location, and network connection method consistent before comparing results.
- If webpages work but video does not, check whether the platform region, exit IP, and DNS resolution are consistent.
Does cross-border access need to stay on all the time?
There is no need to treat “always on” as a universal rule. When visiting local sites, using a LAN printer, or connecting to a company intranet, you can disconnect the client or use rule mode to send local traffic directly. When you need international sites, overseas work files, or a service for a specific region, route only the relevant traffic through the proxy. This usually balances speed and stability better.
Global mode sends more requests through the selected node. It is useful for checking whether rules are missing and for briefly verifying the exit IP, but long-term use can send local sites on a longer route and consume unnecessary plan data. Rule mode matches domains, IP addresses, or apps to connection methods and is better for everyday use, provided the rule set stays current.
Mobile devices are also affected by system power-saving policies. After the system pauses the background client, the interface may still show the last connection state even though the tunnel has been rebuilt or interrupted. If the connection drops after the screen locks, check the client's background permissions first, then see whether it needs to reconnect.
What is a subscription link, and how should it be imported?
A subscription link is an address generated by the service. The client uses it to retrieve node names, server addresses, ports, protocols, and the connection parameters it needs. It is not a regular webpage and does not need to be opened in a browser. Copy the complete link, choose “Import from URL,” “Add subscription,” or a similarly named option in a compatible client, and then update it.
After a successful import, the client displays a node list. When the provider changes routes, you usually only need to update the subscription rather than edit server details one by one. If the list is empty, check in order whether the link was truncated, whether the client supports the subscription format, whether the current network can reach the subscription address, and whether the system date is correct.
- ✅ Copy the complete subscription link from the account panel; do not edit its characters manually.
- ✅ Import it through the client's subscription-management section rather than pasting it into a node-address field.
- ✅ Run an update after importing and confirm that the node names appear in the list.
- ✅ When changing devices, copy the link again from the panel to avoid losing characters while forwarding it.
- ✅ Treat the subscription link as an account credential. Do not publish it or include it in public screenshots.
A failed subscription update does not mean existing nodes stop working immediately. The client may retain the configuration from the last successful update but will not receive later route changes. First check whether an old node can still connect, then inspect the subscription address. If the panel generated a new link, replace the old saved address in the client as well.
How should you choose a proxy protocol?
Shadowsocks, VMess, Trojan, VLESS, Hysteria2, and TUIC can all carry proxy traffic, but they differ in design priorities, transport methods, and client compatibility. A protocol name alone does not indicate route quality. The same protocol can perform very differently across networks, servers, and clients. Beginners should start with a configuration provided by the service and explicitly supported by the client rather than judging speed by the name alone.
| Protocol | Key characteristics | What to check |
|---|---|---|
| Shadowsocks | Lightweight implementation with broad client support, commonly used for standard proxy connections | Encryption method and client compatibility |
| VMess | Mature configuration ecosystem that can combine different transport methods | Transport-layer parameters must match the server |
| VLESS | Relatively simple authentication and data-transport design, often combined with other transport layers | Client core version and transport configuration |
| Trojan | Usually based on TLS connections and dependent on certificate and domain configuration | System time, certificate validation, and domain resolution |
| Hysteria2 | A modern UDP-based transport designed with high-latency or unstable networks in mind | Whether the current network allows stable UDP communication |
| TUIC | Another modern UDP-based approach focused on concurrency and connection recovery | Client support and UDP network quality |
If a network provides unstable UDP support, Hysteria2 or TUIC may show handshake failures, intermittent drops, or an apparently successful connection that cannot transfer data. In that case, try another protocol offered by the service. Conversely, on high-latency networks with reliable UDP, they may be better suited to sustained transfers. Judge by actual connection performance rather than treating any protocol as universally best.
What is the difference between IEPL dedicated routes, relay routes, and direct connections?
A direct route connects the device to an overseas server through the local carrier network. The path is simple, but the international segment is more exposed to changes in public-internet routing. A relay route first connects to a nearby entry node, after which the provider selects the onward path to the exit. This can reduce detours in some regions. An IEPL dedicated route generally uses international Ethernet private-line resources for the cross-border segment, emphasizing path control; it does not mean every access stage is outside the public network.
Dedicated, relay, and direct routes describe network paths, not encryption protocols. An IEPL route can carry Shadowsocks, Trojan, or other protocols. Likewise, using a modern protocol does not automatically turn a direct path into a dedicated route. When choosing a route, keep “how traffic is transported” separate from “where it travels.”
| Route type | Path characteristics | How to evaluate it |
|---|---|---|
| Direct | The local network connects directly to an overseas exit | Observe route quality from the local carrier to the destination region |
| Relay | Traffic reaches an entry node first, then is forwarded to an overseas exit | Compare entry-node reachability and the stability of the onward path |
| IEPL dedicated route | The cross-border segment uses dedicated resources, making the path generally more controllable | Test it against your region, entry quality, and destination service |
A shorter geographic distance does not necessarily mean a better experience. Node location affects potential path length, but actual latency also depends on carrier interconnection, entry-node location, international routing, and the destination's data center. Filter by destination region first, then compare route types under the same protocol, changing one variable at a time.
How are DNS leaks related to split-tunneling rules?
Before accessing a domain, a device usually uses DNS to resolve it to an IP address. If webpage traffic goes through a proxy while DNS requests still use the local network, the resolution result may not match the exit region and the domains being queried may be exposed. A DNS leak is primarily a case where resolution requests take an unintended path, not simply a site that fails to load.
Split-tunneling rules determine which domains or IPs use the proxy and may also determine which DNS group is used. A reliable setup keeps DNS and traffic policies aligned: domains intended for the proxy should not first receive an unsuitable regional result from local DNS, while local services intended for direct access do not all need remote resolution. Clients may use different names for remote DNS, local DNS, proxy DNS, and system DNS, but the goal is the same: make the request path explicit.
- After connecting to a node, check the exit IP and confirm that its region matches the selected node.
- Test global mode and rule mode separately to see whether the issue occurs only with split tunneling.
- Clear the system and browser DNS caches, then revisit the destination domain.
- If both IPv4 and IPv6 are enabled, confirm that both types of traffic follow the intended routes.
- Close other tools that rewrite DNS or proxy settings to prevent overlapping configurations.
Browsers may also enable their own encrypted DNS settings, bypassing the resolution policy of the system or client. During troubleshooting, treat the browser, operating system, and proxy client as one complete chain. Changing only one part may not change the final request path.
What differs between clients on different platforms?
Windows and macOS clients can usually take over the system proxy and may also use a virtual network interface to handle traffic from more applications. With the former, check that system-proxy settings are restored correctly after an unexpected exit. The latter often requires network-extension permission, which should be granted when prompted during first use. If only the browser proxy is configured, other apps may not use the selected route.
Android and iOS generally use the system VPN interface to establish a local tunnel. A connection indicator in the status bar only shows that the interface is established; it does not necessarily mean the destination node can transfer data. Verify through the exit IP or an actual request. Power saving, background restrictions, and network changes can all trigger a reconnection.
A router setup lets devices on the home network use shared split-tunneling rules, which is useful for TVs, gaming devices, and other endpoints where installing a client is inconvenient. The trade-off is that configuration is centralized on the router, making it harder to identify an individual app's requests during troubleshooting. Encryption and forwarding also use router resources. If the router lacks sufficient performance, it is normal for a single-computer client to work well while the whole-home setup slows down.
How should you troubleshoot a connection failure step by step?
A useful troubleshooting sequence moves from local checks to remote ones, changing only one variable at a time. Confirm that the device has working internet access, then update the subscription, switch nodes, check system time and client permissions, and only afterward investigate protocol compatibility or network paths. If you change the client, protocol, node, and DNS simultaneously, you will not know the real cause even if the issue disappears.
- ✅ Disconnect the client and open a commonly used local website to confirm that the basic network works.
- ✅ Update the subscription and verify its active status so the node list is not stale.
- ✅ Choose another route in the same region to determine whether the problem affects only one node.
- ✅ Check the system date, time zone, and network permissions to avoid TLS validation or tunnel-creation failures.
- ✅ Temporarily switch to global mode to determine whether the issue comes from the route or split-tunneling rules.
- ✅ Check for duplicate proxy settings in the browser, operating system, and client.
- ✅ If a UDP protocol connects abnormally, compare it with another compatible protocol provided in the subscription.
- ✅ Record the error text, selected node, protocol, and network environment, then submit a support ticket.
Common errors can be understood by stage. If the subscription cannot update, the problem is usually in retrieving the configuration. If the node handshake fails, check protocol parameters, system time, domain resolution, and network compatibility. If the connection is established but webpages do not load, inspect routing, DNS, and system-proxy settings. If only one app fails, check whether it bypasses the system proxy or uses independent network settings.
When verifying a fix, do not rely only on the client button showing “Connected.” More reliable checks are that the exit IP matches the selected region, DNS resolution follows the intended path, the destination site loads continuously, and network settings recover after disconnecting. Only then can you confirm that the connection chain is working properly.