From 69fc3a47d07969c3e29e1fcd6a9b6d818052d47a Mon Sep 17 00:00:00 2001 From: amitsk6 <53637075+amitsk6@users.noreply.github.com> Date: Wed, 20 Nov 2024 19:42:30 +0530 Subject: [PATCH] docs: add ssh host key error to known issues (#5250) * docs: ssh error due to change in host key * style: remove trailing whitespace * Update website/content/docs/api-clients/client-agent.mdx Co-authored-by: Johan Brandhorst-Satzkorn * docs: rephrase message * Update website/content/docs/api-clients/client-agent.mdx Co-authored-by: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> --------- Co-authored-by: Johan Brandhorst-Satzkorn Co-authored-by: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> --- website/content/docs/api-clients/client-agent.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/website/content/docs/api-clients/client-agent.mdx b/website/content/docs/api-clients/client-agent.mdx index b2b6795578..6a31ecfeec 100644 --- a/website/content/docs/api-clients/client-agent.mdx +++ b/website/content/docs/api-clients/client-agent.mdx @@ -510,6 +510,16 @@ $ boundary client-agent pause Follow the troubleshooting steps to understand why the Client Agent is not able to reach the controller. +#### WARNING! Remote host indentification has changed! It is possible that someone is doing something nasty! + +This error arises when you use an alias to connect to an SSH target after the first successful connection using that alias. The issue occurs because Boundary workers generate a new host key on every new SSH connection. You can safely ignore the warning using the `StrictHostKeyChecking=no` command line option: + +```shell-session +$ ssh -o StrictHostKeyChecking=no targetalias.boundary.dev +``` + +You can also remove the existing server host key from the `~/.ssh/known_hosts` file to avoid the error. + ## Conflicting software Some software is known to cause conflicts with the Boundary Client Agent.