Docs Config Outbound Proxies

Outbound Proxies

Every node in the proxies array shares this set of common fields, regardless of protocol. Protocol-specific fields are covered on each protocol's own page.

Field Overview

config.yaml YAML

proxies:
  - name: "ss"
    type: ss
    server: server
    port: 443
    ip-version: ipv4
    udp: true
    interface-name: eth0
    routing-mark: 1234
    tfo: false
    mptcp: false
    dialer-proxy: ss1
    smux:
      enabled: true
      protocol: smux
      max-connections: 4

Basic Fields

nameRequired

The proxy's name — must be unique.

typeRequired

The proxy node's type, e.g. ss/vmess/trojan, etc.

serverRequired

The proxy server's address — can be a domain name or an IP.

portRequired

The proxy server's port.

ip-versionDefault: dual

The IP version used for outbound connections; affects which address is actually used when server is a domain name. Choose dual/ipv4/ipv6/ipv4-prefer/ipv6-prefer — the -prefer suffix means dual-stack resolution with concurrent connections, preferring that version.

udpDefault: false

Whether UDP traffic is allowed through this node. UDP-based protocols like TUIC, as well as the direct/dns types, already have this enabled by default.

interface-nameOptional

The network interface this node's outbound connections are bound to.

routing-markOptional

An extra routing mark applied when this node initiates a connection (Linux only).

tfo / mptcpOptional

Correspond to TCP Fast Open and TCP Multi Path respectively — only apply to the TCP protocol.

dialer-proxyOptional

Routes this node's connection through another node/proxy group, enabling chained proxies — see the dedicated dialer-proxy page for details.

smux Multiplexing

sing-mux multiplexing, only available for protocols using TCP transport.

Field	Description
`enabled`	Whether to enable multiplexing
`protocol`	The multiplexing protocol — choose `smux`/`yamux`/`h2mux`, defaults to `h2mux`
`max-connections`	The maximum number of connections; conflicts with `max-streams`
`min-streams` / `max-streams`	The minimum/maximum number of multiplexed streams per connection before opening a new one; `max-streams` is mutually exclusive with these two
`statistic`	Whether to show the underlying connections separately in the dashboard, for manual disconnection
`only-tcp`	When true, smux settings only apply to TCP — UDP uses the node's default UDP transport
`padding`	Enable padding
`brutal-opts.enabled`	Enable the TCP Brutal congestion control algorithm
`brutal-opts.up` / `down`	Upload/download bandwidth, defaults to Mbps