Quick reference Configuration guide

V2Ray Glossary

Subscriptions fetch nodes, system proxy and TUN capture traffic, and routing rules decide which outbound handles it next. Browse by category to see what each term does in a configuration.

Cores and ecosystem

Distinguish projects, cores, and graphical clients before checking which component handles a setting.

Project V

Project V is a starting point for understanding V2Ray and its early open-source ecosystem—not a setting you need to enter in v2rayN. In tutorials, “V2Ray” may refer to the core itself or more broadly to related clients and protocols. When following configuration instructions, first check which client and core they cover.

V2Fly

V2Fly is a community project that continues V2Ray’s open-source development; the name also commonly refers to the family of cores maintained by the project. v2flyNG is a graphical client, while the V2Fly core handles connections. They operate at different software layers. To determine whether a setting is available, check both core support and whether the client exposes it.

Xray

Xray is a core derived from V2Ray’s core code. It handles connections, applies routing rules, and establishes outbound connections. v2rayNG uses Xray, and v2rayN also offers core type options related to Xray. Whether a core recognizes a field is separate from whether a subscription imports successfully.

Core type

Core type specifies which core runs a configuration; it does not change a node’s protocol. If the import succeeds but startup fails, check the logs to see which core reported an error, then verify the node’s protocol, transport, and security settings. Switching cores will not automatically convert incompatible node parameters into values accepted by the server.

Transport protocols

VMess, VLESS, and Trojan are proxy protocols; WebSocket is a transport that can carry proxy traffic.

VMess

VMess is a proxy protocol in the V2Ray ecosystem. It identifies authorized users with a UUID and provides its own data encryption. If a handshake fails, check the address, port, and UUID, as well as whether the device clock is accurate. VMess is not WebSocket; WebSocket is one possible transport for carrying it.

VLESS

VLESS is a proxy protocol that typically uses a UUID as the user identifier. In a node labeled “VLESS + REALITY,” VLESS specifies the proxy protocol, while REALITY specifies the connection security mechanism. After importing, check the protocol, transport, and security fields separately; matching names alone do not guarantee equivalent configurations.

Trojan

Trojan is a proxy protocol that typically runs over TLS and uses password authentication rather than the UUID user identifiers used by VMess or VLESS. If a connection fails, distinguish an incomplete TLS handshake from authentication failure after a successful handshake; each points to different fields. Don’t copy authentication fields from another protocol.

WebSocket

WebSocket is an optional node transport, not a standalone proxy protocol. In addition to the address and port, it may require a matching path and HTTP Host. Changing a node’s remark does not change its path or Host; use the actual connection parameters for those fields.

Encryption and obfuscation

Handshake mechanisms, server names, and flow control are separate settings; check each one independently when troubleshooting.

TLS

TLS encrypts connections and protects their integrity; clients usually also verify the server certificate. If the certificate name doesn’t match, check the server name against the domains covered by the certificate. If the certificate dates are invalid, check the device clock too. Don’t disable certificate verification as a substitute for finding the cause.

SNI

SNI is a TLS handshake extension that lets the client send the server name, allowing a service at a shared address to select the right certificate or configuration. It is neither the address to connect to nor the WebSocket HTTP Host. Even when several fields contain the same domain, they serve different purposes in the connection.

REALITY

REALITY is a connection security mechanism supported by Xray and is often paired with VLESS. The client uses parameters such as the server name, public key, and short ID as configured on the server; these are not the same as the VLESS user identifier. REALITY is not a flow control option, so keep its settings distinct from those for XTLS Vision.

XTLS Vision

XTLS Vision is a flow control mode in Xray. A common value in VLESS node configurations is xtls-rprx-vision. Under suitable connection conditions, it can reduce redundant processing and encapsulation of already encrypted traffic. Whether to use it depends on both ends; it is not a speed boost switch for every node.

Subscriptions and nodes

Fetching a list, selecting a node, and verifying a connection are three separate steps; completing one doesn’t mean the others succeeded.

Subscription

A subscription link usually provides a set of node configurations, which the client fetches again when you update the subscription. A successful update means the content was reachable and could be parsed; it does not mean every node works or that the proxy is enabled. Subscription links may contain access credentials, so hide the full URL in screenshots.

Subscription group

Subscription groups organize nodes by source within a client. In v2rayN, “Add subscription group” registers a source, while “Update all subscriptions” refreshes registered sources. If node names or lists change after an update, check which node is selected before determining whether the connection failure followed a node switch.

Node

A node is a set of parameters for establishing a connection. It typically includes a server address, port, proxy protocol, and authentication details, and may also include transport and security settings. Its remark is just a name for identifying it in a list and may not match the server address. Selecting a node does not route traffic through it; apps still need to send traffic to the client through an appropriate mechanism.

Real connection latency

Real connection latency usually means the time a client takes to reach a test address through a selected node. Unlike TCP latency, which only probes the server’s port, it cannot be directly converted into download speed. Compare results using the same test address and settings. If a test times out, check whether the node failed to connect or the test address itself was unreachable.

Routing

To understand a rule, first find its matching conditions, then see which outbound handles matching traffic.

Routing rule

Routing rules match traffic using conditions such as domain, destination IP, and port, then send matching traffic to a specified outbound. V2Ray-family cores generally check rules in order, so an earlier, broader rule may match first and prevent a later exception from taking effect. When troubleshooting, find the rule that actually matched, then check whether it selected the right outbound.

GeoIP

In routing configurations, GeoIP usually refers to a set of IP address ranges organized by region or purpose, used to match destination IPs. It does not match domains directly. Whether a rule matches an IP resolved from a domain also depends on the routing domain strategy. If the same site gets inconsistent matches, check whether it resolved to different IPs.

GeoSite

In routing configurations, GeoSite usually refers to collections of domain rules organized by category, such as geosite:category-ads-all. A collection provides matching criteria; it does not decide whether traffic goes direct, through a proxy, or gets blocked. If a category is missing or results differ from expectations, first check that the local data file includes it, then review rule order.

Routing

Routing sends different connections entering the client to different outbounds—for example, sending local network services direct while proxying other matching traffic. Routing happens after traffic reaches the client. If an app neither uses the system proxy nor has its traffic captured by TUN, changing routing rules alone won’t affect it.

Client settings

First check how app traffic enters the client, then separately check the path taken by DNS queries.

System proxy

The system proxy is an operating system setting that apps can use to connect through a proxy. For example, “Set system proxy automatically” in v2rayN points the system proxy to a local listening port, but not every app reads this setting. If a browser connects but another app doesn’t, first check whether that app uses the system proxy.

TUN mode

TUN mode captures traffic routed by the operating system through a virtual network interface, so apps don’t each need a proxy address configured. Enabling it may require system permissions. If other virtual networking tools are running on the device, check for routing conflicts. To compare the two traffic capture methods, enable only one at a time to make troubleshooting easier.

FakeDNS

FakeDNS returns synthetic IPs managed by the client for domains it has queried and keeps a record of the mapping. When the client captures a connection to one of these IPs, it can recover the original domain and use it for routing. FakeDNS is not a regular DNS cache; it works as expected only when both the query and subsequent connection follow the intended processing path.

DNS leak

A DNS leak occurs when domain queries that should follow a specified path are sent by the system or an app to a different resolver. Proxying web traffic does not prove that DNS queries use the same path. When troubleshooting, check system DNS settings, the browser’s Secure DNS options, and how the client captures and forwards queries.

Download V2Ray clients