Configuration glossary

V2Ray Glossary

Look up terms by where they apply: node settings cover protocols and transports, subscription updates cover the source of node lists, and routing determines where traffic goes after connecting. System proxy and TUN control how traffic enters; choosing an outbound happens afterward.

01 Node connection settings

Protocols & Transports

A protocol defines how proxy requests are identified between the client and server. A transport carries the data, while transport security is configured separately. Match each setting to the server configuration when editing a node.

VMess

VMess is a proxy protocol in the Project V ecosystem. Clients use parameters such as a UUID to communicate with the server. The handshake checks the time, so a large clock difference can prevent authentication even when the address and port are reachable. When troubleshooting, sync the system clock first, then check the transport and security settings.

VLESS

VLESS is a proxy protocol that identifies users with a UUID and does not provide traffic encryption on its own. TLS or REALITY provides transport security; the protocol name alone does not tell you whether either is enabled. In the configuration, flow is a flow-control field. Use the value provided by the server rather than copying it from another node.

Trojan

Trojan typically carries proxy requests over a TLS connection and uses a password for authentication. When a connection fails, check the logs to distinguish between the TLS handshake and proxy authentication: a certificate name mismatch and an incorrect password are different issues.

REALITY

REALITY is a transport security mechanism supported by Xray and is often paired with VLESS. After importing a node, check that the core supports it and that the client's server name, public key, Short ID, and other settings match the server configuration. Seeing the node in the list confirms only that it was imported, not that the handshake succeeded.

WebSocket

WebSocket is a transport that can carry data for proxy protocols. The WebSocket path in a node's settings matches the server's handshake endpoint; it is not a page path for everyday browser use. When TLS is enabled, the WebSocket Host and the TLS server name belong to different layers and should be checked separately.

02 Software layers

Cores & Ecosystem

The GUI manages settings; the core handles connections. To check whether a feature is supported, look at the core and version actually in use, not just the client name.

Project V

Project V is the open-source network proxy ecosystem that includes V2Ray. Some configuration names in older documentation come from conventions shared across this ecosystem, but always check the documentation for the core you use. Project V is neither a node provider nor the name of a GUI client.

V2Fly

V2Fly is a community project continuing V2Ray development. Its core program reads configuration and processes traffic. v2flyNG is an Android GUI client that uses this core. When troubleshooting node compatibility, first check whether the core supports the protocol and transport security options, then compare the node settings.

Xray

Xray is an independent core developed from a fork of the V2Ray core and maintained by Project X. It shares some configuration concepts with V2Fly, but not every parameter is interchangeable. In v2rayNG, if a node field is unrecognized, first check the actual core version and whether it supports the relevant feature.

GUI client

A GUI client manages nodes, subscriptions, and local settings, then passes the relevant configuration to the core for processing. v2rayN, v2rayNG, and v2flyNG all belong to this layer. Opening the interface, importing a node, and starting the core are three separate checks; one does not confirm the others.

03 Import & testing

Subscriptions & Nodes

First identify where the node list comes from, then check which profile is selected. Updating the list and testing a connection are separate actions.

Subscription

A subscription is typically a URL that provides a list of nodes. When refreshed, the client fetches it again and parses the response. After a successful update, check that the new entries appear in the current group. Subscription URLs may contain access credentials, so redact the full link before sharing screenshots or logs.

Node

A node is a connection profile in a client, containing details such as the server address, port, protocol, and authentication parameters. The note in the list is just a display name; it does not confirm the server's location or affect the protocol handshake. Two entries with the same address may still be incompatible if their protocol or transport settings differ.

TCP latency

A TCP latency test measures how long it takes to establish a TCP connection to the node's address and port. It can help determine whether the port is reachable, but it does not verify proxy authentication or whether a destination page is available, and it is not a download speed test. Compare results from the same type of test; don't mix them with proxy latency results.

Proxy latency

A proxy latency test sends a request to a test URL through the selected node and measures the time taken along that request path. Results depend on the test URL, handshake, and current network conditions; they are not the node's round-trip time. A timeout from one test URL does not prove the node is unusable for every destination.

04 Matching & outbounds

Routing

When troubleshooting routing, first check whether the core received a domain or an IP address. Then check the first matching rule and the outbound it references.

Routing rule

Routing rules select an outbound for traffic based on conditions such as domain, destination address, and port. The core checks rules in configuration order, and the first match determines where traffic goes. Broad rules placed first may prevent more specific rules later in the list from matching.

Traffic routing

Traffic routing sends different traffic already received by the core to different outbounds. For example, LAN destinations can go direct while other matched requests use a specified proxy. If an app's traffic never reaches the local proxy or virtual interface, changing the core's routing rules won't affect that app.

Outbound tag

An outbound tag is the name identifying an outbound in the configuration; routing rules use it to select that outbound. Common tags such as direct, proxy, and block are naming conventions; behavior depends on the outbound configuration assigned to each tag. Renaming an outbound to block does not automatically block requests.

GeoIP

GeoIP is a collection of IP address ranges grouped by category, used by routing rules to match destination addresses. For example, geoip:private can match private and reserved address ranges defined by the rule set. If the core receives a domain, whether it resolves it to an IP for matching also depends on the domain resolution strategy.

GeoSite

GeoSite is a collection of domain rules grouped by category, commonly supplied by geosite.dat. geosite:cn refers to the cn category in the current rule set; it does not mean every listed domain resolves to the same region. If a rule does not match, first check that the category exists and that the core received the destination domain.

Domain resolution strategy

In a routing configuration, domainStrategy determines whether domain requests are resolved to IP addresses when matching routing rules. For example, IPIfNonMatch lets the core resolve a domain after the initial match fails, then use the resulting IP to check the rules. This setting does not specify an upstream DNS server.

05 Local traffic & DNS

Client Features

App traffic and DNS queries do not necessarily follow the same path. Check how traffic enters the client, then inspect connection and DNS routing separately.

System proxy

The system proxy directs requests from apps that follow the operating system's proxy settings to a specified proxy address. Apps that manage their own network connections may ignore this setting. After enabling the system proxy, check that the local port is listening and which outbound the core selects for each request.

TUN mode

TUN mode receives IP traffic routed by the operating system through a virtual network interface. Unlike a system proxy, it usually does not require apps to support proxies themselves, but which networks and apps are intercepted still depends on system and client settings. Starting the virtual interface does not guarantee that DNS or LAN traffic is handled as expected.

Local listening port

A local listening port is where the client accepts connections on the device; it is separate from the node's remote port. If another process is using the port, the core may be unable to start the corresponding inbound. After changing the port, update any apps where you manually entered the proxy address; do not change the remote node.

FakeDNS

FakeDNS maps domains to synthetic IP addresses so the core can recover the domain from subsequent connections. These synthetic addresses identify traffic; they are not the actual addresses of destination servers. If DNS uses FakeDNS but the app's connection does not pass through a handler that can access the mapping, the connection may fail.

DNS leak

A DNS leak occurs when queries that should use a specified resolver or route are instead sent to an unexpected resolver or take a different path. Before checking, identify which domains are intentionally allowed to resolve locally and whether the browser has its own encrypted DNS setting. A working website or successful proxy test alone cannot confirm how DNS queries are routed.

Download a client