SSH: Connection closed by remote server

Question

I am trying to ssh login to my remote server. But whenever i try to login through terminal using ssh command:

  ssh root@{ip_address}

I get error:

 Connection closed by {ip_address}

I checked hosts deny and hosts allow, there is nothing in the file. I am not getting why it happening?

It happened when i changed my workstation and key got changed. When i tried ssh login, it asked to add key and i entered yes and then it closed the connection.

Is there any way to get connected with ssh again?

Your help is appreciated.

Thank you.

Edit:

Output of ssh -v -v -v -v root@{ip_address} is

OpenSSH_5.9p1 Debian-5ubuntu1.1, OpenSSL 1.0.1 14 Mar 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to {ip_address} [{ip_address}] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/mona/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /home/mona/.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/mona/.ssh/id_rsa-cert type -1
debug1: identity file /home/mona/.ssh/id_dsa type -1
debug1: identity file /home/mona/.ssh/id_dsa-cert type -1
debug1: identity file /home/mona/.ssh/id_ecdsa type -1
debug1: identity file /home/mona/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.1
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "{ip_address}" from file "/home/mona/.ssh/known_hosts"
debug3: load_hostkeys: loaded 0 keys
debug1: SSH2_MSG_KEXINIT sent
Connection closed by 151.236.220.15

Please send us the output of `ssh -v -v -v -v root@{ip_address}` — Iwan Aucamp, Aug 08 '13 at 08:56
From the man page: `Multiple -v options increase the verbosity. The maximum is 3.` — domih, Oct 22 '19 at 10:21

score 4 · Answer 1 · answered Oct 01 '14 at 09:55

4

Had the same issue but a simple remote server reboot helped.

answered Oct 01 '14 at 09:55

Aistis

2,953
2
28
31

This helped. Probably its enough to restart the ssh service? – zypro Feb 26 '19 at 12:54
I don't know why. Maybe some corrupt SSH server state occurred. – Aistis Apr 23 '19 at 12:50

score 3 · Answer 2 · answered Oct 05 '13 at 06:27

3

Are you sure your server is permitting root logins via SSH? If not, I suggest using a different account with sudo privileges instead of enabling root login - especially if the server's SSH port is accessible from the whole inernet.

answered Oct 05 '13 at 06:27

Kimvais

34,273
14
100
135

good advise for root user -- i implicitly replaced root@ with myuser@, which is what I wanted. I am confused why ssh on client resolves an issue with the server closing the socket. – mobibob Nov 23 '19 at 16:59

score 2 · Answer 3 · answered Jun 13 '18 at 08:13

2

try sudo ssh root@{ip_address}, it works for me.

answered Jun 13 '18 at 08:13

Beatrice Lin

1,308
11
16

2

While this answer doesn't provide any reasoning for why it worked, it actually does solve one potential cause for the error the OP got, and in fact, solved my issue when I ran into this as well: If you attempt to connect via some user account that isn't allowed or doesn't exist, but root is allowed, then this can solve the issue. The more general solution at play is simpler: use a user account that exists and is configured for SSH. – lance.dolan Jan 22 '19 at 20:31
How do I configure account for ssh so that I can connect to it? – zwolin Aug 02 '19 at 15:28

score 1 · Answer 4 · edited Nov 13 '16 at 22:45

I was getting the same "Connection closed by {ip_address}" error on one of my SSH connections. I tried all the usual solutions and nothing worked. Finally I found that the ~/.ssh/authorized_keys file on the host was corrupted. Someone had tried to append a key to the file, but they copied and pasted it with embedded line feeds where each line wrapped at the end. So what should have been one continuous string spanning three lines was actually three separate strings -- one per line. Since the embedded line feed was exactly at the end of the line, it was not apparent from looking at it.

I deleted the offending key and added my own. Then everything worked as expected.

Me too. I had a problem with the client keys. Deleting them helped. — domih, Oct 22 '19 at 10:22

score 0 · Answer 5 · edited Feb 28 '20 at 14:24

0

I myself had same problems while working with cloud9 editor. Mine was cause from high CPU usage. It would get fine after stopping apache connection.

edited Feb 28 '20 at 14:24

Umair Khan

1,343
13
27

answered Feb 28 '20 at 12:55

Batbekh Batmagnai

49
3

score 0 · Answer 6 · answered Apr 03 '20 at 17:07

0

Check the name being used to connect to the ftp site, its either wrong or multiple names are being sent for uthentication.

answered Apr 03 '20 at 17:07

snnpro

121
1

SSH: Connection closed by remote server

6 Answers6

Linked