Outbound

Outbound Protocols

Match the account protocol in a node profile.

Updated

The protocol is the account type used by a node. It tells Tunna which credentials matter. Choose the same protocol shown by your provider, then copy the required values exactly.

Choose from the protocols Tunna shows

Tunna exposes VLESS, VMess, Trojan, and Shadowsocks for user-created proxy nodes. If an upstream Xray feature is not shown in the Tunna interface, there is nothing to select or configure for it here.

Choose the protocol your provider named

VLESS

A lightweight Xray account protocol, often paired with TLS or Reality.

Good fit The provider profile says VLESS or includes a VLESS link.

Not ideal You do not have the UUID or the provider's flow/security values.

VMess

An older Xray account protocol with an ID and security choice.

Good fit Your provider still gives VMess nodes.

Not ideal The profile says VLESS, Trojan, or Shadowsocks instead.

Trojan

A password-based proxy protocol commonly used with TLS.

Good fit The provider gives a Trojan link or Trojan server details.

Not ideal You only have a UUID-style VLESS or VMess account.

Shadowsocks

A password and method based proxy protocol.

Good fit Your provider gives a Shadowsocks server, password, and method.

Not ideal The provider expects Reality, VLESS flow, or a protocol-specific UUID.

Fields translated into everyday meaning

Where the server is

Address and Port point to the provider server. The address may be a domain or an IP address.

Address

The server host or IP. Do not put a WebSocket or XHTTP path here.

Port

The listener number from the provider. It is not the same as a routing-rule port.

Who you are to the server

Credentials identify your account. Small differences are enough to make a working server fail.

UUID or ID

The VLESS or VMess account identifier.

Password

The Trojan or Shadowsocks secret.

Method or Security

The protocol-specific encryption choice. Keep the imported value unless the provider says otherwise.

UDP over TCP

For Shadowsocks, this wraps UDP traffic in TCP for servers that expect it. Leave it off unless the provider or server says it is required.

VLESS flow is not a style choice

XTLS-RPRX-Vision and XTLS-RPRX-Vision-UDP443 are server-specific VLESS flow controls. Keep the provider's value. Standard Vision can intercept or reject UDP port 443 and QUIC-style traffic; the UDP443 variant allows that traffic for setups that need it. Changing flow without matching the server can make an otherwise correct node fail.