Lambdatest SSH tunnel Error while creating ssh connection, over port 22 ssh: handshake failed: ssh: unable to authenticate

Using this command

./LT --user lambdatest@example.com --key SECRET --tunnelName automation-tunnel --load-balanced --mode ssh --verbose

I het the following error

DEBUG	Remote config fetched
DEBUG	Trying over ssh over ws
DEBUG	Trying on port 22
DEBUG	Trying on port 443
DEBUG	Starting sink proxy
INFO	Tunnel binary started on port :9090
DEBUG	WSS connection was successful
DEBUG	SSH connection over port 443 successful
DEBUG	SSH connection over ws successful
DEBUG	SSH connection over port 22 successful
INFO	Using ssh(over_22) :: connection mode
INFO	Launching tunnel
DEBUG	Starting control ws connection at wss://ts.lambdatest.com/monitor
DEBUG	Control ws channel opened
DEBUG	Starting message listener on control connection
DEBUG	Sending tunnel registered message to channels
DEBUG	Tunnel registered message received on control channel
DEBUG	Using 5 ssh connection
DEBUG	controller bus registered
DEBUG	Failed to dial at ts.lambdatest.com:22  err : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
ERROR	Error while creating ssh connection, over port 22 ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	closed ssh connection with port 26463
DEBUG	SSH channel connection error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	Failed to dial at ts.lambdatest.com:22  err : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
ERROR	Error while creating ssh connection, over port 22 ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	Failed to dial at ts.lambdatest.com:22  err : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	SSH channel connection error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
ERROR	Error while creating ssh connection, over port 22 ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	closed ssh connection with port 24331
DEBUG	closed ssh connection with port 21098
DEBUG	SSH channel connection error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	Failed to dial at ts.lambdatest.com:22  err : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
ERROR	Error while creating ssh connection, over port 22 ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	closed ssh connection with port 6982
DEBUG	SSH channel connection error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	Failed to dial at ts.lambdatest.com:22  err : ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
ERROR	Error while creating ssh connection, over port 22 ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
DEBUG	closed ssh connection with port 16948
DEBUG	SSH channel connection error: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
ERROR	Err occurred: ERR::ALL::SSH::FAIL : All SSH connections failed 
ERROR	Aborting
INFO	Tunnel closure requested from server. Exiting

This happens like 9 / 10 times and then suddenly it works until it fails again.

Geo dns gets me connected to this ip if it matters

PING ts-ha-oregon.lambdatestgeo.com (52.36.84.247)

It seems that if I change that to another IP then LT works just fine.

# tail -1 /etc/hosts
3.66.78.89 ts.lambdatest.com

Is there anything wrong with 52.36.84.247 Oregon ?

This seems to be happening during the last 2 days.

Also switching to an ed25519 key seems to be working with Oregon. Did you ditch RSA?

SSH Key exchange algorithms seems to be supporting it

>ssh -v 52.36.84.247 2>&1 | grep kex
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com>