Outbound
Manage the nodes Tunna can use for proxy traffic.
An outbound is a node Tunna can connect through. It may be a local node you entered yourself or a node delivered by a subscription. The selected outbound is the node used whenever Routing sends traffic to Proxy, and the outbound list is also where Tunna shows live health signals such as latency, recent checks, and node stats.
What Outbound is for
Bring a server into Tunna
Create a node manually, scan a QR code, paste a provider link, or receive one through Resources.
Decide what Proxy means
Tap a node to make it current. Proxy traffic uses that selected node.
Prove a node before routing
Latency checks help sorting, subscription visibility, Top 10 views, and ZAP.
Move credentials deliberately
Share a local node as a link or QR code. Treat the result as private credentials.
Provider profile terms in Outbound
Provider links often use technical Xray or V2Ray-compatible terms. Keep the original values together and change them only when the provider tells you to.
Use these cards as a map of the visible labels in this view. Each card names one field, control, or status item and explains what it is for before you change it or rely on it.
Visible choices
These are controls, states, or measurements in the view. Read them as reference, not as feature claims.
Protocol
VLESS, VMess, Trojan, and Shadowsocks describe the account and credential shape for the node.
Transport
TCP, WebSocket, gRPC, XHTTP, HTTPUpgrade, KCP, and QUIC describe how the connection travels to the server.
Security
TLS, REALITY, server name, uTLS fingerprint, ALPN, and certificate fields describe the handshake expected by the server.
Subscription
A subscription URL lets Tunna refresh a provider-managed group of nodes instead of editing each node by hand.
When the list is empty
Use the empty-state actions to create a manual node, scan a QR code, paste a provider link, or add a subscription. After a subscription fetches successfully, its nodes appear in Outbound as a group.
Manual node edits stay account-shaped
Manual edit views use the same Xray Core terminology as imported profiles, so they stay concise. Copy provider values exactly, keep imported transport and security fields unless you know the server setup, and use Add or Save after the required address, port, and credential fields are valid.
Rules can use different nodes at the same time
Tunna is not limited to one global proxy choice. Routing rules can target Proxy, which means the currently selected node, or a specific proxy node. Use specific-node rules when one destination should use a different provider node from the rest of your traffic.
Local node or subscription
Local node
A single server profile that you own and maintain inside Tunna.
Good fit You manage one server, received one provider link, or need to adjust one profile carefully.
Not ideal Your provider manages many nodes and changes the list over time.
Subscription
A provider profile that can contain many nodes plus usage, expiry, profile, and support data.
Good fit You want Tunna to refresh a provider-managed node list and choose from a group.
Not ideal You do not trust the profile source or only need one fixed server.
Do not guess node details
If a node fails, compare it with the provider profile before changing random fields. Address, port, protocol, transport, security, server name, path, and credentials must belong to the same server setup.