Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I used to connect to my server without any problem using ssh on Ubuntu with this command:

ssh username@server-ip

I can no longer do it now I've changed my location (same PC).

whene I run the same command using the -v parameter, it outputs me this:

OpenSSH_6.0p1 Debian-3ubuntu1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to [] port 22.
debug1: Connection established.
debug1: identity file /home/riless/.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/riless/.ssh/id_rsa-cert type -1
debug1: identity file /home/riless/.ssh/id_dsa type -1
debug1: identity file /home/riless/.ssh/id_dsa-cert type -1
debug1: identity file /home/riless/.ssh/id_ecdsa type -1
debug1: identity file /home/riless/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.5p1 Debian-6+squeeze3
debug1: match: OpenSSH_5.5p1 Debian-6+squeeze3 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.0p1 Debian-3ubuntu1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP

and then after a while:

Connection closed by

what is the problem, and how can I solve it ?

EDIT: ps: it works on PuTTY, but not with OpenSSH

share|improve this question
The server you're opening a session with, have you configured it in the past to only accept requests from specific IPs? – Colyn1337 Sep 5 '13 at 13:42
and do you have physical access now? – Achu Sep 5 '13 at 14:05
@Colyn1337: not configured for that. – Ghilas BELHADJ Sep 5 '13 at 14:14
@Achu: No, only remote access – Ghilas BELHADJ Sep 5 '13 at 14:14
This looks to me like a server-side problem. Have you checked the server logs? – Andrea Corbellini Sep 5 '13 at 14:43

Try adding -c aes128-ctr to the command line, and/or disabling ECDSA keys. If this helps, you may be bitten by this bug.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.