VX DocsInbounds
ProxyInboundConfig and MultiProxyInboundConfig
Inbound configuration lives in ServerConfig.inbounds and ServerConfig.multiInbounds.
Schema definition: protos/proto/vx/inbound/inbound.proto.
ProxyInboundConfig
A standard inbound. You can specify multiple proxy protocols, but only one transport protocol and one security protocol may be active.
addressListen address; empty means all interfaces
portSingle port (can be set alongside ports)
portsList of ports to listen on
protocolOne proxy server configuration (VMess, VLESS, Trojan, etc.)
protocolsMultiple protocols on the same listener
Example:
{
"tag": "vmess",
"ports": [10000],
"protocol": {
"@type": "type.googleapis.com/vx.proxy.vmess.VmessServerConfig",
"secureEncryptionOnly": true
}
}Protocol @type values are listed in Proxy protocols. Transport and TLS/REALITY: Transport, Security.
Note: When multiple protocols support UDP, only one protocol's UDP will actually take effect. If Hysteria is present, it is preferred and UDP for other protocols will not be enabled.
MultiProxyInboundConfig
Multi-inbounds can use multiple transport and security configurations simultaneously.
tagInbound tag for routing
addressListen address; empty means all interfaces
portsListen ports
protocolsProxy protocol configurations (same Any type as above)
Security
Each entry in securityConfigs
Only one of tls or reality may be set per security block.
tlsrealitydomainsUse this security configuration for the specified SNI
regularExpressionUse this security configuration for SNI matching this regular expression
alwaysUse this security configuration for all connections
Transport protocol
Each entry in transportProtocols
Only one of websocket, http, grpc, httpupgrade, splithttp, or tcp may be set per transport block.
alpnMatch ALPN
sniMatch connection SNI
pathHTTP/1 path
h2Connection uses HTTP/2
alwaysUse this transport for all connections
Field details are in Transport and Security.