V2Ray Glossary
First identify which layer a setting belongs to: protocols define how the two sides communicate, the core handles connections, and routing decides which outbound a request uses. Browse the categories below to find unfamiliar options; each glossary card has its own link.
Protocols & transport
When entering connection settings, check the protocol, transport, and connection security options separately. They are not the same field.
- VMess
- VMess is a proxy protocol in the V2Ray ecosystem. Clients and servers establish sessions using parameters such as a user ID. Authentication is sensitive to system time, so if a handshake fails, first check the device's actual clock, then review the user ID and other settings. A correct time zone does not mean the clock is accurate.
- VLESS
- VLESS is a proxy protocol that commonly uses a UUID to identify users. After importing a configuration, check the transport, connection security, and flow-control fields separately. The same protocol name does not mean two configurations use the same handshake. Support for a given option depends on the core in use and its version.
- Trojan
- Trojan is a password-authenticated proxy protocol that typically establishes connections over TLS. A correct password and a successful TLS handshake are separate requirements. If the log reports a certificate name mismatch, check the server name and certificate first instead of repeatedly re-entering the password.
- REALITY
- REALITY is an Xray connection security mechanism that uses a TLS-related handshake; it is not a proxy protocol on the same level as VLESS. In a client, it usually appears under connection security, while the protocol field may still show VLESS. A successful import only means the client read the configuration—it does not prove that the active core can run it.
- Transport
- A transport determines how a proxy protocol's data travels between the client and server. With WebSocket, for example, you may need to check settings such as the path as well as the transport type. Changing the transport on the client alone usually will not make configurations that already differ between the two ends compatible.
Cores & ecosystem
The client handles the interface and configuration management; the core determines whether a configuration can actually run.
- Project V
- Project V is the name associated with V2Ray's origins; V2Ray is its core tool. Project V, V2Ray, and the core names shown in today's clients are not interchangeable terms. When troubleshooting compatibility, check the name and version of the core that is actually running.
- V2Fly
- V2Fly is a community project that continues V2Ray's development and maintains V2Ray core. v2flyNG is an Android GUI client in this core family. When following instructions for an older configuration, check which generation of the core the documentation covers before reusing its fields.
- Xray
- Xray grew out of the V2Ray ecosystem, and its core program is commonly called Xray-core. Some configuration concepts overlap with V2Ray core, but that does not mean features such as REALITY can be used interchangeably between them. When troubleshooting a configuration, check the logs first to confirm which core actually started.
- GUI client
- A GUI client displays server lists, subscription groups, and settings, and manages the running core. Desktop v2rayN and Android clients such as v2rayNG and v2flyNG all belong to this layer. Being able to save a setting in the interface does not mean the core received or applied it successfully.
- Core switching
- Core switching means handing a configuration to another core supported by the client. After switching, check that the protocol, transport, and routing fields are supported, and confirm that the core starts normally. On Android, you may need to choose a client for the core rather than look for a universal switching button in one interface.
Subscriptions & configuration
Whether a subscription updated, whether a server can connect, and how long a connection test took are three separate questions.
- Subscription
- A subscription lets a client retrieve or update a set of connection configurations from a URL. Saving the URL and fetching the list are separate steps, so you usually need to update after adding it. If the update succeeds but no usable servers appear, check the response format and the current group. Subscription URLs may contain credentials, so hide the full URL in screenshots.
- Subscription group
- A subscription group keeps connection configurations from the same source together for easier updates and filtering. If the list is empty, first confirm that you are viewing the same group you just updated, then check whether a filter is enabled. Do not judge the update based only on entries visible in another group.
- Server
- A server entry in the client usually contains an address, port, protocol, and transport settings. The label is only there to help identify it: two entries with the same name might point to different servers or differ in just one setting. Compare the actual fields when troubleshooting rather than relying on the label to spot duplicates.
- Latency
- Latency is the time a specific test takes from start until its measurement condition is met, usually measured in milliseconds. A port probe and a test that accesses a target through a proxy cover different things, so their results are not directly comparable. Lower latency does not mean higher bandwidth; to find the cause of slowness, distinguish connection setup from data transfer.
- Real connection latency
- Real connection latency usually measures how long a request takes to reach a test URL through the selected proxy configuration, according to the client's measurement settings. It is closer to real-world access than a port-only test, but results also depend on the test URL, current network, and measurement method. One failed test does not mean every destination is unreachable; confirm the test conditions match before comparing results.
Routing & split routing
First check whether the request reached the client, then check the split-routing rules and domain resolution. Assess each separately.
- Routing rule
- Routing rules select an outbound for traffic based on conditions such as domain, IP address, or port. With common first-match routing, the first matching rule determines the result, so a broad rule near the top can prevent an exception below it from taking effect. Check both the conditions and whether the target outbound exists.
- Split routing
- Split routing sends different requests along different paths according to matching rules, instead of sending everything through the same outbound. For example, requests to matching local network addresses can go direct while other requests use the default outbound. If app traffic never reaches the core, it cannot match these rules.
- GeoIP
- In routing configurations, GeoIP usually refers to a dataset used to match IP address ranges. It may also include categories such as private addresses; it is not limited to geographic regions. If a request arrives with only a domain, whether it is resolved to an IP for matching depends on the core's domain strategy.
- GeoSite
- GeoSite is a collection of categorized domains that routing rules can reference. Rules match the domains and conditions actually included in the data file, not the language used by a website. Changing the data source or version can also change which domains a category with the same name covers.
- System proxy
- A system proxy is a proxy endpoint provided by the operating system to apps that follow its settings. In v2rayN, selecting “Set system proxy” lets the client configure this endpoint; it does not mean all requests use a proxy outbound. Apps may also have their own proxy settings, so if traffic does not pass through the client, first check how the app reads proxy configuration.
- TUN mode
- TUN mode receives IP packets routed to it by the system through a virtual network interface. Unlike a system proxy, it does not depend on apps actively reading the system proxy settings. Actual coverage also depends on the routing table and exclusions, so the enabled status alone does not prove that all traffic is captured.
- FakeDNS
- FakeDNS returns a temporary virtual address for a domain, allowing the core to recover the original domain from later traffic. This address is a mapping used for identification, not the website's actual public address. If DNS resolution and the subsequent connection do not use the same mapping mechanism, an app may get an address it cannot connect to.
- DNS leak
- A DNS leak occurs when name lookup requests take an unexpected route and reach a resolver the user did not intend to use. A page loading successfully does not prove that DNS resolution and the web connection took the same path. When troubleshooting, check the app's secure DNS, system DNS settings, and the client's DNS rules separately.
Android system behavior
System permissions, app coverage, and background activity have separate settings. Getting one right does not mean the others are ready.
- VpnService
- VpnService is an Android system API that lets an app create a local virtual network interface with the user's permission. The first time VPN mode starts, Android displays a connection request. The VPN icon in the status bar only confirms that the system tunnel is up; it does not verify the remote connection.
- Per-app proxy
- Per-app proxy settings determine which Android apps send traffic through the VPN tunnel created by the client. They control app coverage, not domains; the core can still route an app's requests to different outbounds based on their destination domains. After changing the app list, reconnect and test with the target app.
- Bypass mode
- On a per-app proxy screen, bypass mode usually excludes the selected apps from the VPN tunnel. If the setting is “proxy selected apps only,” selecting apps means the opposite. This also differs from a desktop client's address bypass rules: the former filters by app, while the latter matches request destinations.
- Battery optimization
- Battery optimization is a set of mechanisms used by Android and device manufacturers to limit background app activity. If the connection repeatedly drops only after the screen locks, check whether the client's battery settings restrict background activity; some systems offer an “Unrestricted” option. After changing the setting, retest on the same network so network changes do not muddy the results.