Client Configuration Glossary

V2Ray Glossary

Before importing a link, make sure you know whether it’s a node or a subscription. In the settings, distinguish the protocol from the transport and security options. This glossary explains 25 common terms across six categories, with a link to each entry.

Protocols and transports

The protocol defines how the two sides exchange data; the transport defines how that data is delivered. These settings are usually configured separately when editing a node.

Proxy protocol

VMess

A proxy protocol in the Project V ecosystem that typically identifies users by UUID. When importing or entering a node manually, check the UUID and make sure the transport and connection security settings match the server. If everything looks right but the connection still fails, check your system date and time—a clock mismatch can interfere with authentication.

Proxy protocol

VLESS

A proxy protocol whose configurations commonly identify users with a UUID. VLESS is often paired with TLS or REALITY, configured separately as the protocol and connection security settings. Two nodes can both use VLESS but have different transports or flow-control settings, so don’t swap their configurations based on the protocol name alone.

See how REALITY works →
Proxy protocol

Trojan

A proxy protocol that typically uses TLS for connections and password-based authentication. When editing a node, note that this password is not your client login password; it’s the authentication credential configured on the server. If the log reports a certificate name mismatch, check the server name and certificate configuration first rather than assuming the password is wrong.

Transport

WebSocket

WebSocket is a transport, not an alternative to VMess or VLESS. Selecting it often reveals Path and Host fields in the settings. If the path doesn’t match, the handshake may fail even when the address and port are correct. WebSocket can be used with TLS; check the server configuration to see whether it’s enabled.

Cores and ecosystem

When troubleshooting compatibility, first identify whether a name refers to a project, a core, or a client. Each has its own version numbering.

Project background

Project V

Project V is a name often found in accounts of the V2Ray ecosystem’s history. It is neither a proxy protocol nor a graphical client. When you see it in older documentation, check the publication date to tell whether it refers to the original project or related software. Before following a guide, check the menus and core in the client you’re actually using.

Core projects

V2Fly

V2Fly is a community project that continues V2Ray development. Its core handles connections, routing, DNS, and more. v2flyNG uses this core. Its name is similar to v2rayNG, which uses the Xray core, but the two clients don’t support exactly the same features. Before using a manual configuration example, check which core it targets.

Core projects

Xray

Xray is an independent core project that grew out of the V2Ray ecosystem, with its own features and release schedule. v2rayNG uses the Xray core, but the app version and core version are different. When importing a node with settings such as REALITY, check which fields are supported by your current core and client.

Runtime components

Core

The core establishes connections, applies routing rules, and forwards traffic. The graphical client organizes settings and runs the core. A working interface doesn’t mean the core has started successfully. If connecting triggers an immediate error, check the client log to see whether configuration parsing failed, a port is already in use, or the core process failed to start.

Browse setup guides for all platforms →

Client features

The traffic entry point determines which apps send traffic to the client; the speed test determines what the numbers in the list actually measure.

Traffic routing

System proxy

A system proxy is a set of proxy settings provided by the operating system for apps, usually specifying a local proxy address and port. Only apps that read and honor these settings use this route. If a browser works but another app doesn’t, check whether that app has its own proxy settings before trying a different traffic entry method.

Traffic routing

TUN mode

TUN mode receives IP traffic from the system through a virtual network interface, then processes it according to the client’s rules. It can cover some apps that ignore system proxy settings, but the actual scope depends on system routing, exclusions, and permissions. If local network devices become unreachable after switching modes, check whether local network traffic is being captured.

Compare with system proxy →
Connection tests

Latency

Latency is the time from starting a test to receiving a response, usually measured in milliseconds. Depending on the test, it may check only whether a connection to the server port can be established or send a real request. Results from different test modes aren’t directly comparable. Low latency doesn’t necessarily mean fast downloads; check file transfer speeds separately.

Connection tests

Real connection latency

Real connection latency usually measures the response time for a request made through a node to a test URL. It’s more representative of everyday browsing than a port-only check. An unreachable test URL, DNS resolution failure, or failed node connection can all cause a timeout. For a fair comparison, use the same test URL and method at roughly the same time.

Subscriptions and nodes

For a single node, use the clipboard or QR code import option. For a subscription URL that supports bulk updates, add it to a subscription group instead.

Configuration sources

Subscription

A subscription lets a client fetch multiple configurations from a URL. Adding the URL saves the source; updating it fetches the latest content. If an update completes but no nodes appear, check that you selected the right group, then see whether the client reported a failed request or an unrecognized response format. Subscription URLs may contain access credentials, so don’t include them in public screenshots.

See how to add and update a subscription →
Connection profiles

Node

A node usually means one connection profile in a client’s list, containing a server address, port, protocol, authentication, and transport settings. The label is just a display name; renaming a node doesn’t change how it connects. Entries with the same name may come from different groups, so check the source before editing or deleting one.

Managing sources

Subscription group

Subscription groups organize subscriptions and their imported nodes by source. Updating a group usually refreshes only that source; it doesn’t switch the active connection. If an old node disappears from the list, switch groups to check whether it’s just filtered out, then compare the entries before and after the update.

Routing and DNS

First ask which resolver handles the domain, then which outbound handles the connection. These steps are related, but changing one doesn’t necessarily change the other.

Match criteria

Routing rule

Routing rules match traffic by criteria such as domain, destination IP, or port, then send matching traffic to a specified outbound. The core usually checks rules in order, and the first match determines where traffic goes. If a specific rule doesn’t take effect, check whether it appears after a broader rule that matches first.

Rule data

GeoIP

In routing configurations, GeoIP usually refers to tagged IP range data used to match destination IPs. These classifications come from the data set; they aren’t real-time location lookups and don’t match by domain suffix. If the destination is a domain, whether it’s resolved before matching against an IP depends on the core’s routing policy.

Rule data

GeoSite

GeoSite is a collection of domains organized by tags for use in routing or DNS rules. The current data file determines which domains each tag covers; don’t infer the full list from the tag name alone. If a particular domain doesn’t match as expected, check whether it’s in the collection, then review the rule order.

See what GeoIP matches →
Outbound selection

Split tunneling

Split tunneling routes different requests through different outbounds according to rules—for example, sending local network traffic through a direct outbound. It doesn’t change the server’s configuration. To troubleshoot a destination, check both whether the app handed its traffic to the client and which rule the client applied to that traffic.

Domain mapping

FakeDNS

FakeDNS returns a synthetic IP for a domain and stores the mapping between that IP and the original domain in the core. When an app connects to that address, the core can use the mapping to recover the domain and apply domain-based rules. The synthetic address isn’t the website’s real IP, so it shouldn’t be used to test a direct connection to the server.

Resolution path

DNS leak

A DNS leak occurs when domain lookups take an unexpected route—for example, when queries still go to a resolver provided by the local network while web traffic uses a proxy. To investigate, first identify which resolver should handle the queries, then check the browser’s, system’s, and client’s DNS settings separately. A change in the web traffic’s exit IP alone doesn’t show where DNS queries went.

See how DNS routing works →

Encryption and obfuscation

This section covers the security mechanisms and handshake fields used to establish connections. They’re separate from the node address and proxy protocol.

Connection security

TLS

TLS encrypts connections and typically uses certificates to verify the server’s identity. Enabling TLS in a client doesn’t change the node’s proxy protocol. If the log reports an expired certificate or a name mismatch, check the certificate’s validity, your system clock, and the server name you entered. Don’t disable certificate verification just to suppress the error.

Connection security

REALITY

REALITY is a connection security mechanism provided by Xray. It’s often paired with VLESS, but isn’t another name for VLESS. The client must recognize the relevant security fields and use a server name and authentication parameters that match the server. If those options disappear after import, check whether your client and core support the configuration.

Back to the VLESS entry →
Handshake fields

SNI

SNI (Server Name Indication) is sent during the TLS handshake so the server can select the right certificate and configuration. In a client, it may be labeled SNI or Server Name, and it doesn’t have to match the server address used to connect. It’s also different from the WebSocket Host field, which belongs to the transport request.