Transport
TransportConfig — wire protocols and socket options
Transport settings wrap proxy protocols on inbounds and outbounds via transport: { ... }.
Root message: TransportConfig in protos/proto/vx/transport/transport.proto.
TransportConfig
| Field | Description |
|---|---|
socket | SocketConfig — marks, TFO, bind, buffers |
tcp, kcp, websocket, http, grpc, httpupgrade, splithttp | Wire protocol (oneof) |
tls, reality | Security layer (oneof); see Security |
transportProtocol, securityProtocol | Any escape hatch for extended types |
Only one protocol and one security field should be set per config.
Example (VLESS + WebSocket + TLS)
{
"tag": "vless-ws",
"ports": [443],
"transport": {
"websocket": { "path": "/ws", "host": "example.com" },
"tls": {
"serverName": "example.com",
"certificates": [
{ "certificateFilepath": "/etc/vx/cert.pem", "keyFilepath": "/etc/vx/key.pem" }
]
}
},
"protocol": {
"@type": "type.googleapis.com/vx.proxy.vless.VlessServerConfig",
"users": [{ "id": "uuid" }]
}
}Wire protocols
Multi-inbound transport matrix
On MultiProxyInboundConfig, transport protocols are selected per ALPN/SNI/path in transportProtocols[] instead of a single TransportConfig. Security blocks work the same way in securityConfigs[]. See Inbounds.