Configuration & Troubleshooting Terms

V2Ray Glossary

When you see VLESS, TUN, or proxied request latency in the interface, first identify which layer it belongs to. Then check the server profile, system settings, or configuration file as appropriate.

Protocols & Transport

Protocol, transport, and security layer are separate server profile settings. Check each one individually when troubleshooting.

VMessProxy protocol
VMess is a proxy protocol in the Project V ecosystem. The client and server use agreed settings to identify users and handle proxy requests. If a profile imports successfully but cannot connect despite the port being reachable, check the user ID, transport, and security settings, and make sure the device clock is accurate.
VLESSProxy protocol
VLESS is a proxy protocol that typically identifies clients with a UUID, but does not encrypt payloads on its own. In practice, it is often paired with a security layer such as TLS or REALITY. Choosing VLESS alone is not enough to establish a connection; the transport and security settings must also match the server.
TrojanTLS-based proxy protocol
Trojan typically authenticates with a password over a TLS connection. The password is a proxy protocol setting, not a certificate setting. If logs stop at the TLS handshake or certificate verification stage, first check the server name, certificate, and system time, then check the password.
REALITYTransport security
REALITY is a security layer supported by Xray and often used with VLESS. It is neither a proxy protocol nor a transport like WebSocket. For a profile marked REALITY, first confirm that the selected core supports it, then check the server name, public key, short ID, and other settings against the profile source.
TransportTransport
Transport determines how proxy protocol data is carried, for example over raw TCP, WebSocket, or gRPC. Two profiles can use the same proxy protocol but different transport settings. If a path or service name does not match, check the relevant transport setting rather than changing the profile name or authentication details.

Cores & Ecosystem

The interface manages settings; the core handles connections. Check their versions and supported features separately.

Project VOpen-source ecosystem
Project V is the open-source network proxy project from which V2Ray originated. Cores and graphical clients maintained by different communities emerged later. So when an article mentions “V2Ray,” it may mean a specific core or the broader ecosystem. Before checking a configuration, confirm which one the documentation refers to.
XrayXray-core
Xray is an independent proxy core developed from the V2Ray ecosystem, with support for features such as REALITY. Seeing a profile in the graphical interface does not mean the active core can use it. To troubleshoot compatibility, check which core is actually running and its version, then verify the features the profile requires.
V2FlyV2Ray community project
V2Fly is a community project continuing V2Ray development. Its V2Ray core reads configuration, accepts inbound connections, and handles outbounds. V2Fly and Xray share a history, but their fields and features evolve independently. Similar-looking configuration formats do not guarantee that the two are interchangeable.
View core configuration reference →

Client Features

App traffic first enters the client, then the core decides how to handle it. Troubleshoot inbound and outbound failures separately.

System proxySystem proxy
The system proxy provides a local proxy endpoint for apps that follow the system proxy settings. Apps that manage their own network connections may ignore these settings, so a working browser does not mean every app uses the same route. If an app keeps trying to connect to a local port after you close the client, check whether the system proxy settings are still enabled.
TUN modeVirtual network interface
TUN mode receives traffic routed by the system through a virtual network interface, rather than waiting for apps to use a proxy explicitly. It may require system authorization, and the traffic it captures depends on routing and exclusion settings. If another virtual network adapter is already in use, the two setups may compete for routes; check which routes each one handles.
Inboundinbounds
An inbound defines how the proxy core accepts connections, such as the address and port for a SOCKS service. If a local app cannot connect, first check that its protocol and port match the inbound. An endpoint intended only for local use usually listens on a loopback address and does not need to bind to every network interface.
Outboundoutbounds
An outbound defines how the core handles a connection: it can forward traffic to a proxy server, connect directly, or block it. Routing rules usually reference a specific outbound by its tag. If an inbound receives a connection but traffic is not sent as expected, compare outboundTag in the rule with the outbound's tag.
View inbound configuration examples →

Routing & DNS

DNS resolution determines how an address is obtained; routing determines which outbound handles the connection. The two are related, but troubleshoot them as separate steps.

Routing Rulesrouting.rules
Routing rules select an outbound based on criteria such as destination domain, IP address, or port. V2Ray and Xray typically check rules in configuration order, applying the first match. If a specific rule never matches, check whether an earlier, broader rule is catching the connection first.
Traffic routingTraffic routing
Traffic routing sends different connections to different outbounds—for example, sending local network traffic directly and routing other connections through another outbound. It only applies to traffic that enters the relevant processing path. If test results are unexpected, first confirm that the traffic reaches the core, then check the routing conditions.
GeoIPgeoip:
GeoIP groups IP ranges by region or address category, allowing a single rule to match a set of addresses. It reflects how an address is categorized in the data file, not necessarily where the server is physically located. If a rule behaves unexpectedly, check both the IP address actually matched and the data file currently in use.
GeoSitegeosite:
GeoSite is a collection of domains organized by category. Routing rules can reference a collection name to match multiple domains. Categories and their coverage depend on the dataset, so a category name alone does not guarantee that it includes a particular domain. To match one domain precisely, add a separate domain rule.
FakeDNSSynthetic IP mapping
FakeDNS returns a synthetic IP address to the app and stores its mapping to the original domain. When the subsequent connection reaches a core that recognizes the mapping, the core can recover the domain and use it to match rules. If the DNS response uses this mechanism but the subsequent connection is not handled by the corresponding core, the app may fail to connect.
DNS leakDNS leak
A DNS leak occurs when queries take an unexpected route and are handled by an unintended resolver. Seeing an unfamiliar resolver on a test page alone does not prove that the configuration is wrong; first determine which resolver you expect to handle the queries. To investigate, check the app's encrypted DNS, operating system settings, and the core's DNS configuration separately.
View routing rules and match order →

Subscriptions & Server Profiles

Updating a subscription, testing a port, and sending a request through a proxy are three separate steps. Passing one does not mean the next has passed.

SubscriptionSubscription
A subscription is a source for clients to import and update multiple server profiles at once, usually via a link. A successful update only means the client retrieved and processed the data; it does not mean every profile can connect. Subscription links may contain access credentials, so hide the full link before sharing screenshots or logs.
Server profileServer profile
A server profile is a client configuration entry containing a proxy endpoint and connection settings, typically including an address, port, protocol, and security options. Its display name helps distinguish entries but does not guarantee that profiles with the same name point to the same service. If duplicates appear after an update, compare their subscription groups and connection settings before deciding which to keep.
TcpingTCP connect test
Tcping uses TCP connection time as a reference for port connectivity. It typically does not check proxy protocol authentication or access a website through the profile. If Tcping succeeds but proxy requests fail, focus on the protocol, security layer, and proxy outbound rather than assuming the profile works based on the port test alone.
Proxied request latencyProxied request latency
Proxied request latency measures the time taken to access a test target through the selected proxy outbound, as recorded by the client. The test address, connection reuse, and target server response can all affect the result; it is not download throughput. To compare profiles, use the same test target and method whenever possible.