Security
[!CAUTION] No Encryption By Default The VideoToolbox Remote protocol runs over plain TCP. Traffic is NOT encrypted. Do NOT expose the daemon port (default 5555) directly to the public internet.
Token Authentication
The server supports a simple token-based authentication mechanism.
- Server: Start with
--token-file <path>(recommended),--token-env <variable>or--token <secret>. Restrict the token file to the daemon user. - FFmpeg: Run with
-vt_remote_token <secret>. - VA-API / Plex: Set
VTREMOTE_TOKENin the application/container environment. - OBS: Set the encoder’s Authentication Token property.
[!WARNING] This token prevents unauthorized access but does not protect against eavesdropping or man-in-the-middle attacks.
Recommended Secure Setup
If you must run this over an untrusted network (e.g., across the internet), use a secure tunnel.
Option 1: SSH Tunnel (Recommended)
- Bind to localhost: Start the server bound only to loopback.
vtremoted --listen 127.0.0.1:5555 - Create Tunnel: From the client, create an encrypted tunnel.
ssh -N -L 127.0.0.1:5555:127.0.0.1:5555 user@mac-server - Connect: Point FFmpeg to localhost.
ffmpeg ... -vt_remote_host 127.0.0.1:5555 ...
Option 2: VPN / Tailscale
Run both client and server on a private Tailscale network (or WireGuard/OpenVPN). Use the VPN IP addresses for connection. This provides encryption transparently.
For Plex containers, the endpoint must be reachable from the container’s network namespace. A loopback tunnel on the Docker host is reachable through loopback when using Linux host networking; a bridged container needs an explicitly reachable, restricted tunnel endpoint. Keep the token out of published logs and shared configuration.