Configuration reference

V2Ray glossary

For node settings, distinguish the protocol, transport, and security layer. For local settings, distinguish how traffic enters the client and where it exits.

Protocols & transports

VMess

VMess is a proxy protocol in the Project V ecosystem that uses a user ID for authentication. In a node’s details, VMess identifies the protocol used to exchange proxy data between the client and server. Transport and security are separate settings and cannot be inferred from the protocol name alone.

VLESS

VLESS is a proxy protocol that authenticates with a user ID. Common configurations pair it with TLS or REALITY to protect the connection. Two VLESS nodes can still use different transports, server names, or flow-control options, so don’t copy settings from one node to another without checking them.

Trojan

Trojan typically runs over TLS and uses a password for proxy authentication. Password authentication and server identity verification are separate: a correct password does not guarantee that the server certificate matches the name expected by the client.

Transport

Transport describes how proxy data travels between the client and server. Common options include WebSocket and gRPC. The settings on both ends must match; depending on the transport, the path or service name may also need to match. Changing the transport does not change the proxy protocol.

Cores & clients

Proxy core

The core establishes connections, applies routing rules, and forwards traffic. The GUI client turns settings from its interface into a configuration the core can read. An open main window only confirms that the GUI is running; to verify that it is handling traffic, check the core’s status and local listeners.

Xray

Xray is an independent proxy core project that grew out of the V2Ray ecosystem and supports features such as REALITY. To check whether a node will work, look beyond its protocol name: verify that the running core supports the node’s transport, security layer, and flow-control options.

V2Fly

V2Fly is an open-source project continuing development of the V2Ray core. V2Fly and Xray share some protocol and configuration concepts, but their features and release paths differ. A setting supported by one core may not work the same way in the other.

v2rayN

v2rayN is a desktop GUI client for importing subscriptions, selecting nodes, and managing proxy cores. The client and core have separate version numbers. When troubleshooting incompatible settings, note both the GUI version and the version of the core actually running.

Security & encryption

TLS

TLS protects communications between two endpoints with confidentiality and integrity, and commonly uses certificates to verify the server’s identity. TLS on a proxy connection can coexist with TLS used to access an HTTPS site, but they protect different connections.

REALITY

REALITY is a connection security mechanism implemented by Xray that can be used with VLESS, but it is not VLESS itself. Parameters such as the public key and short ID configure this security layer; they are different from the user ID used by the proxy protocol.

SNI

SNI is a TLS extension that tells the server which server name the client wants to connect to. One address can serve multiple domains, so a node’s connection address and configured server name may differ: the address locates the endpoint, while the server name is used during the handshake.

Routing & DNS

Routing rules

Routing rules use criteria such as domain, destination address, or port to decide which outbound route traffic takes, such as direct, proxy, or block. Sending different traffic through different outbounds is called split tunneling. When rules are matched in order, put specific exceptions before broad rules; otherwise, a broader rule may catch the traffic first.

GeoIP

GeoIP data organizes IP ranges by region or purpose for use in routing rules. A match only means the destination address falls within a range listed in the data file; it does not identify where a website operator is based or replace domain-based matching.

GeoSite

GeoSite groups domains by service or purpose so routing rules can reference them by category. Categories vary by data source and update. If a rule only has the destination IP and no domain information is available, it cannot match against a domain category directly.

System proxy

A system proxy registers a proxy address and port with the operating system for apps that support those settings. Apps may use their own proxy settings or connect directly, so a browser working through the system proxy does not mean command-line tools or other apps will take the same route.

TUN mode

TUN mode uses a virtual network interface to pass IP traffic covered by system routing rules to the client. Apps do not need to read the system proxy settings, but traffic entering the virtual interface is not necessarily sent through a remote node. The client’s routing rules still determine whether it goes direct or through a proxy.

FakeDNS

FakeDNS returns a temporary virtual address for a domain and keeps a mapping between them. When a later connection enters the same processing chain, the core can use the mapping to recover the domain and apply domain-based routing. The virtual address is not the real address of the destination server, and the component handling the traffic must be able to read the mapping.

DNS leak

A DNS leak occurs when a query is sent to a resolver outside the intended policy. Web traffic and DNS queries can take different routes, so successfully opening a website does not prove that DNS followed the expected path. When troubleshooting, check both the system resolver and any encrypted DNS settings in the app.

Subscriptions & node management

Subscription

A subscription lets a client fetch and update a set of node configurations at once. Updating a subscription refreshes the local list; it does not select a node or establish a connection. Subscription URLs may contain account credentials, so hide the full URL before sharing logs or screenshots.

Node

A node is a set of connection settings saved by the client, typically including an address, port, protocol, authentication details, and transport settings. Its name is only a label: two nodes with the same name may point to different endpoints, and changing a label does not change the connection settings.

Connection latency

Connection latency usually measures how long the client takes to access a test address through the selected node; the exact method varies by client. It is not the same as an ICMP ping to the server or a measure of sustained download speed. For a fair comparison, use the same client and test address under similar network conditions.