Configuration reference

V2Ray Glossary

Look up what each setting does, from protocol names in node profiles to routing and DNS options after connecting.

Importing a profile for the first time? Start with subscriptions and nodes. Already connected, but traffic isn't taking the expected route? First distinguish routing and traffic splitting from DNS and network modes.

Protocols and transport

A protocol defines how two sides exchange proxy data; transport determines how that data is delivered.

VMess
VMess is a proxy protocol in the V2Ray ecosystem that typically uses a UUID to identify users. Authentication depends on the clocks on both ends being roughly in sync. If the address and profile haven't changed but the connection suddenly stops working, check whether automatic time synchronization is enabled on the device.
VLESS
VLESS is a proxy protocol that authenticates users by ID and is commonly configured with TLS or REALITY. When editing a node, the protocol and connection security are separate settings. Simply changing the protocol name to VLESS does not mean you can reuse every parameter from another protocol.
Trojan
Trojan is a proxy protocol that typically runs over TLS and uses a password for authentication. The password and the TLS server name are separate settings: the former is used for authentication, while the latter tells the client how to verify the server.
REALITY
REALITY is a connection security mechanism implemented by Xray, often paired with VLESS. In this configuration, select VLESS as the protocol and REALITY as the connection security option. Parameters such as the public key must match the server configuration; don't copy them from another node.
Transport
Transport is how proxy protocol data is carried between the client and server, for example over WebSocket or gRPC. Even when both ends use the same protocol, communication will fail if their transport settings differ. With WebSocket, make sure the path matches on both sides.

Cores and clients

Being able to import a profile in the app doesn't necessarily mean the core can run it.

Core
The core is the software that establishes connections, handles protocols, and applies routing rules. App and core versions are usually maintained separately. If you get an unsupported-field error, note both versions to make troubleshooting easier than reporting just the client name.
Xray
Xray is a proxy core maintained by the Xray project and used by v2rayNG. Some configuration concepts overlap with V2Fly, but the implementations and features are not identical. If a profile uses REALITY, make sure the core actually supports it.
V2Fly
V2Fly is an open-source project that maintains the V2Ray core implementation and related documentation. v2flyNG uses an implementation from this core family. Before following configuration instructions, check which core project they apply to so you don't assume similarly named fields behave the same way.
GUI client
A GUI client is an app that manages profiles through an interface and runs a proxy core, such as v2rayN or v2rayNG. Clients typically provide subscription groups, profile editing, and testing tools. Menu locations can differ even between clients that use the same core family.

Subscriptions and nodes

A subscription is a source of profiles; a node is one profile you can select and use.

Subscription
A subscription lets a client fetch and refresh connection profiles from a URL. A successful update only means the client retrieved the list; it doesn't mean every node in it is reachable. Subscription links may contain credentials, so hide the full URL before sharing screenshots or logs.
Node
A node usually means one remote connection profile in a list, including its address, port, protocol, and required parameters. The displayed name is just a label: two profiles with the same name can point to different addresses, and one address can offer different ports or protocols.
Subscription group
Subscription groups keep profiles from different subscription URLs organized separately. To refresh just one source, check which group is selected, then choose the command to update that group. A group does not determine which outbound an app's traffic uses.
Real connection latency
Real connection latency is the time measured when accessing a test destination through a node; it is not the same as pinging the server address. Results depend on the test destination, handshake, and network conditions. For a fair comparison, use the same destination and don't confuse latency with download speed.

Routing and traffic splitting

Conditions determine which rule matches; the outbound determines what happens next.

Routing rule
Routing rules select an outbound for a connection based on conditions such as domain, IP address, or port. In common configurations, the core checks rules in order and uses the first match. If a specific rule doesn't take effect, check whether an earlier, broader rule is overriding it.
Traffic splitting
Traffic splitting sends different connections through different outbounds—for example, connecting directly to local network addresses while handling other requests according to subsequent rules. It only applies to traffic that has entered the relevant routing process; it does not replace the system proxy or TUN mode for capturing app traffic.
GeoIP
GeoIP is IP address range data used by routing rules, for example to match private address ranges. It does not match domains directly. If the core has a domain rather than an IP address, whether it can match an address range depends on domain resolution and the routing policy.
GeoSite
GeoSite is domain category data used by routing rules, letting you match a set of related domains with a single condition. Category names and included domains depend on the data file. If you switch to another data file, check that the category your rules reference is still available.
Outbound
An outbound defines how the core handles traffic, such as connecting directly, forwarding it to a remote proxy, or dropping it. The outbound tag in a profile is the name referenced by routing rules, not the node label shown in a list. If you rename it, check that all references still match.

DNS and network modes

First check how app traffic reaches the client, then check which resolver handles domain lookups.

System proxy
The system proxy uses the operating system's proxy settings to tell apps that read them to send requests through a proxy. It does not automatically capture every app's connections. A browser using the proxy doesn't mean an app with its own network settings is using it too.
TUN mode
TUN mode receives IP traffic routed to the client by the system through a virtual network interface. Apps don't need to read the system proxy settings. The actual coverage depends on system routes and exclusions; enabling TUN alone doesn't mean every connection uses a proxy outbound.
FakeDNS
FakeDNS returns a temporary mapped address for a domain. When the client receives a later connection, it looks up the original domain and can route based on the domain name. The mapped address is not the destination server's address; the component receiving the connection must be able to recognize the mapping.
DNS leak
A DNS leak occurs when domain lookups bypass the intended resolution path and reach an unexpected resolver. Before checking for leaks, identify which resolver should handle each lookup, then review the app's encrypted DNS and system DNS settings. A website loading successfully doesn't mean DNS followed the expected path.