Deploy a tunnel per client site
Use this page when you run many client sites and want to push the same Conduit Tunnel to each one from your RMM. Each site runs the conduit-tunnel binary (the v2 Tunnel) as a service. It dials the WYRE relay over WSS and opens no inbound port. The installers are the ones in the Quickstart; this page shows how to wrap them for unattended, repeatable rollout.
What you need per site
Section titled “What you need per site”| Value | Where it comes from |
|---|---|
| Enrollment token | Connections → Tunnels → Add Tunnel in Conduit, in the org for that client. It is identity-only (no capabilities) and valid for up to 1 year. Treat it as a secret. |
RELAY_URL |
Baked in by the Conduit install route. You do not set it. |
| Connectors | Not set on the host. You enable them in Conduit and they are pushed down the tunnel. |
Routing and connector config apply to your org’s current live tunnel, so give each client site its own Conduit org and mint that site’s token there. See One live tunnel, many tunnel rows.
Do not set CAPABILITIES on a Tunnel host. The Tunnel refuses to boot if it is present. See the Reference.
RMM scripts
Section titled “RMM scripts”Both scripts assume your RMM injects the token as the ENROLLMENT_TOKEN environment variable from its secret or custom-field store. Do not paste the token into a script body that the RMM logs.
Run as root (most RMM agents already do):
#!/usr/bin/env bashset -euo pipefail: "${ENROLLMENT_TOKEN:?inject ENROLLMENT_TOKEN from the RMM secret store}"curl -fsSL https://conduit.wyre.ai/get/tunnel.sh | ENROLLMENT_TOKEN="$ENROLLMENT_TOKEN" bashThis downloads the currently supported release, installs a hardened systemd service (conduit-tunnel), and starts it. The token is written to /etc/conduit-tunnel/env with mode 600.
Windows (PowerShell)
Section titled “Windows (PowerShell)”Run as an administrator or SYSTEM:
$ErrorActionPreference = 'Stop'if (-not $env:ENROLLMENT_TOKEN) { throw 'inject ENROLLMENT_TOKEN from the RMM secret store' }& ([scriptblock]::Create((irm https://conduit.wyre.ai/get/tunnel.ps1))) -Token $env:ENROLLMENT_TOKENThis downloads the Authenticode-signed binary, installs it as a Windows service, and starts it. To run the service under a gMSA (needed for SQL Server Windows Integrated Auth), call the upstream installer directly as shown in Quickstart → Windows.
Verify a site is online
Section titled “Verify a site is online”On a Linux host:
journalctl -u conduit-tunnel -n 20 --no-pager | grep 'tunnel registered'You should see tunnel registered (v2, zero capabilities until config push). The site also shows as live under Connections → Tunnels. Then enable connectors from that tunnel’s page.
Upgrade a site
Section titled “Upgrade a site”Run the same RMM script again. The installer stops the service, replaces the binary with the release Conduit currently pins, and restarts it. It rewrites the host’s env file from the token you pass, so keep the token in the RMM secret store. Connector config lives in Conduit and is re-pushed within about a minute.
Verify what you install
Section titled “Verify what you install”The Windows binary is Authenticode-signed (check the publisher is WYRE AI), and each release ships SHA256SUMS for the Linux binaries. See Architecture Context → Image Verification.

