Here’s the basic relationship to know: a subscription provides configuration, a node determines the connection’s entry and exit points, a protocol defines how data is transmitted, and routing rules decide which path each request takes. These operate at different layers, so changing the wrong setting often won’t fix the problem. This guide explains them in the order you’ll encounter them in a VPN client.
Subscriptions and profiles: what you pay for vs. the link you import
“Subscription” can mean two different things. On a billing page, it refers to service benefits provided for a set period. In a VPN client, it usually means a remote source for nodes and related configuration. Activating a plan doesn’t automatically load its configuration into your client, and a successful import doesn’t mean your account benefits are still active.
A subscription link usually contains access credentials. When a client reads it, it retrieves configuration from the service. That configuration may include a list of nodes, policy groups and routing rules, depending on the server’s format and the client’s capabilities. It isn’t an ordinary information-page URL, and it may not work if pasted into your operating system’s VPN settings.
“Update subscription” means fetching the remote configuration again. It doesn’t renew your plan or automatically add traffic. Node names, groups or connection settings may change after an update. Whether your manual edits are kept depends on how the client merges configurations. If a connection stops working, update the subscription first, then check which profile is active.
Nodes, regions and route types: what each one tells you
A node is a connection profile you can select in your client. It typically includes a server address, port, protocol and authentication settings. A region label such as “Japan” usually indicates the exit location, but the node name alone can’t verify where traffic exits—or guarantee that a particular platform will accept that exit.
The entry point is where your device connects to the service network. The exit point is where a request leaves that network on its way to a website. They may be different. The region shown in a node list, the region a website detects and the region associated with your account may not match. Websites may also consider account details and past activity.
| Route type | Typical route | What to consider | What you can’t assume |
|---|---|---|---|
| IEPL dedicated line | A segment of the route uses an international Ethernet private line | The overall performance of your local connection, the dedicated segment and the exit | That the entire route is exclusive or congestion-free at all times |
| Relay | Traffic first reaches an intermediate server, then gets forwarded to the exit | Connectivity to the entry point and the quality of onward forwarding | That a relay always uses a dedicated line or is always faster than a direct connection |
| Direct | Usually bypasses a separate relay entry operated by the provider | The actual route from your local carrier to the remote server | That there are no carrier routers along the way or that latency will always be lower |
These terms describe routes, not protocols or standardized performance tiers. The same route type can perform differently on different access networks. For a fair comparison, keep the device, local network and target app the same, then switch routes. Changing everything at once makes it hard to tell what caused the difference.
Protocols and clients: compatibility matters more than the name
A protocol defines how a client and server establish a connection, verify identity and transmit data. The client reads the configuration, runs the protocol implementation and routes device traffic through the appropriate connection. Support for a protocol doesn’t guarantee compatibility with every provider’s subscription format or every protocol extension.
Common VPN protocol names, explained
- Shadowsocks: An encrypted proxy protocol. Both ends need to use matching encryption methods and credentials. It isn’t a built-in VPN protocol in your operating system.
- VMess: A proxy protocol whose configuration includes identity credentials and transport options. The client and server settings need to match.
- Trojan: Typically uses TLS to protect traffic. Certificate validation, the server name and the connection address must be configured correctly.
- VLESS: The protocol itself doesn’t encrypt transmitted content. Assess security in the context of the transport protection in use; the name alone doesn’t tell you enough.
- Hysteria2 and TUIC: QUIC-based proxy protocols that depend on UDP network conditions. If your network restricts UDP, connections may be affected. Using QUIC doesn’t mean it will be faster in every situation.
These are industry terms, not a statement that V8VPN supports every protocol. Check the dashboard, client download page and configuration for the options available to you. Names such as TLS and QUIC describe technical mechanisms; they don’t, by themselves, tell you about a service’s privacy policy.
If you’re new to VPNs, start with the compatible configuration provided by the service. If you see an error such as “unsupported format” or “missing field,” check the client type, version and import method first. Don’t randomly change encryption methods or disable certificate validation. Manual changes can turn a format issue into a connection problem and obscure the original cause.
Split tunneling, rule-based routing and global mode
Split tunneling routes different requests along different paths. Rules may match by domain, destination address or app process, though not every client supports every condition. A match may send traffic directly, through a proxy, to a policy group or block it.
Rule-based mode follows a set of rules. It’s useful for handling apps that need international routes separately from local traffic. Rule order often matters: an earlier match may determine where traffic goes, while a final catch-all rule handles anything unmatched. Updating routing rules may be a separate action from updating node subscriptions.
Global mode usually sends requests handled by the client’s proxy through the selected exit. That doesn’t mean it takes over all traffic on the device. Apps that ignore the system proxy and traffic excluded from the tunnel may still use other routes.
System proxy tells the operating system or apps which proxy address to use; apps must support it. TUN mode captures selected traffic through a virtual network interface. It works differently and remains subject to routing, permissions and exclusion rules. Clients may also implement modes with the same name differently.
DNS, exit IPs and connection checks
DNS translates domain names into network addresses. Your connection’s exit determines where a website sees a request as coming from, while DNS settings determine which resolver handles domain lookups. If a webpage opens, that only confirms one access path works; it doesn’t prove that every app or DNS lookup uses the same route.
A DNS leak generally means that queries expected to follow a particular protected route are instead sent to an unintended resolver. Direct resolution of local domains isn’t necessarily a leak; assess it against your configuration’s intended behavior. Your browser’s encrypted DNS, system DNS and client DNS may all be active, so check whether any bypass the expected route.
Use the network check to verify your browser’s current exit IP, then test the specific app. A successful browser check doesn’t replace testing other apps. If the exit IP has changed but a website still reports the wrong region, also check your account region, session cache and the platform’s own access requirements.
- ✅ Check the active profile, selected node and operating mode. Updating a profile doesn’t mean the client has stopped using an older group.
- ✅ Compare the browser with the target app to tell whether the app is bypassing the proxy or the entire route is unreachable.
- ✅ Check whether the domain matches the expected rule, then review the DNS route.
- ✅ Keep other conditions unchanged while switching nodes, and note what happens rather than just writing “doesn’t work.”
- ❌ Don’t treat a single webpage test as proof that all traffic from your device is covered.
From import to connection: a step-by-step checklist
Interfaces vary across platforms. Windows and macOS clients may offer system proxy and virtual interface options. iOS and Android commonly use system VPN permission to route selected traffic. Linux may require additional setup for the system proxy, routing or service permissions. A VPN indicator on your device means the relevant configuration is active; it doesn’t guarantee that a particular website is reachable.
- Check your service benefits. Confirm that your plan is active and that traffic remains available. Seeing nodes in the client doesn’t mean your account status has been verified.
- Get a compatible client. V8VPN supports Windows, macOS, iOS, Android and Linux. For other platforms, sign in to access the client. The iOS download option requires an active plan; sign in to get your subscription.
- Import using the right option. Use the client’s subscription import feature, then confirm that the profile name and node list appear. Don’t paste the subscription link into a field meant for a single server address.
- Grant system permissions. Allow the required network configuration when prompted, then select a node and mode. Avoid running multiple tools that take over network traffic at the same time, as their routing and DNS settings may conflict.
- Test real-world access. Check your exit IP and the target app. If something goes wrong, check your account, subscription, node, routing rules and DNS in order, changing one setting at a time.
When asking for help, include your operating system, client name, error message and the checks you’ve already tried. That’s more useful than simply saying “connection failed.” Hide credentials in configuration screenshots. You can also find the relevant instructions in the Help Center, then submit the details through a support ticket after signing in.
How billed data and resets work
The subscription expiry date, remaining traffic and node status shown in the client each refer to different things. Monthly subscriptions include traffic for each billing period. V8VPN resets traffic monthly on your activation date, not at the start of each calendar month. If you upgrade partway through a period, the price difference is converted into remaining days; check the dashboard for the exact calculation.
A traffic package lets you use its available data until it runs out and never expires. It’s a different billing option from a monthly subscription, and it doesn’t guarantee a fixed exit IP or uninterrupted access to any particular platform. There’s no limit on the number of devices connected at the same time; this is a device-use policy, not unlimited data. Check prices and data allowances on the plans page.