Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Termix-SSH/Termix/llms.txt

Use this file to discover all available pages before exploring further.

SSH Tunneling in Termix lets you create and manage SSH tunnels that run on the server, not on your local machine. Once configured, tunnels persist on the server and reconnect automatically — freeing you from keeping a terminal window open or relying on your workstation’s network connection.

​
Tunnel types

Termix supports three tunnel forwarding modes, matching the standard SSH forwarding options:

Local

Forward a port on the source host to a port on the endpoint. Traffic arriving at the source port is forwarded to the endpoint.

Remote

Forward a port on the endpoint host back to a port reachable from the source. Useful for exposing local services through a jump server.

Dynamic (SOCKS)

Create a SOCKS5 proxy on the source host. Applications can route traffic through the proxy, which is forwarded over SSH to the endpoint.

​
Reliability features

When a tunnel drops — due to a network interruption, server restart, or SSH timeout — Termix automatically attempts to reconnect. You can configure the maximum number of retries and the interval between attempts per tunnel.
Tunnel status is tracked in real time. The UI shows whether each tunnel is connected, reconnecting, waiting between retries, or has exhausted its retry budget.
Mark a tunnel as autostart so it connects automatically when Termix starts or when the host becomes available.

​
Client-to-server tunnel settings

Desktop clients store tunnel configurations locally on each install. This means your tunnel presets stay private to the device unless you explicitly share them.
1

Configure tunnels on your client

Set up the tunnel configuration locally — source host, endpoint, port mappings, and forwarding mode. These settings live on your current device.
2

Save a preset snapshot to the server

Optionally save the current tunnel configuration as a named preset snapshot on the Termix server. Snapshots can be renamed and deleted from the server at any time.
3

Load the preset on another client

On a different device or install, load a saved preset snapshot from the server to apply the same tunnel configuration without re-entering it manually.
Client-to-server tunnel settings are stored locally per desktop install by default. Preset snapshots are opt-in — they only sync when you explicitly save them to the server.

​
Per-host tunnel management

Each saved host can have multiple independent tunnel configurations. Tunnels are managed separately per host, so you can maintain different forwarding rules for each server without configuration conflicts.
Use preset snapshots when you work from multiple machines and need the same tunnels available on each without manually reconfiguring them.

Build docs developers (and LLMs) love

Get started for freeTalk to us