Look up common concepts including VMess, VLESS, Xray, subscriptions, routing, and DNS. Each explanation maps to an actual client configuration field or operation and does not replace specific server parameters.
Protocols define authentication and data encapsulation, while the transport security layer establishes a protected connection. When importing a configuration, match the protocol, port, transport, and security parameters as a set.
A proxy protocol in the Project V ecosystem that establishes connections with a user identifier and time-based verification. Configurations typically include a server address, port, UUID, and transport. Client settings must match the server, and a significant device clock difference can also affect connectivity.
A lightweight proxy protocol that does not duplicate data encryption within the protocol itself. Transport security is typically provided by an outer TLS or REALITY configuration. With VLESS, also verify related settings such as flow control, server name, public key, and transport type.
A proxy protocol that relies on TLS for secure transport and typically uses a password field for authentication. The client must match the server's domain, port, and transport parameters. Certificate verification failures, an incorrect server name, or an inaccurate system clock can interrupt the handshake.
A transport security solution in the Xray ecosystem, commonly used with VLESS. Connection settings typically include a public key, short ID, fingerprint, and server name. It is not a standalone node protocol; selecting its name alone is not enough without the corresponding VLESS and transport settings.
The graphical client handles the interface and configuration management, while the core handles connections, routing, and resolution. Clients with similar names may use different cores and support different protocol fields.
An open-source technology ecosystem built around V2Ray-related protocols, cores, and tools. It includes configuration formats, proxy protocols, and routing mechanisms, rather than referring to one particular graphical client. Projects may share some concepts, but their feature sets are not identical.
Community projects and a family of cores that continue the V2Ray Core development line. They can execute inbound, outbound, routing, and DNS configurations. Whether a client uses the V2Fly core should be confirmed from the app documentation, core selector, and current runtime logs.
A core implementation with many concepts in common with the V2Ray configuration system. It supports VLESS, REALITY, routing, DNS, and multiple transport settings. The graphical client generates the configuration and starts the core; the core version affects which fields are available.
The software component that handles protocols, routing decisions, DNS queries, and network connections. Graphical clients mainly handle configuration editing, subscription management, and runtime controls. When troubleshooting, distinguish interface errors, configuration-field errors, and core runtime errors.
Subscriptions provide configurations in bulk, while nodes are selectable connection profiles. The system proxy and TUN mode determine which app traffic enters the client, and their coverage differs.
A URL provided by a service provider for a collection of configurations, which may include multiple nodes, groups, and updates. Adding the URL only saves the subscription source; you must still run an update. If updating fails, check the URL, network path, and group selection first.
A server connection profile in a client, typically containing an address, port, protocol, identity fields, and transport method. A node is a configuration unit, not the local client or core. After selecting one, you must also start the client and choose how traffic will be intercepted.
The client changes the operating system's proxy settings so apps that follow the system proxy send requests to a local listening port. Some apps use independent network settings and may bypass it. Restore the system proxy before quitting the client to avoid leaving an inaccessible local-port configuration behind.
A mode that receives device traffic through a virtual network interface, usually covering more traffic than the system proxy. It may require system permissions; check routing rules, DNS, and virtual-address settings. If other networking tools are installed, check for interface and route conflicts.
The time from sending a probe from the local device to receiving a response, usually shown in milliseconds. A basic latency test may check only an address or port and may not complete the protocol handshake. Results vary with the network path, test target, and current load, so check the actual connection too.
The response time measured after connecting with the node's actual protocol and transport settings. It includes more steps than a basic port probe and can help identify handshake parameter errors or connection timeouts. The result still depends on the test target and does not by itself represent sustained transfer speed.
Routing rules select an outbound based on destination characteristics. GeoIP covers address sets, while GeoSite covers domain sets; both require the corresponding data files and valid tags.
Configuration that directs traffic based on domains, addresses, ports, protocols, or processes. When multiple rules exist, their order determines the final match. Put specific rules first, followed by a general outbound for remaining traffic.
A configuration method that sends traffic from different targets or apps to different outbounds. Common destinations include proxy connections, direct connections, and blocked connections. Whether it works depends on DNS results, rule order, and whether the inbound receives enough destination information.
A collection of data organized by address ranges and geographic tags for routing rules to match destination addresses. It matches resolved or directly accessed addresses and does not perform DNS resolution itself. Data files must use formats and tag names supported by the core.
A collection of rule data organized by domain categories, used to match groups of related domains in bulk. Category names are defined by the data file, so the display name alone does not reveal all contents. If a rule does not match, check the tag, domain format, and data update time.
DNS settings determine where domains are queried, while routing settings determine how query requests and resolution results are connected. FakeDNS preserves domain information through mappings, while DoH changes the query transport.
The basic system that resolves domain names to network addresses. V2Ray configurations can specify DNS servers, domain-matching rules, expected address types, and query paths. Client DNS, operating-system DNS, and app-level resolvers may coexist, so troubleshoot layer by layer.
A mechanism that returns reserved addresses to an application first, then lets the core recover the original domain through a mapping. It is commonly used with TUN so routing can still access domain information. Enabling it requires coordinated address-pool, DNS inbound, and routing settings.
A situation where an app's domain queries bypass the configured resolution path and are handled by another network interface or resolver. Check the operating system, browser, client, and TUN settings together. Changing one DNS address may not change every query path.
A DNS resolution method that sends queries over HTTPS, commonly configured as an HTTPS URL. Make sure the resolver's connection path, bootstrap domain resolution, and routing rules form a complete chain. If the resolver itself cannot be reached, subsequent domain queries will fail.
Security parameters span protocol identity, transport encryption, and certificate verification. Correct field names do not guarantee a valid combination; each setting must correspond to the server configuration.
A standard security protocol that encrypts network connections and authenticates the server. The client's server name, certificate verification, and application-layer protocol parameters must match the server configuration. The TLS handshake occurs before application data transfer; if it fails, protocol authentication usually never begins.
A common user identity in VMess and VLESS configurations. It must match the server record and should be managed as a connection credential, not used as a node name or server address. When copying a configuration, preserve every character and hyphen exactly.
Data used in a TLS connection to prove the server's identity and establish a chain of trust. The domain, validity period, and issuer relationship affect whether the client can verify it. For certificate errors, first check the system time, connection domain, and server-name setting.
The process of converting readable data into data that can be recovered only with a key or secure session. Protocols place encryption at different layers: some rely on outer TLS, while others include their own processing. Assess the protocol layer, transport layer, and client core implementation together.