Using SBN Tunnel with SBN
This page describes how the SBN Tunnel is configured and used from within SBN.
For an overview of what SBN Tunnel is, how it works alongside a VPN, and how to retrieve your license, see SBN Tunnel.
Walkthrough
The ... button beside Connect via Tunnel on the login form opens the Tunnel Farm Configuration dialog. The button shows only while the checkbox is checked.

SBN stores its tunnel license in tunnels.json, in %LOCALAPPDATA%\IBS\SBN\. SBN 92 (build 08.92.0105 and later) uses the folder described in Settings File Locations.
The Connect via Tunnel checkbox on the SBN logon screen controls whether this login goes through the tunnel. When checked, SBN reaches the server named in the Server field through the tunnel; when unchecked, SBN connects directly -- or through any VPN you already have active. The checkbox is remembered between sessions. The server name you type must match one of the destinations your license is authorized for.
If the tunnel cannot connect while you log in, the login stops and SBN shows the reason. Clear Connect via Tunnel to log in directly instead. Once you are logged in, if the tunnel becomes unavailable SBN keeps working over a direct connection and moves back to the tunnel as soon as it is available again.

Every file shown above must be present in the same folder as SBN.exe for the tunnel to work. The install copies all of them automatically; if any one is missing, SBN cannot connect through the tunnel.

To confirm a connection is actually going through the tunnel, open the Debug window and check SQL Calls. When SBN is using the tunnel, each entry is prefixed with [tunnel:<host>:<port>] showing which tunnel server is in use. Entries prefixed [direct-fallback] mean the tunnel was unavailable and SBN is connecting directly until it returns. If there is no prefix, SBN is connecting to that server directly.
Disabling the tunnel
Clear the Connect via Tunnel checkbox on the login screen. SBN then connects directly, or through any VPN you already have active, and remembers the choice for later logins.
Troubleshooting
Login says "There is no server listening at 127.0.0.1:<port>"
127.0.0.1 is your own PC, and the port is the tunnel's local relay, a free port Windows assigns each time the tunnel connects. The message means the tunnel could not reach the database at that moment, usually because the tunnel server was restarting or the network dropped. Close the message and log in again. If it keeps happening, open the Tunnel dialog and check that a server shows as connected, then contact support with the time it occurred.