![xshell 5 slow to open host xshell 5 slow to open host](https://windows-cdn.softpedia.com/screenshots/Xshell-Free_23.png)
When I just do an `ssh -vvv I get this: OpenSSH_7.4p1, OpenSSL 1.0.2k-fips ĭebug1: Reading configuration data /etc/ssh/ssh_configĭebug1: /etc/ssh/ssh_config line 58: Applying options for *ĭebug2: resolving "" port 22ĭebug1: Connecting to port 22.ĭebug1: identity file /home/kyleh/.ssh/id_rsa type 1ĭebug1: key_load_public: No such file or directoryĭebug1: identity file /home/kyleh/.ssh/id_rsa-cert type -1ĭebug1: identity file /home/kyleh/.ssh/id_dsa type -1ĭebug1: identity file /home/kyleh/.ssh/id_dsa-cert type -1ĭebug1: identity file /home/kyleh/.ssh/id_ecdsa type -1ĭebug1: identity file /home/kyleh/.ssh/id_ecdsa-cert type -1ĭebug1: identity file /home/kyleh/.ssh/id_ed25519 type -1ĭebug1: identity file /home/kyleh/.ssh/id_ed25519-cert type -1ĭebug1: Enabling compatibility mode for protocol 2.0ĭebug1: Local version string SSH-2.0-OpenSSH_7.4ĭebug1: Remote protocol version 2.0, remote software version conker_1.1.31-8625750 app-131ĭebug1: no match: conker_1.1.31-8625750 app-131ĭebug1: Authenticating to :22 as 'git'ĭebug2: KEX algorithms: host key algorithms: ssh-ed25519ĭebug2: ciphers ctos: ciphers stoc: MACs ctos: MACs stoc: compression ctos: compression stoc: languages ctos:ĭebug2: KEX algorithms: host key algorithms: ssh-dss,ssh-rsaĭebug2: ciphers ctos: ciphers stoc: MACs ctos: MACs stoc: compression ctos: noneĭebug1: kex: algorithm: kex: host key algorithm: (no match)
![xshell 5 slow to open host xshell 5 slow to open host](https://embed-ssl.wistia.com/deliveries/7703349e5643aa0f5798ac80677e12194c181c12.jpg)
I place it in bitbucket and it accepts the key no problem, but when I test it out: `Unable to negotiate with 18.205.93.2 port 22: no matching host key type found.
![xshell 5 slow to open host xshell 5 slow to open host](http://blog.netsarang.com/wp-content/uploads/2015/12/85.png)
The command to generate the key is: ssh-keygen -t rsa
#XSHELL 5 SLOW TO OPEN HOST HOW TO#
I think it has something to do with how the key is being generated and the cipher used, but it is unclear to me how to fix it. I am unable to set up a ssh key between my machine and bitbucket.