Configuration terminology index
A practical guide to protocols, cores, subscriptions, routing and networking terms. Use the categories to quickly find settings such as VLESS, GeoSite, TUN and FakeDNS.
Reading order
When a node cannot connect, protocol parameters, the proxy core, routing rules and system network settings belong to different layers. Identify the affected layer first, then check the relevant fields to avoid repeatedly changing unrelated options.
Protocols
The protocol determines how the client and server authenticate and exchange data. When importing a configuration, preserve the complete combination of protocol, transport and security layers rather than copying only the server address and port.
V
An earlier proxy protocol used in the Project V ecosystem. A node configuration typically includes a user ID, server address, port, security options and transport settings.
When editing a VMess node in v2rayN, you may also see compatibility fields such as alterId. Whether they are required depends on the server configuration; do not copy them from another node blindly.
V
A proxy protocol with streamlined authentication that does not provide additional data encryption by itself. It is commonly combined with TLS, REALITY, TCP, WebSocket or gRPC transport and security layers.
When troubleshooting a VLESS connection, check the user ID, flow control, server name, transport type and security options together. Matching the protocol name alone is not enough to establish a connection.
T
A proxy protocol that operates over a TLS channel. Client configurations typically require a server address, port, authentication details, server name and certificate-related options.
If the address is reachable but the protocol connection fails, check the server name, local time, TLS settings and transport type against the server configuration.
R
A transport security solution in the Xray ecosystem, commonly used with VLESS, TCP and REALITY. Clients typically require a public key, short ID, server name and fingerprint.
These fields belong to one handshake configuration. A mismatch in any key value can interrupt the connection. Share links and subscriptions generally include all required parameters.
Cores and ecosystem
Graphical clients handle subscription management, interface actions and system settings, while proxy cores handle protocol connections, routing and DNS. Distinguishing the client from the core makes feature ownership in release notes easier to understand.
P
An open-source technology ecosystem built around proxy protocols, core programs and configuration tools. Concepts such as VMess, routing rules and multiple outbounds developed within this ecosystem.
Project V is not the name of a single graphical client. Clients such as v2rayN and v2rayNG are independent projects that provide interfaces on top of related core capabilities.
V
A community project and core family following the Project V technology line. It provides the underlying capabilities for protocol handling, routing, DNS, inbound connections and outbound connections.
v2flyNG uses a related core to handle connections on Android devices. The client name, core name and node protocol are three distinct concepts and should be identified separately when reading a configuration.
X
A core ecosystem closely associated with V2Ray configurations, supporting VLESS, VMess, Trojan, REALITY, routing and DNS. v2rayN and v2rayNG can use the Xray core to run connection configurations.
Client upgrades and core upgrades are not always the same thing. If a new protocol parameter is not recognized, check support in both the client and the core.
C
The underlying program responsible for protocol handshakes, connection forwarding, DNS queries and route matching. A graphical client generates the configuration, starts the core, then reads its logs and runtime state.
The client interface may still open normally when the core fails to start. Check configuration parsing, port conflicts and permission messages in the logs before importing the subscription again.
Subscriptions and nodes
Subscriptions provide configurations in bulk, a node is one selectable connection record, and a group manages their sources. Updates, filtering and latency tests occur at different stages.
S
A server-provided URL containing a set of configurations. After updating, the client downloads the content, parses the nodes and adds them to the relevant group.
A subscription URL opening successfully does not guarantee that the client can parse its nodes. If the update is empty, check that the link is complete, the content format is supported and group filters have not hidden every record.
N
A server connection profile in the client. It typically includes an address, port, protocol, authentication parameters, transport method and security settings.
A node name is mainly for identification and does not determine connection quality. Choose nodes based on real connection latency, protocol compatibility, target region and actual browsing performance.
G
A container for managing multiple subscription sources and node collections separately. Each group can have its own subscription URL, update method, filters and currently selected node.
If an update succeeds but the server list does not change, confirm that you are viewing the correct group. Also check whether keyword or regular-expression filters excluded the new nodes.
L
The response time measured by establishing an actual protocol connection, making it more representative of everyday connectivity than a basic reachability test. It is affected by the local network, protocol handshake and test target.
A single reading reflects only the conditions at test time. Test several times and consider stability while opening pages and downloading when choosing a node.
Routing and traffic rules
Routing rules are usually checked from top to bottom, and a match is handed to the specified outbound. Review rule order, matching scope and the final outbound name together.
R
A matching rule that determines the outbound direction for traffic based on domains, IPs, ports, protocols or processes. Common results include direct, proxy and block.
Rules generally run in list order. A broad rule placed too early may override more specific rules below it. After editing, reload the configuration and check match results in the logs.
S
A configuration method that sends traffic for different targets to different outbounds. For example, local traffic can use direct, selected domain groups can use proxy, and explicitly rejected targets can use block.
Traffic routing is not a protocol type but a traffic-decision process in the core. The same node may carry different traffic depending on the routing mode.
G
A data set matching IP addresses by geographic region or predefined category. Common rules include geoip:cn and geoip:private.
GeoIP matching occurs after the target IP is obtained, so results depend on the data file and DNS resolution. With outdated data, some newly allocated addresses may not be categorized as expected.
G
A rule set organized by domain category, commonly written as geosite:cn or geosite:geolocation-!cn. It reduces the work of maintaining domain rules one by one.
GeoSite and GeoIP match different objects: the former handles domains, while the latter handles IPs. Both can be used in complex configurations, with their order coordinated with the DNS policy.
Client features
These options determine how the client receives system traffic and when it refreshes configurations. Before enabling multiple capture methods, understand the application coverage of each one.
S
Proxy settings supplied by the operating system for applications to read. When enabled, browsers and desktop programs that support system proxy settings send connections to the client’s local listening port.
Some applications ignore the system proxy and create connections themselves. In that case, check the application’s network options or evaluate whether TUN mode is appropriate.
T
A mode that captures and processes system traffic through a virtual network interface. It can cover applications that ignore system proxy settings and handle more TCP and UDP traffic consistently.
Enabling it usually requires system permissions and may conflict with other virtual networking tools through interface or route overlap. If local devices become unreachable, check rules that bypass LAN and private addresses.
F
A DNS mechanism that temporarily assigns a virtual IP to a domain and restores the original domain information for subsequent connections. It is often used with TUN mode so routing can still classify traffic by domain.
FakeDNS addresses are meaningful only within the client’s internal mapping. If the mapping scope, routing or DNS settings are inconsistent, a domain may resolve successfully while the connection still fails.
A
The client refetches subscription content and refreshes groups at the configured interval. This synchronizes node changes but does not repair an invalid subscription URL or malformed content.
The list after an update is still affected by group filters, sorting and deduplication rules. When important settings change, update manually once and review the client logs.
Networking and system
Proxy configurations rely on the operating system’s networking capabilities. DNS resolution determines the destination address, while TCP and UDP describe different data transport methods.
D
The basic network service that resolves domain names to IP addresses. Clients can configure DNS servers, domain matching rules, query types and the outbound path for DNS traffic.
When a webpage fails to open but direct access by IP works, DNS is one area to check. Also review the system cache, client logs and the browser’s own DNS settings.
D
A situation where domain queries take an unintended path, causing DNS traffic to follow a different routing policy from connection traffic. It is common when system DNS, browser-specific DNS and client DNS operate at the same time.
First determine which layer should handle resolution, then check the system proxy, TUN, DNS outbound and browser settings together. Changing only one DNS address may not resolve an inconsistent path.
T
A transport-layer protocol that provides a reliable, ordered byte stream. Web access, file transfers and most proxy transport combinations use TCP.
TCP in a configuration may refer to the underlying transport method or to a network type matched by routing rules. Interpret the field according to its configuration layer.
U
A datagram-oriented transport-layer protocol used by DNS, real-time communication and some application traffic. It does not provide the same connection acknowledgment and retransmission mechanisms as TCP.
When one application feature fails while ordinary webpages work, check whether the node, core, routing and TUN settings allow UDP. The client’s UDP options must also match the current operating mode.