VPNbasics: subscriptions, nodes, protocols, and routing explained
A clear guide to subscriptions, nodes, IEPL dedicated lines and relays, common protocols, and global and rule-based modes—so you can understand how they relate and make sense of your client.
New to VPNs? Start with these basics: A subscription provides configuration details, nodes are connection options, protocols define how the client communicates with a node, and routing determines which requests go through it. A successful import, a reachable node, and a page that loads are three different things to check.
What is a subscription link, and what happens after you import it?
On a pricing page, “subscription” refers to billing. In a client, it usually means an updatable source of configuration. The link may return nodes alone or a full configuration with nodes, proxy groups, routing rules, and DNS settings. A subscription isn't a single route, and pasting its link won't connect you automatically.
- Copy the subscription link from your service dashboard. If the dashboard offers multiple formats, choose one based on your client and its configuration guide. Don't rely on the file extension alone.
- Open the client's Configuration or Subscription page, choose import from URL, and update it. If the update fails, check whether the error occurred during download or parsing: for a download issue, make sure the URL is accessible; for a parsing issue, check that the format is supported.
- Enable the imported configuration, then select a connection option under Nodes or Proxy Groups. If local changes disappear after updating the subscription, check whether they were made in a configuration that gets overwritten during updates.
How to read nodes, exit locations, and IEPL dedicated lines
A node is a selectable connection profile in a client, with settings such as the server address and protocol. The entry point is the server your client connects to; the exit is where a request leaves the proxy network to reach its destination. A location shown in the list may identify the exit or simply be an operator's label. To check which address a website sees, compare the IP lookup results before and after connecting in the same browser. This only shows the route taken by the lookup request; other apps may use different exits.
Whether traffic is relayed between the client and the exit node and which route is used for the cross-border segment are two separate questions. Direct connection usually means the client connects straight to the exit node—not that the internet route has no routers. With a relay, the client connects to an entry point, which forwards traffic to the exit. IEPL is an international Ethernet private line; the term describes the link being used. A relayed setup may use IEPL for one segment, but that doesn't mean the entire route from your home to the destination uses a dedicated line.
A client's latency figure may measure the response time of a test address. It's useful for an initial comparison, but it can't be converted directly into download speed. To choose a node, test the actual sites you use on your usual network and at your usual times. Compare the initial page load and continued use before switching.
How do common protocols differ?
Here, “protocol” mainly refers to how the proxy client communicates with the server, not the VPN settings built into your operating system. If the client says a configuration is unsupported, first check whether the client and its core version can read it. Then verify the node's transport and security settings. Matching protocol names alone won't guarantee a connection—the client settings must match the server configuration.
| Protocol | Key features | What to check |
|---|---|---|
| Shadowsocks | Encrypted proxy | Check that the encryption method and key match |
| VMess | Authenticated proxy protocol | Check that the identifiers and transport settings match |
| Trojan | Typically uses TLS | Check the password and certificate validation settings |
| VLESS | No built-in encryption | Check the transport and security layers against the configuration |
| Hysteria2 | Uses QUIC over UDP | Check whether the current network can reach the node's UDP port |
| TUIC | Uses QUIC over UDP | Check that the protocol version and authentication settings match |
A protocol name doesn't indicate the quality of a route. If a node connects but access slows at certain times, compare available nodes on the same network before changing protocol settings. For terminology, see the protocol reference.
Global mode or rule-based routing?
Global mode typically sends all traffic handled by the client through the selected proxy. Rule-based mode uses conditions such as domains or destination addresses to direct requests through different routes, such as direct, proxy, or blocked. “Direct” in a rule means a request reaches its destination without a proxy; a “direct node” in a route list still uses a proxy node.
If you need both local sites and international websites, start with rule-based mode. If a site only loads in global mode, keep the node and network unchanged, then check which rule matched the domain in the routing log. Login pages and images may use different domains, so a working homepage doesn't mean every request is routed correctly. If switching to global mode makes no difference, don't rewrite the rules right away—first check whether the request reached the client.
Which traffic a client handles depends on the operating system and client. On desktop, some apps may ignore system proxy settings. Clients that support virtual network adapter mode can handle more traffic, though exceptions may still apply. On iOS, the client often needs permission to add a VPN configuration. Even when the system says it's connected, not every request necessarily goes through the proxy.
Why won't webpages load after a successful connection?
- ✅ Confirm that the active configuration and selected node are in use. A successful configuration update only means the settings were downloaded; it doesn't confirm that the node can connect.
- ✅ Check the exit using the browser where the issue occurs, and verify that the destination domain matches the expected rule. If logs are available, check the lookup page and destination site separately.
- ✅ If you see a DNS resolution error, check the client's DNS rules and the browser's Secure DNS settings. Then see whether the system resolver is handling the lookup.
- ❌ Don't treat a visible proxy exit as proof that DNS is working as expected. Web requests and DNS lookups may take different routes.
A DNS leak usually means that lookups expected to follow a specific DNS route were sent to an unintended resolver by another route. A test showing a different resolver and exit IP doesn't automatically indicate a leak: rules may intentionally send some lookups locally or use a separate DNS service. Compare test results with the behavior expected from your current configuration instead of judging by the resolver's location alone.
During troubleshooting, keep the device, network, and destination site the same, and change only one setting at a time—node, mode, or DNS. This helps identify whether the configuration failed to import, the node is unreachable, requests aren't being routed as expected, or the domain isn't resolving.