This VPN glossary for beginners starts with the options you’ll commonly see in a client: a subscription provides the configuration, a node determines which exit your traffic can use, a protocol defines how the client communicates with the server, and routing determines which requests go through the proxy. Knowing these terms helps you tell the difference between a configuration that hasn’t been imported, a node you can’t connect to, and a site that alone won’t load.
Subscription links: What gets imported and updated
On a plan page, “subscription” usually means a billing arrangement. In a client, it usually means a remotely hosted configuration that can be updated. A subscription link is the address the client uses to fetch that configuration. It typically contains node addresses, ports, and connection settings, and may also include proxy groups or routing rules. Selecting “Update subscription” fetches the configuration again; it doesn’t renew your plan or establish a connection.
- Copy the subscription link that matches your client from the service dashboard. Start with the import instructions in the Guides. Being able to open a link doesn’t mean every client can read the format it returns.
- In your client, look for an option such as “Import from URL,” “Subscription,” or similar, then add the link and refresh. If you see a node list, the configuration has been read—but that doesn’t confirm the nodes are reachable.
- Enable the imported configuration, choose a node or proxy group, then turn on the proxy or system tunnel. Test it with the app you actually want to use; don’t rely only on the client’s “Connected” status.
If an update fails but your existing nodes still work, first check whether the subscription URL has expired, whether the format matches your client, and whether your current network can reach the URL. The client may still be using its last saved configuration. Keeping that configuration is more useful for troubleshooting than deleting everything at the first error.
Nodes and routes: direct, relay, and IEPL
A node is a connection configuration you can select in your client; a route is the path traffic takes to reach its exit. The entry point accepts the client connection, and the exit sends requests to the destination site. Two nodes labeled with the same location may still use different entry points or network paths. A location label also doesn’t guarantee that a destination site will identify the exit as being in that location.
| Name | How traffic travels | What to check when choosing |
|---|---|---|
| Direct node | The client connects straight to the node’s server address without first passing through a separate relay entry point provided by the service. | Whether the route from your current network to the node is stable. “Direct” here still uses a proxy. |
| Relay route | The client connects to an entry point first, then the service forwards traffic to an exit. The forwarding leg may use the public internet or a dedicated route. | Whether the entry point is easy to reach and the forwarding leg gets congested during the times you usually connect. |
| IEPL dedicated route | IEPL stands for International Ethernet Private Line. In route descriptions, it usually refers to one leg of cross-border transmission, not the entire path from you to a website. | Check which part of the route the dedicated line covers, then test how your apps perform. The route name alone doesn’t tell you whether its exit is suitable for a particular site. |
DIRECT in a rule log means something different: that request didn’t go through a proxy node. To compare two routes, keep the device, network, and destination app the same, switch only between nodes in the same location, and observe page loads, video buffering, or dropped long-lived connections. The latency shown next to a node depends on how the client probes it; that number alone can’t tell you how quickly a site will load.
Protocols: Client and server settings must match
A protocol defines how a client and server establish a connection, authenticate, and transfer data. Shadowsocks is an encrypted proxy protocol. VMess and VLESS are different proxy protocols, and their configurations aren’t interchangeable. VLESS doesn’t provide encryption on its own; whether a connection is encrypted depends on the accompanying transport security settings. Trojan typically uses TLS. Hysteria2 and TUIC are both based on QUIC and rely on UDP, but they aren’t compatible with each other.
If a node is labeled TLS, WebSocket, or QUIC, distinguish the protocol from the transport method and security settings. A client recognizing a protocol name doesn’t mean it supports the transport method or security parameters in the subscription. If import reports “unsupported” or skips some nodes, check the client’s and its core’s compatibility documentation. Don’t manually change a node to a different protocol.
If a node that relies on UDP works at home but keeps timing out on another network, while a TCP-based node connects, a restricted UDP path is one possible cause to investigate. This is only a clue; it doesn’t rule out a server problem or a configuration error. First try an existing compatible node. Avoid changing the client, subscription, and node all at once, or you won’t know which change made a difference.
Routing: Choosing between global and rule mode
Once a client handles your traffic, routing determines which exit each request uses. Rule mode can send requests to a proxy group, allow them to connect directly, or block them based on conditions such as domain or destination IP; the available conditions depend on the client. Many clients apply the first matching rule, then send unmatched traffic to a fallback rule. Check both the matching rule and the exit it selects.
Global mode typically sends traffic handled by the client through a single global policy instead of choosing a route for each request. It doesn’t necessarily cover the whole device: with system proxy enabled, apps that ignore system proxy settings may bypass the client; a system tunnel may also have app exclusions or routing exceptions. If the same subscription behaves differently on desktop and mobile, check how each client handles traffic and what permissions it has before suspecting the node.
Use rule mode day to day, and compare it briefly with global mode when troubleshooting. If a site opens with the same node in global mode but not rule mode, check whether rule mode sends the main site, login domain, or static assets through different exits. When switching modes, confirm which node the global policy actually selects so you don’t mistake a node change for a routing-rule issue.
DNS: What else should you check?
DNS translates domain names into addresses. A website connection going through a proxy doesn’t mean its DNS queries do too. If queries are supposed to be handled on the proxy side but are still sent to your local network’s resolver, that’s a DNS leak to investigate for that configuration. In rule mode, using local DNS for domains expected to connect directly isn’t necessarily a problem. A DNS test shows which resolver answered; an exit IP check shows the outgoing IP. They answer different questions and aren’t interchangeable.
If the difference occurs in just one browser, check whether it has its own secure DNS enabled and compare that with the client’s DNS handling settings. Keep the device, network, and app the same while troubleshooting. First confirm that traffic enters the client, then check DNS resolution, route selection, and the actual exit.
- ✅ Empty node list: First check whether the subscription refreshed successfully and whether the client supports the import format.
- ✅ Nodes are listed, but connections time out: On the same network, try another compatible node to see whether the issue affects one node or all of them.
- ✅ Only some sites or login pages won’t load: Check the destination domain, matching rule, and exit in the connection log, then review your DNS settings.
- ❌ Don’t assume an app is working just because the client says “Connected” or shows low latency. Check whether the request actually succeeds.
Still stuck? Check the setup instructions for your platform in the Help Center. When asking for help, include the client name, network, selected mode, and the step where the error occurs. Before sharing logs, redact subscription links, access credentials, and any domains you don’t want to disclose.