Skip to content

VLESS

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
proxies:
- name: "vless"
  type: vless
  server: server
  port: 443
  udp: true
  uuid: uuid
  flow: xtls-rprx-vision
  packet-encoding: xudp

  tls: true
  servername: example.com
  alpn:
  - h2
  - http/1.1
  fingerprint: xxxx
  client-fingerprint: chrome
  skip-cert-verify: true
  reality-opts:
    public-key: xxxx
    short-id: xxxx
  encryption: ""

  network: tcp

  smux:
    enabled: false

Note

Meta's xtls-* flow control is effectively equivalent to xtls-*-udp443 in Xray-core. To block UDP traffic on port 443, use the logical rule: AND,((NETWORK,UDP),(DST-PORT,443)),REJECT.

Common fields

TLS fields

uuid

Required, VLESS user ID.

flow

VLESS sub-protocol. Available value: xtls-rprx-vision.

packet-encoding

UDP packet encoding. Empty means raw encoding. Available values: packetaddr (supported by v2ray 5+)/ xudp (supported by xray).

encryption

VLESS encryption client configuration:

encryption: "mlkem768x25519plus.native/xorpub/random.1rtt/0rtt.(padding len).(padding gap).(X25519 Password).(ML-KEM-768 Client)..."

XTLS Vision with native/xorpub can splice. Use only 1-RTT mode, or reuse 0-RTT if the ticket sent by the server has non-zero seconds.

Only one item can be selected before /; after that, at least one base64 item is required and more can be appended indefinitely. Generate values with mihomo generate vless-x25519 and mihomo generate vless-mlkem768, and remove the parentheses when replacing values.

Padding is optional and only applies to 1-RTT to remove handshake length characteristics. The default value on both sides is 100-111-1111.75-0-111.50-0-3333:

  • After the 1-RTT client/server hello, append random padding of 111 to 1111 bytes with 100% probability.

  • Wait a random 0 to 111 milliseconds with 75% probability (probability-from-to).

  • Send random padding of 0 to 3333 bytes again with 50% probability. If the value is 0, no Write() occurs.

  • The server and client can use different padding parameters. Parameters can be appended indefinitely in len/gap order. The first padding must have 100% probability and at least 35 bytes.

network

Transport layer. Supports ws/http/h2/grpc/xhttp. If unset or set to another value, TCP is used.

See Transport configuration.