From d9230f517a88be0eb88c9af39f7a4212644c9a3d Mon Sep 17 00:00:00 2001 From: akbash Date: Mon, 6 Jul 2026 18:21:31 +0300 Subject: fix: clarify remote ssh auth failures (#1084) refs #1034 Co-authored-by: akbash-bot <300245827+akbash-bot@users.noreply.github.com> --- docs/next/website/src/content/docs/persistence-remote.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'docs/next/website/src/content') diff --git a/docs/next/website/src/content/docs/persistence-remote.mdx b/docs/next/website/src/content/docs/persistence-remote.mdx index f449e2ff..a365ac88 100644 --- a/docs/next/website/src/content/docs/persistence-remote.mdx +++ b/docs/next/website/src/content/docs/persistence-remote.mdx @@ -69,6 +69,15 @@ Native Windows `herdr --remote` is not part of the Windows beta. From Windows, S By default, `herdr --remote` runs remote setup and the bridge through a temporary SSH config that includes your SSH config first, then adds fallback keepalive settings and a private per-attach control socket for connection reuse. Existing user keepalive settings win. Set `[remote].manage_ssh_config = false` to use plain `ssh` without Herdr's generated config or control socket. +Remote attach uses your normal OpenSSH authentication. If the target uses a passphrase-protected key in a non-interactive shell, script, CI job, or mobile terminal that cannot show the passphrase prompt, load the key into ssh-agent first: + +```bash +ssh-add +herdr --remote workbox +``` + +For any remote authentication failure, verify plain SSH access first with `ssh workbox`, then run `herdr --remote workbox` again. + By default, remote attach uses the normal restart/stop flow if it needs to replace or restart a running remote server. To opt into experimental live handoff for a supported running remote server, pass `--handoff`: ```bash -- cgit v1.2.3