V2Ray Glossary

Look up client settings by name. First distinguish protocols, transports, and security layers, then check subscription updates, routing matches, and latency test results.

Protocols and Transports

A protocol defines how peers exchange proxy data; a transport determines how that data is carried.

VMess

VMess is a proxy protocol in the V2Ray ecosystem. Clients connect to a server using parameters such as a user ID. When configuring a server, choosing VMess is only the first step: check the transport and security layer separately. A device clock that is out of sync can also affect VMess authentication, so check the time if the handshake fails.

VLESS

VLESS is a proxy protocol that configures connection authentication separately from transport security. Seeing VLESS alone doesn't tell you whether the connection uses TLS or REALITY, or which transport it uses. When entering a node manually, use the protocol, transport, and security settings provided by the server; don't reuse settings from another node.

Trojan

Trojan is a password-authenticated proxy protocol commonly used with TLS. The password and TLS server name serve different purposes: the password authenticates the proxy connection, while the server name is used for the TLS handshake and identity verification. If the certificate name is incorrect, check the server name and certificate configuration rather than repeatedly changing the password.

WebSocket

WebSocket is a transport that can carry data for proxy protocols such as VMess and VLESS. Set the path and Host header as specified by the server; don't guess based on the connection address alone. In some deployments, the WebSocket Host and TLS server name may be the same, but they serve different purposes.

Cores and Clients

The client interface manages configurations; the core parses them, establishes connections, and handles traffic.

Xray-core

Xray-core is a proxy core forked from the V2Ray project, with features such as REALITY. v2rayNG uses the Xray core, while v2rayN can use different cores to process configurations. If a link imports but the connection won't start, check whether the selected core recognizes the transport or security fields in the configuration. Successful import only means the client was able to read it.

V2Fly

V2Fly is an open-source community project continuing development of the V2Ray core, and v2flyNG uses a core from this ecosystem. V2Fly and Xray share project roots, but newer features and configuration fields are not necessarily compatible. When migrating a configuration, first check whether the core supports its protocol and transport combination, then see if the routing settings can be reused.

GUI client

v2rayN, v2rayNG, and v2flyNG are GUI clients for importing subscriptions, choosing servers, and running a core. The settings a client displays and the connection methods its core supports are separate matters. When troubleshooting, include both the client name and the core in use; that's more useful than simply saying “V2Ray won't connect.”

Subscriptions and Nodes

Subscription updates, node connections, and latency tests are separate steps. Start by identifying which one is failing.

Subscription

A subscription lets a client fetch and update a set of server configurations from a URL. In v2rayN, you can group different subscription URLs and check each group's update results separately. Saving a URL doesn't mean the configurations have been fetched. If a group is empty, first check whether the update succeeded, then whether the client can parse the response.

Node

A node is usually a connection entry in a server list, containing the server address, port, and protocol-specific parameters. Two nodes can point to the same address yet connect differently because their ports, transports, or authentication settings differ. The label is only for identification; renaming it doesn't change the connection route.

TCPing

TCPing measures the time needed to establish a TCP connection, making it useful for a quick check of whether a server's TCP port is reachable. It doesn't verify proxy authentication or test a complete proxy request. If TCPing returns a result but the app still can't connect, check the security layer, transport settings, and real connection test.

Real connection latency

Real connection latency measures the time taken to send a request to a test address through the selected proxy configuration. It's more representative of an app connection than a TCP port test alone. Results depend on the test address, node route, and current network conditions; they aren't download speeds. To compare nodes, use the same test address and method where possible.

Routing and Traffic Routing

System proxy and TUN determine how traffic enters the client; routing rules determine which outbound handles it.

Traffic routing

Traffic routing sends different connections through different outbounds—for example, choosing direct or proxy access based on the destination. It only applies to traffic that has entered the core. If an app isn't using the client as its entry point, changing routing rules won't affect its connections. When troubleshooting, first check whether the traffic enters the core, then check which rule matches.

Routing rule

A routing rule maps matching criteria to an outbound tag. Criteria can include domains, destination IPs, and ports. Rules are usually checked in order, so an earlier broad rule can prevent a later exception from taking effect. If routing isn't working as expected, check the criteria and rule order, and whether the core sees a domain or an IP address.

GeoIP

GeoIP provides sets of IP address ranges for matching—for example, geoip:private typically matches private and special-purpose ranges defined in the rule data. The exact contents depend on the current data set, so a label alone doesn't guarantee that a particular address will match. When accessing a domain, whether an IP rule can also match depends on DNS resolution and routing policy.

GeoSite

GeoSite provides categorized domain sets for routing rules. Category names and their coverage depend on the data file in use, and different sources may not include the same labels. If a category can't be found after changing data files, check which labels the source supports and which file the client actually loads.

System proxy

A system proxy provides an entry point for apps that follow the system proxy settings. In v2rayN, “Set system proxy automatically” writes the relevant settings, while “Do not change system proxy” leaves them as they are—it doesn't clear an existing proxy. If a browser connects but another app doesn't, first check whether that app uses the system proxy.

TUN mode

TUN mode uses a virtual network interface to receive IP traffic covered by system routes, without relying on each app to read the system proxy settings. The traffic it captures depends on system permissions, routes, and exclusions. If the system proxy works but TUN won't start, check the virtual interface and permissions before switching nodes.

Encryption and Security

Check handshake verification and DNS resolution separately: an encrypted connection doesn't tell you which path DNS queries take.

TLS

TLS encrypts connections and protects their integrity, usually using certificates to verify the server's identity. The client can connect to an IP address, but the server name used for verification must still match the certificate configuration. If a certificate error occurs, check the server name, certificate trust chain, and device clock. Don't treat disabling verification as a standard fix.

REALITY

REALITY is a transport security option provided by Xray-core. It's often paired with VLESS, but isn't itself a proxy protocol. The client needs parameters supplied by the server, such as the public key, server name, and short ID. If the handshake fails after import, check that the core supports this configuration and that the imported fields match the server settings.

FakeDNS

FakeDNS returns a temporary IP address for a domain and stores the mapping in the core. When a subsequent connection passes through a compatible core, it can recover the original domain for routing. The temporary IP isn't the website's actual address, so don't use it to determine where the site is hosted. If the connection doesn't pass through the core, the mapping can't be used to recover the domain.

DNS leak

A DNS leak occurs when domain lookups leave the intended resolution path and reach an unintended resolver. Web traffic and DNS queries can take different paths, so opening a website doesn't prove that DNS is resolving as expected. When troubleshooting, first identify the intended resolver, then check the browser's Secure DNS, system DNS settings, and client DNS settings separately.