Skip to content

VPN Kill Switch

koppot edited this page Oct 20, 2026 · 1 revision

VPN & Kill Switch Manager

The VPN & Kill Switch Manager lets you configure an external VPN profile and arm a kill switch that blocks all torrent traffic if the VPN disconnects.

Open it by clicking the VPN button (shield icon) in the toolbar.


VPN profile

The modal has two tabs: Status and Routing & Kill Switch.

Status tab

Shows whether the VPN is connected, the interface name it is using, and the assigned VPN IP address.

Routing & Kill Switch tab

This is where you paste your VPN configuration and manage the kill switch.

Adding a VPN profile

  1. Open the Routing & Kill Switch tab.
  2. Paste your VPN configuration (WireGuard or compatible format) into the Configuration text area.
  3. Save the configuration.

Kill Switch

The Kill Switch blocks all BitTorrent engine traffic the moment the VPN interface goes down, preventing any data from leaking over your regular internet connection.

Arming the Kill Switch

Click the Kill Switch toggle button in the Kill Switch Panel. The button label changes to Armed when active.

State What it does
Armed All torrent traffic is blocked if the VPN disconnects
Disabled Torrent traffic continues normally regardless of VPN state

Caution

When the Kill Switch is armed and the VPN drops, all torrent activity stops immediately — including seeding. Arm it only when you specifically require that behaviour.

Kill Switch triggered

If the Kill Switch has been triggered (VPN disconnected while armed), a visible warning appears in the Status tab. To resume:

  1. Reconnect your VPN.
  2. Verify the VPN status indicator in the modal shows connected.
  3. The engine resumes automatically once the VPN interface is back.

Relationship to the Tailnet

The VPN & Kill Switch Manager manages an external, separately configured VPN (e.g. a WireGuard tunnel to a hosting provider). It is separate from the Tailscale private mesh that connects Nebulae to ADC infrastructure. Both can be active simultaneously.


Next: Tailnet Status

Clone this wiki locally