V2Ray Glossary

Find the concept behind any client setting. Protocols define how two endpoints exchange data; cores handle connections and routing; clients provide an interface for configuring them. When troubleshooting a connection, first identify which layer a setting belongs to, then check the settings at that same layer.

Proxy protocols

A protocol defines how the two endpoints identify requests and exchange data. The correct protocol and authentication settings matter, even when the server address and port are right.

VMess

A proxy protocol in the V2Ray ecosystem that typically uses a UUID to identify users. Authentication depends on the system clock, so a significant time offset can prevent connections even when the address and user ID are correct. When troubleshooting, make sure the device clock is synchronized before checking connection settings.

VLESS

A proxy protocol supported by cores such as Xray that commonly uses a UUID as the user ID. VLESS identifies the protocol, but says nothing about the transport or security layer. When entering settings manually, check the transport, security options, and any flow control required by the server separately.

Trojan

A proxy protocol that typically uses password authentication over a TLS connection. The TLS handshake and password authentication are separate steps, so a correct password does not guarantee certificate verification will succeed. If the logs first report a certificate name mismatch, check the TLS settings.

Shadowsocks

A proxy protocol that requires both sides to use matching encryption methods and keys or passwords. Supported encryption methods can vary between clients and cores, so being able to import a configuration does not guarantee it will work. Enter the exact method name provided by the server rather than choosing a similar-looking option.

Cores & ecosystem

The client interface is not the protocol implementation. Switching cores in the same client can change which fields it recognizes and which features are available.

Project V

The open-source project that V2Ray originally belonged to, a name often used when discussing the project's history. It is neither a node protocol option nor the name of a graphical client's installer. When reading older documentation, check whether it refers to the project, the core, or a client that uses the core.

V2Fly

An open-source project continuing development of the V2Ray core. The core handles inbound connections, matches routing rules, and passes traffic to an outbound; the client provides the graphical interface. A client importing a configuration does not mean the current core supports every field in it.

Xray

A proxy core forked from the V2Ray ecosystem and used by v2rayNG. Even when two cores support a protocol with the same name, their fields, transport options, and default behavior may differ. Before migrating a configuration, check that the target core supports its security and transport combination.

Transport & encryption

The transport describes how data is carried; the security layer describes how the connection is verified and protected. Client settings usually configure these separately.

REALITY

A transport security mechanism supported by Xray that can be paired with VLESS, but is not a standalone proxy protocol. Enter the VLESS user ID correctly, then check the REALITY public key, server name, short ID, and other parameters separately. Correct settings in one layer cannot compensate for errors in another.

TLS

A security layer that encrypts connections and verifies identity. The address the client connects to may differ from the name used for certificate verification; for example, a domain name may still be required when connecting directly to an IP address. For certificate errors, check the name, device clock, and certificate chain separately.

WebSocket

A bidirectional transport that can carry proxy traffic. Its path and request hostname must match the server or intermediary forwarding layer. Even if the server port is reachable, an incorrect path may send the request to a regular web handler instead of the proxy endpoint.

Subscriptions & nodes

Subscriptions update configurations; nodes connect to servers. A successful subscription update only confirms that entries were fetched—it does not mean their nodes have passed a connection test.

Subscription

A way for clients to fetch and update multiple configuration entries from a single URL. A group alias is only a local label; changing it does not change the subscription source. Subscription URLs may grant access to configurations, so hide the full URL before sharing screenshots or logs.

See how to import a subscription →

Node

A connection profile in a client, usually containing a server address, port, protocol, and authentication parameters. Its display name is just a label and does not determine the server settings. Two nodes with the same name may point to different servers, while one server can offer nodes with different protocols.

Real connection latency

The time measured when accessing a test URL through a specified outbound. Timing methods vary by client. Unlike a direct probe of the server port, this measurement depends on the test target, handshake, and current network conditions. For a fair comparison, use the same test URL and conditions; milliseconds are not download speed.

Routing & traffic rules

Once traffic reaches the core, routing rules determine which outbound handles it. When troubleshooting a match, check whether the destination reaches the core as a domain or an IP address.

Routing rule

A rule that selects an outbound for a connection based on criteria such as domain, address, or port. In configurations that use the first matching rule, a broad rule placed too early can match traffic before later exceptions. Before making changes, note the expected match, then test and confirm which outbound is actually used.

Read the guide to routing and traffic rules →

GeoIP

An IP range dataset used for address matching, organized by region or other categories. Categories depend on the data source and update schedule; they are not real-time measurements of a user's location. If a rule only has a domain to work with, using IP categories also depends on whether the core resolves the domain during matching.

GeoSite

A categorized dataset for domain matching, allowing a rule to reference a group of domains. Coverage can vary between data packages, so the category name alone does not tell you what it includes. If you only have a destination IP and no usable domain information, a domain list cannot directly replace an IP rule.

Traffic routing

Sends connections that meet different criteria through different outbounds, such as direct, proxy, or reject. It determines where connections go after reaching the core, not which applications send traffic to the core. If an application never uses the proxy entry point, changing outbound rules will usually not affect it.

Client settings

First determine how application traffic enters the client, then check where DNS queries go. These paths may differ, and a successful application connection does not confirm that DNS followed the expected path.

TUN mode

Receives IP traffic routed in by the operating system through a virtual network interface, then passes it to the client for processing. It can cover applications that ignore system proxy settings, but the scope still depends on routing, exclusions, and permissions. After enabling it, verify that target applications and the local network still behave as expected.

System proxy

Provides a proxy address to applications that read the operating system's proxy settings. Applications using their own settings, environment variables, or direct connections may not be affected by the system proxy toggle. If a browser works but a terminal does not, first compare the proxy entry point used by each.

Local listening port

The port on which the client accepts proxy requests from the local device, distinct from the remote node's port. When configuring an application manually, match both its port and proxy type to the listening endpoint. If the client switches to another port because of a conflict, update any applications still pointing to the old one.

FakeDNS

A mechanism that returns synthetic addresses for domains and keeps a mapping. When an application connects to one of these addresses, the core can recover the domain from the mapping for subsequent matching and connection handling. A synthetic address is not the server's public IP and should not be used to test server reachability directly.

DNS leak

Domain lookups are taking an unexpected resolution path—for example, an application may use its own resolver instead of the configured DNS chain. Before diagnosing a leak, establish which resolver should receive the query, then observe the actual path. A website loading through the proxy only confirms the route taken by that connection; it does not prove that DNS queries followed the same path.