Troubleshooting
"spawn tmux ENOENT"
tmux isn't installed or isn't in your PATH. Termbridge prints this error but currently keeps running without serving a terminal (#4); press Ctrl+C, install tmux, and start it again.
# macOS
brew install tmux
# Ubuntu/Debian
sudo apt install tmux
"spawn cloudflared ENOENT"
Cloudflare's tunnel client isn't installed or isn't in your PATH. This is only required for tunnel mode; --no-tunnel and Daytona direct mode do not need cloudflared.
# macOS
brew install cloudflared
For Linux, download from cloudflare.com/downloads.
Tunnel won't start
A few things to check (skip this if you're using direct sandbox mode):
- Verify cloudflared works:
cloudflared --version - Make sure you can reach
https://trycloudflare.com - Check if a firewall is blocking outbound connections
If the tunnel fails to start, Termbridge prints the error, stops its server and exits with status 1. It does not fall back to a local-only mode, and the server only listens on 127.0.0.1 by default, so other devices on your network can't reach it either. The tmux sessions created for that run are left running (#4).
To use Termbridge without the Cloudflare tunnel, run it with --no-tunnel --public-url <url> behind your own reverse proxy or tunnel.
"429 Too Many Requests" from trycloudflare
Cloudflare rate limits account-less tunnels. If you see errors like 429 Too Many Requests, try:
- Wait a few minutes and retry
- Make sure no old
cloudflaredprocesses are still running - Use a named tunnel token (recommended for frequent use)
Blank screen or "Unable to load terminals"
This usually means the browser has no valid session cookie, for example because it was opened without redeeming a share link, or the tunnel URL changed:
- Check if the local server is still running
- Look at the browser console for 401/403 errors
- Restart Termbridge to get a fresh URL and QR code
No output in the terminal
The tmux session might not be running:
# Check if sessions exist
tmux ls
If sessions show up but the terminal is blank, try:
- Reloading the page
- Checking that your shell supports
TERM=xterm-256color
QR code scans but page is blank
The QR code contains a one-time token. It works once, and only within 90 seconds of Termbridge starting. A used or expired link returns invalid token.
Solution: Restart Termbridge to generate a new QR code, and scan it right away.
node-pty errors about spawn-helper
Termbridge tries to fix this automatically, but if you see permission errors:
chmod +x node_modules/node-pty/prebuilds/**/spawn-helper
Still stuck?
Open an issue at github.com/inline0/termbridge with:
- Your OS and Node.js version
- The error message
- Steps to reproduce