V2-RAY.online
Xray transports: XHTTP, WebSocket, and TCP
The transport determines how Xray carries VLESS data. XHTTP uses HTTP mechanisms, WebSocket uses an HTTP/1.1 Upgrade, and TCP carries a direct stream; TLS and REALITY are separate security settings.
Updated: 2026-08-23
XHTTP
XHTTP supports multiple modes and can work with TLS or REALITY. Mode, path, domain, and server behavior must match the client. Auto mode lets the core choose behavior from the remaining configuration and may change across releases.
Regular Xray Mux is not the same as XHTTP internal connection management. Manual tuning without measurement can hurt long downloads or increase connection churn.
WebSocket
WebSocket starts as an HTTP/1.1 Upgrade and is often placed behind Nginx or Caddy. The reverse proxy terminates public TLS and forwards the configured path to a local Xray inbound.
TCP and REALITY
A direct TCP profile has no HTTP path. REALITY clients require the correct SNI, public key, short ID, and fingerprint. A successful handshake does not prove that VLESS authorization, DNS, and outbound routing work.
Profile selection
- Use complete profiles from the subscription.
- Refresh both the client and subscription before diagnosis.
- Compare profiles on the same network.
- Do not enable allowInsecure permanently.
- For long-session failures, inspect proxy limits, MTU, and packet loss as well as Xray.
Documentation
See the official XHTTP and WebSocket documentation. Test new core releases on a canary node before a fleet rollout.
Frequently asked questions
Which transport is best?
There is no universal choice. It depends on the client, network, reverse proxy, and route.
Are TLS and REALITY transports?
No. They are connection-security layers used with a network transport.