-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
The remote SSH session has a minimal PATH that doesn't include ~/.cargo/bin.
Fix: add to ~/.bashrc or ~/.zshrc on the remote host (outside any if [ -z "$PS1" ] interactive-only guard):
export PATH="$HOME/.cargo/bin:$PATH"Or specify the full path explicitly:
etr --server-path /home/user/.cargo/bin/etrs user@hostetr's bootstrap SSH connection runs non-interactively — it can't prompt for a password.
Fix: set up passwordless SSH with a key pair:
ssh-keygen -t ed25519
ssh-copy-id user@hostCheck the server log on the remote host:
cat ~/.local/state/etr/etrs.logCommon causes:
- The remote shell (
$SHELL) exits immediately due to a broken.bashrc/.zshrc - PTY allocation failed (rare; try on a fresh server account)
Verbose logs go to a file during a live session to avoid corrupting the terminal display.
tail -f ~/.local/state/etr/etr.logThe log path is printed to stderr before the session starts.
- Wait up to 15 seconds — the client reconnects on heartbeat timeout, not immediately
- Check that UDP traffic is allowed between client and server (QUIC runs over UDP; some networks block non-TCP)
- The server keeps state for 30 minutes; if more than 30 minutes elapsed, the session is gone
QUIC runs over UDP. If your network blocks outbound UDP on high ports, etr cannot connect. There is no TCP fallback. Options:
- Ask your network admin to allow UDP on high ports
- Use a VPN that permits UDP
etr and etrs must be the same version. Ensure both are up to date:
etr --version
ssh user@host etrs --versionThe server log is at ~/.local/state/etr/etrs.log on the remote host:
ssh user@host 'tail -50 ~/.local/state/etr/etrs.log'Run etrs -vvv manually to see full stream traces during debugging:
ssh user@host etrs -vvvThen connect with etr -vvv user@host in another terminal.