VLESS
Complete example: vless_over_tls.yaml. Adapt addresses and secrets before deployment.
The field sketches below contain placeholders, not runnable values. Use a complete example when configuring a deployment.
Server
Section titled “Server”protocol: type: vless user_id: string # UUID udp_enabled: true # Default: true (enables XUDP) fallback: string? # Optional fallback destination for failed auth (e.g., "127.0.0.1:80")Client
Section titled “Client”protocol: type: vless user_id: string h2mux: # Optional multiplexing max_connections: 4 min_streams: 4 max_streams: 0 padding: falseRelated settings
Section titled “Related settings”- H2MUX describes client connection pooling and multiplexing fields.
- Vision describes encryption-disabled VLESS over TLS or REALITY.
- VLESS Encryption describes native client
encryption, serverdecryption, protocol-levelvision, and serverencryption_limits.