Unable to connect to SSH host

[ekool]

I have a host I am unable to add. No matter what type of auth or settings I choose, I get this error:

wave> error, ssh cannot connect to client: ssh: handshake failed: remote host identification has changed

Connecting to this host via SSH via regular terminal works fine. No other error is given. (latest Mac client installed via homebrew).

[zerorendan]

same here

[FrankSchoene]

the same

[joergmschulz]

Please use the thumbs-up icon for the first post if you can't contribute anything but a me-too. Thanks! This might bost the probability we get an answer

[oneirocosm]

Unfortunate to see this is still happening. Since we are using the golang ssh/knownhosts library, there have been some cases where our parsing of knownhosts is incorrect. Unfortunately, I haven't been able to reproduce it myself, but it's widespread enough that there must be a straightforward way to reproduce it. To help narrow this down:

• Do any of you have particular keywords in your ~/.ssh/config file that are related to parsing known hosts?
• Also, what does your ~/.ssh/known_hosts look like? Are there multiple publickeys per host listed? Are the keys being hashed in a specific way?

In an absolute worst case scenario, you could temporarily get around the issue by deleting the host from your known_hosts file and add it again while connecting with wave. I don't think this is a satisfactory solution, so I'll be looking for a better system on our end.

[zerorendan]

Unfortunate to see this is still happening. Since we are using the golang ssh/knownhosts library, there have been some cases where our parsing of knownhosts is incorrect. Unfortunately, I haven't been able to reproduce it myself, but it's widespread enough that there must be a straightforward way to reproduce it. To help narrow this down:

• Do any of you have particular keywords in your ~/.ssh/config file that are related to parsing known hosts?
• Also, what does your ~/.ssh/known_hosts look like? Are there multiple publickeys per host listed? Are the keys being hashed in a specific way?

In an absolute worst case scenario, you could temporarily get around the issue by deleting the host from your known_hosts file and add it again while connecting with wave. I don't think this is a satisfactory solution, so I'll be looking for a better system on our end.

Yes and the known_hosts, yes it has multiple publickeys per host listed, example 192.168.86.20 ssh-ed25519 and 192.168.86.20 ecdsa-sha2-nistp256 and a few more for 192.168.86.20 ssh-ed25519

[oneirocosm]

In that case, there's a chance it's related to this issue: https://github.com/golang/go/issues/36126 I don't see this being resolved on their end very quickly, so I'll see if I can find a workaround.

[vinowan]

I have a similar problem

this is my error

[Mathieudewet]

For me removing keys with ssh-keygens -R on ip or hostname before to retry worked.

[Snowflake-Pink]

https://github.com/wavetermdev/waveterm/releases/tag/v0.11.0-beta.1

0.10.4 release still doesn't work well.

But I updated to 0.11.0-beta.1 and ssh connection works.