How do I solve this error: ssh_exchange_identification: Connection closed by remote host

Posted by bernie on Server Fault See other posts from Server Fault or by bernie
Published on 2012-11-13T06:12:58Z Indexed on 2012/11/13 11:06 UTC
Read the original article Hit count: 350

Filed under:
|
data@server01:~$ ssh [email protected] -vvv
OpenSSH_5.5p1 Debian-6, OpenSSL 0.9.8o 01 Jun 2010
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 10.7.4.1 [10.7.4.1] port 22.
debug1: Connection established.
debug3: Not a RSA1 key file /home/data/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /home/data/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/data/.ssh/id_rsa-cert type -1
debug1: identity file /home/data/.ssh/id_dsa type -1
debug1: identity file /home/data/.ssh/id_dsa-cert type -1
ssh_exchange_identification: Connection closed by remote host

© Server Fault or respective owner

Related posts about ssh

Related posts about ssh-keys

  • Is it reasonable to have multiple SSH keys?

    as seen on Super User - Search for 'Super User'
    So far I've created a separate SSH key for each server I need to login to (for each purpose, to be more accurate). I did it out of a sense of security, just like different passwords to different sites. Does having multiple SSH keys actually improve security? All of them are used from the same machine… >>> More

  • Ubuntu Github ssh keys issue

    as seen on Stack Overflow - Search for 'Stack Overflow'
    I followed every step given in this guide: http://help.github.com/linux-key-setup/ When I get to the end I am able to ssh to [email protected], getting the response: PTY allocation request failed on channel 0 Hi AlexBaranosky! You've successfully authenticated, but GitHub does not provide shell… >>> More

  • Problem with shared ssh keys

    as seen on Super User - Search for 'Super User'
    Following the process I've used in other environments (http://www.trilug.org/pipermail/trilug/Week-of-Mon-20080602/054712.html), I've tried setting-up shared keys between my Mac and my CentOS 4 webserver. I've seen the same problem with my older Ubuntu 7.10 workstation trying to connect via keys to… >>> More

  • Invalidating unused ssh keys

    as seen on Server Fault - Search for 'Server Fault'
    I am using one ssh account for all my Subversion users. They send me their public keys and I put them in .ssh/authorized_key of the svn account, then they can check out the code from Subversion using ssh tunnel. So far everything works fine. The problem though is that I want to invalidate keys that… >>> More

  • SSH keys fail for one user

    as seen on Server Fault - Search for 'Server Fault'
    I just set up a new Debian server. I disabled root SSH and password auth, so you've gotta use a key file. For my primary user, everything works exactly as expected. I used ssh-keygen -t dsa and got myself a public and private key. Put one in authorized keys, put the other in a pem file locally. I… >>> More