Configuration Reference

V2Ray and Xray Glossary

Look up terms by configuration layer: distinguish protocols, transports, and cores; then see how subscriptions provide connection settings, how routing selects an outbound, and how app traffic reaches the client.

Follow the setup steps in Getting Started, or see the full parameter reference in the Advanced Setup manual.

01 / Protocol & Transport

Protocols & Transports

A proxy protocol defines how both ends identify users and exchange data. Transport and security layer settings are separate options, so the protocol name alone can't tell you whether a configuration is compatible.

Protocol

VMess

VMess is a proxy protocol in the Project V ecosystem that identifies users with UUIDs. A connection can fail even when the address and port are correct if the UUID or transport settings don't match. Authentication also depends on time, so if the handshake fails, check that both systems' clocks are synchronized.

Protocol

VLESS

VLESS identifies users with UUIDs but does not encrypt payloads itself. After selecting VLESS as the protocol, set the transport and security layer to match the server configuration. TLS and REALITY are security layer options, not other names for VLESS.

Protocol

Trojan

Trojan authenticates users with a password and typically runs over TLS. The password and TLS settings serve separate purposes—user authentication and connection security—and both must be correct. If the client reports a certificate name mismatch, check the TLS server name rather than changing the node label.

Transport Security

REALITY

REALITY is Xray's transport security mechanism and is commonly used with VLESS. The server name, public key, and short ID are security layer settings; use the values provided by the server, not details inferred from the node name. If the client offers a corresponding option, make sure the selected core supports it.

Transport

Transport

Transport determines how proxy protocol data is carried, for example over WebSocket or gRPC. Each transport has its own settings: a WebSocket path and a gRPC service name are not interchangeable. Even with the same proxy protocol at both ends, a transport mismatch will prevent the connection from working.

02 / Core & Ecosystem

Cores & Ecosystem

The client provides the interface; the core reads the configuration and handles connections. When checking feature support, distinguish the GUI client version from the version of the core actually running.

Ecosystem

Project V

Project V is the open-source ecosystem originally associated with V2Ray, not a separate GUI client to launch after installation. In documentation, V2Ray may refer to the core or to the wider ecosystem. When troubleshooting, note the actual client, core name, and version rather than just writing “V2Ray.”

Core Project

V2Fly

V2Fly is a community project continuing V2Ray development and maintaining v2ray-core and its documentation. Clients such as v2rayN turn GUI settings into core configuration. When using a configuration example, make sure it targets the same core; Xray-specific fields can't simply be copied over.

Core

Xray

Xray is a proxy core forked from the V2Ray codebase. It listens for inbound connections, selects outbounds according to routing rules, and establishes connections. v2rayN and v2rayNG can manage the related settings through a GUI. If the core log says a field is unrecognized, first check which core and version actually started.

03 / Subscriptions & Servers

Subscriptions & Nodes

Subscription updates fetch server configurations; connection tests check whether those configurations work. They may use different network paths, so review their results separately.

Subscription

Subscription

A subscription is a source clients use to fetch server configurations in bulk, usually by adding a URL. The server list updates only when the client receives a response and recognizes its format. Subscription URLs may contain access credentials, so hide the URL and query parameters before sharing screenshots or update logs.

Group

Subscription group

Subscription groups organize server entries by source, making it easier to update and filter them separately. A group name only organizes the list; it doesn't change outbound routing. If an update brings in fewer entries than expected, first check that you updated the right group, then review its filter settings.

View subscription group settings
Server Entry

Node

A node is a server connection profile in the list, with an address, port, protocol, and required settings. Region and route names are usually just labels and aren't used in the handshake. Multiple nodes may also point to the same server but use different ports, protocols, or transports.

Connection Test

Real connection latency

Real connection latency is the time a client records when accessing a test address through the selected node; the exact timing depends on how the test is implemented. It differs from a direct server round-trip measurement and doesn't indicate download throughput. To compare nodes, use the same test address and network, and note whether timeouts recur.

04 / Routing & DNS

Routing & DNS

When troubleshooting a connection, check separately which resolver handles the domain, whether the core receives a domain or an IP, and which routing rule the connection ultimately matches.

Rule

Routing rule

Routing rules match connections by conditions such as domain, IP, or port, then use an outbound tag to specify how to handle them. Xray checks rules in order and stops at the first match. If a more specific rule doesn't take effect, check whether an earlier, broader rule already matched.

View routing rules
Outbound Selection

Traffic routing

Traffic routing sends different connections through different outbounds, such as a proxy, direct connection, or block. It determines where connections already inside the core go; it doesn't determine which connections the operating system sends to the core. If an app's traffic never reaches the proxy inbound, changing routing rules won't affect it.

IP Data

GeoIP

GeoIP is categorized IP address range data referenced by routing rules and can also classify private address ranges. It matches IPs, not website or provider names. If the core receives a domain, whether it gets an IP to match also depends on the domain strategy and DNS resolution result.

Domain Data

GeoSite

GeoSite is categorized domain-matching data that lets routing rules reference category labels instead of maintaining domains one by one. Available labels and coverage depend on the data file actually loaded. A service may use both its main domain and separate asset domains, so matching the former doesn't necessarily cover the latter.

DNS Mapping

FakeDNS

FakeDNS returns a synthetic IP for internal use and stores its mapping to the domain. When a later connection reaches a core that supports the mapping, the core can recover the original domain and apply domain-based routing. If DNS queries are intercepted but subsequent connections aren't, an app may receive a synthetic address it can't reach directly.

Resolver Path

DNS leak

A DNS leak occurs when queries don't use the intended path or resolver. An app may use its own encrypted DNS or fall back to the system resolver. When troubleshooting, first define which resolver should be used, then test the browser and other apps separately. Whether a webpage opens isn't enough to determine if DNS is leaking.

05 / Client Functions

Client Features

First check how traffic reaches the client, then whether the core can identify the destination and apply rules. The system-level traffic handling method and the core's routing configuration are separate layers.

Virtual Interface

TUN mode

TUN mode receives system-routed IP traffic through a virtual network interface, including traffic from apps that ignore system proxy settings. The traffic it captures still depends on routing, exclusions, and permissions. If local network services become unreachable after enabling it, check whether the local subnet is routed through the virtual interface.

System Setting

System proxy

The system proxy sets the operating system's proxy address and port to the client's local listening address. Only apps that follow this setting send the relevant connections to the client. If just one app can't connect, check whether it uses the system proxy or has its own proxy settings.

Sniffing

Traffic sniffing

Traffic sniffing attempts to extract clues such as domain names from protocol headers or handshake data for routing. This can let the core match domain rules even when the connection initially provides only an IP. What can be extracted depends on the traffic type and visible data; sniffing does not decrypt app content.

Inbound Port

Local listening port

The local listening port is the entry point where the client accepts app connections on the same device, not the remote node's port. When configuring an app's proxy manually, make sure its local address, port, and SOCKS or HTTP type match the inbound settings. After changing the port, update any apps with separately configured proxy settings.