Configuration Reference / Glossary

V2Ray Glossary

Identify the layer each setting belongs to: which protocol connects, which core handles it, and how traffic reaches the client, resolves domains, and selects an outbound.

Protocols and Transports

Proxy protocols, transport methods, and transport security are separate settings. Recognizing a protocol name does not tell you what the other two are.

VMess

VMess is a proxy protocol in the V2Ray ecosystem. It authenticates users with an ID and provides protection at the protocol layer. A VMess node type identifies the proxy protocol used by both ends; check the underlying transport, port, and outer security settings separately.

VLESS

VLESS is a proxy protocol supported by Xray, and commonly uses a UUID to identify users. VLESS alone does not mean the connection uses TLS or REALITY. To check transport security, review the node's security settings and compare them with the server configuration.

Trojan

Trojan is a password-authenticated proxy protocol, commonly deployed with TLS to protect transport. When troubleshooting, distinguish authentication failures from TLS handshake failures: check the password for the former, and the server name, certificate, and connection port for the latter.

REALITY

REALITY is a transport security mechanism provided by Xray, often used with VLESS. It operates at a different layer from the proxy protocol. The server name, public key, and short ID in the client configuration must match the server settings. After importing a node, confirm that the active core recognizes these fields.

WebSocket

WebSocket can carry proxy traffic as the underlying transport. The connection is upgraded through an HTTP handshake before carrying proxy data. If the server specifies a path, the client's WebSocket path must match. Changing to this transport does not change the proxy protocol above it.

gRPC

gRPC carries proxy traffic over HTTP/2 streams. In cores that support this transport, the service name entered on the client must match the server. If the connection passes through a reverse proxy, that intermediary must also support this forwarding method.

Cores and Ecosystem

The client manages configuration; the core runs it. When checking compatibility, first identify which core is actually running the selected node.

Project V

Project V is the open-source project ecosystem in which V2Ray originated, with V2Ray as its core tool. Project V is often mentioned in accounts of the project's history. When choosing an installer, check the client name; when checking configuration fields, look at the core actually in use.

V2Fly

V2Fly is a community project that continues V2Ray development and also refers to the V2Ray core maintained by that project. v2flyNG uses this core. For examples generated by other cores, first check whether the protocol, transport, and fields are supported.

Xray

Xray-core originated from V2Ray and is now maintained independently; v2rayNG uses the Xray core. The two share some configuration concepts, but their supported features and fields are not identical. If an unknown-field error appears, first check that the core generating the configuration matches the one reading it.

Core

The core reads the configuration, establishes connections, and applies routing. The graphical client manages nodes, generates configuration, and controls the core process. Whether a client can run a node depends on the core and version in use, not just on whether the interface displays a protocol name.

Clients and Subscriptions

Subscription updates, node reachability, and application traffic are three separate checkpoints. Passing one does not mean the next is working.

Subscription

A subscription uses a URL to retrieve a set of node configurations; updating it fetches the remote list again. Loading the list successfully does not mean its nodes are reachable. A subscription URL with access parameters may let anyone who has it read the list, so redact the full URL before sharing logs or screenshots.

Node

A node is a remote proxy configuration you can select in a client. It typically includes a server address, port, protocol, and authentication details. The name in the list is for identification and does not replace connection parameters. Two nodes with the same name may use different addresses or transports.

Latency

Latency is the time measured by a particular probe, usually shown in milliseconds. An ICMP probe, a TCP connection, and a request sent through a proxy each measure a different part of the connection. Compare results using the same test method and target; lower latency does not mean higher throughput.

Real Connection Latency

Real connection latency is typically measured by sending a request to a test URL through the selected node, checking whether the request succeeds, and recording the time taken. Results depend on the test URL, network path, and timeout settings. Failure to reach one test URL does not mean all destinations are unreachable.

System Proxy

System proxy settings provide a proxy address and port to applications that follow the operating system's proxy configuration. Some command-line tools use their own proxy options or environment variables, so a browser using the proxy does not mean a terminal does too.

TUN Mode

TUN mode uses a virtual network interface to receive IP traffic routed to it by the operating system, without relying on applications to read system proxy settings. Which traffic it captures depends on permissions, system routes, and exclusions. Once traffic enters TUN, client rules can still determine its outbound route.

Routing and DNS

Whether a rule matches depends on whether the core receives a domain or an IP address, and on how the current configuration resolves domains. See the DNS section of the JSON manual for field examples.

Routing Rules

Routing rules pair matching conditions with an action, such as sending connections to a specific outbound based on the destination domain or IP. In V2Ray's routing list, rules are evaluated in order and the first match takes effect. Narrow exceptions usually belong before broader rules.

Split Tunneling

Split tunneling sends different connections through different outbounds, such as routing local network traffic directly while proxying selected traffic. It applies to traffic that has entered the core. Before troubleshooting rules, confirm that the target application's connections reach the core through the system proxy or TUN.

GeoIP

In routing configuration, GeoIP refers to IP address range data organized by labels. It can match a destination IP against a specified set. Results depend on the data file currently loaded. Whether a domain can be matched by an IP rule also depends on whether the core resolves it for routing decisions.

GeoSite

GeoSite is categorized domain data referenced by routing rules. Categories vary by dataset and version and do not indicate where a service is hosted. If an application passes only the destination IP to the core and the core cannot recover the domain, domain rules cannot match.

Built-in DNS

The core's built-in DNS sends domain queries according to its own configuration, for example to obtain destination IPs for IP-based routing rules. It is separate from the system resolver and resolvers built into applications. Changing the core's DNS server list does not automatically take over every application's DNS requests.

FakeDNS

FakeDNS returns synthetic addresses and stores a mapping between each address and its domain, allowing the core to recover the original domain when it receives a connection to that address. Later connections must return to a core that can read this mapping. If an application takes another network path, the synthetic address usually cannot reach the destination directly.

Encryption and Security

Check server identity verification and the DNS query path separately. An encrypted connection does not mean DNS requests follow the expected route.

TLS

TLS encrypts traffic between two endpoints and protects its integrity; clients usually also verify the server's certificate and name. Here, outer TLS protects the connection between the client and proxy server. HTTPS used by an application to access a destination site is a separate layer of connection security.

SNI

SNI (Server Name Indication) is sent during the TLS handshake so the server can select the appropriate certificate or site. The connection address can be an IP while SNI remains a domain name. When the client verifies a certificate against a domain, that name should match one covered by the certificate.

ALPN

ALPN lets both ends negotiate an application protocol during the TLS handshake; common identifiers include h2 and http/1.1. It does not authenticate users or select a proxy protocol. If the transport depends on HTTP/2, make sure the server and any proxy layers along the route allow the required negotiation.

DNS Leak

A DNS leak occurs when domain queries expected to follow a specified route are sent to an unintended resolver, potentially exposing the queried names. A website connection going through a proxy does not prove that its DNS queries follow the same route. Check system DNS, browser DNS settings, and core DNS separately.