X Timed out while waiting for handshake

[kvgary]

Version: 1.0.176 Platform: macOS arm64 21.4.0 Plugins: none Frontend: xterm 我用TABBY ssh 连接ESXI就有这个提示。但是我系统自带的终端用ssh root@ip 去连接是正常的。 X Timed out while waiting for handshake SSH X Remote rejected opening a shell channel: Error: Not connected

[kvgary]

补充一下，用TABBY连接其它的CENTOS是正常的唯独连接ESXI不正确。

[Issues-translate-bot]

The translator bot has detected that this issue body's language is not English, and has translated it automatically.

---

To add, it is normal to use TABBY to connect other CENTOS, but the connection to ESXI is not correct.

[jed-hacker]

I have the same question.

[aylerliu]

我这里也有这个问题 I had the same issue

[zhaolj]

Have the same issue.

[germain-italic]

Same here, can't connect to VMWare Esxi hosts (7.x)

[uwbfortner]

I am also having this issue. Cannot connect to esxi 7

[zhangdp]

same issue

[catid]

Same issue

 SSH  Connecting to esxi.lan
 SSH  Host key fingerprint:
 SSH   ecdsa-sha2-nistp256  W6tuViARqSFoO0bQrVQIxC1dWGdLsvJLLnmWOTLiXDg= 
 X  All configured authentication methods failed

[ghost]

Same issue

[Issues-translate-bot]

The translator bot has detected that this issue body's language is not English, and has translated it automatically.

---

Same issue

[godsyn]

This is still an issue with 1.0.193.

[Asthaknes]

Same problem with version 1.0.196 (Windows x64) and a connection on an ESXi v6.7...

[godsyn]

and: 1.0.196 (Windows x64) and a connection on an ESXi v7.2. Doesn't appear to be ESX version dependent.

[kachunkachunk]

This appears to have something to do with FIPS mode on SSH servers, and thus isn't limited to ESXi (see #5962).

Connecting via the native SSH client in the current Tabby release (1.0.196) seems to encounter this issue due to what I suspect is an older or incompatible library. I haven't tried any more current or nightly releases, though.

As a workaround, you can open a PowerShell profile (or any other local terminal) that is using a different SSH client library, and ssh will probably connect just fine. And as a less secure workaround, you can disable FIPS mode on the SSH server (i.e. /etc/ssh/sshd_config and setting FipsMode = off). Restart the service (on ESXi, the service is upper-case as /etc/init.d/SSH restart), for good measure.

To also confirm, I edited my connection profile to match precisely what the server is configured to accept, to no avail. Had to disable FIPS mode or use another client.

Edit: Enabling verbose logging in the SSH server will show a bit more, but it's not the most accurate/helpful message:

Using arbitrary primes is not allowed in FIPS mode. Falling back to known groups.

[Deltatiger]

I was facing the same timeout issue when connecting using SSH but was working when I open and navigate via other Shells to the same remote machine. I was able to find a workaround from Tabby by change some settings in the Profile's Advanced tab. I changed the Ready Timeout from default (it showed 20000 but probably was not 20000) to something like 30000 and it worked. Not sure if this helps everyone, but it is worth a try.

[Nodewebzsz]

This is still an issue with 1.0.197 on mac

[pilotcy]

same problem

[WindowPlaceBrain]

We also get that problem, it freezes tabby completely.

[kid1612]

I was facing the same timeout issue when connecting using SSH but was working when I open and navigate via other Shells to the same remote machine. I was able to find a workaround from Tabby by change some settings in the Profile's Advanced tab. I changed the Ready Timeout from default (it showed 20000 but probably was not 20000) to something like 30000 and it worked. Not sure if this helps everyone, but it is worth a try.

Thanks, it worked for me. In my case, because DNS (nameserver) doesn't config so Tabby take more than 20s to connect. So I set timeout to 30s then it worked but very slowly. Finally, I fix nameserver and return timeout to 20s (default by Tabby) then it connect right now.

[Neo1102]

This method works for me, and here is the sed command:

[root@localhost:~] sed -i 's/^FipsMode yes/FipsMode no/i' /etc/ssh/sshd_config
[root@localhost:~] /etc/init.d/SSH restart

[swRains]

same problem

[swRains]

can't connect to VMWare Esxi

[pilotcy]

same problem

[Renderer6060]

same here in latest version

[Kado814]

same problem

[Issues-translate-bot]

The translator bot has detected that this issue body's language is not English, and has translated it automatically.

---

same problem

[Hotinosin]

same problem

[rationa1]

same problem

[rationa1]

I was facing the same timeout issue when connecting using SSH but was working when I open and navigate via other Shells to the same remote machine. I was able to find a workaround from Tabby by change some settings in the Profile's Advanced tab. I changed the Ready Timeout from default (it showed 20000 but probably was not 20000) to something like 30000 and it worked. Not sure if this helps everyone, but it is worth a try.

Thanks, it worked for me. In my case, because DNS (nameserver) doesn't config so Tabby take more than 20s to connect. So I set timeout to 30s then it worked but very slowly. Finally, I fix nameserver and return timeout to 20s (default by Tabby) then it connect right now.

set timeout to 30s（30000ms） valid

[Renderer6060]

Didnt solve it for me

[soapmancn]

Didnt solve it for me

Based on this method, set the authentication method to automatic and try again. After I set it up like this, the connection was successful.

[soapmancn]

This method works for me, and here is the sed command: sed -i 's/^FipsMode yes/FipsMode no/i' /etc/ssh/sshd_config

i am esxi 8.0.2 . it work this command: sed -i 's/^fipsmode yes/fipsmode no/i' /etc/ssh/sshd_config

then set the authentication method to automatic.

[tarocjsu]

https://github.com/Eugeny/tabby/issues/6233#issuecomment-1509722236

Problem solved temporary

[csaeum]

Same Problem here