SSH not logging in


#1

When I try to SSH in I get the following error;

Connecting to 192.168.1.100 port 22
Connection established
Remote version string: SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u3
Local version string: SSH-2.0-JSCH-0.1.53
CheckCiphers: chacha20-poly1305@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr,aes256-cbc,aes192-cbc,aes128-cbc,3des-ctr,arcfour,arcfour128,arcfour256
CheckKexes: diffie-hellman-group14-sha1,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521
CheckSignatures: ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
SSH_MSG_KEXINIT sent
SSH_MSG_KEXINIT received
kex: server: curve25519-sha256@libssh.org,ecdh-sha2-nistp521,ecdh-sha2-nistp384,ecdh-sha2-nistp256,diffie-hellman-group-exchange-sha256
kex: server: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
kex: server: chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
kex: server: chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
kex: server: hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128@openssh.com
kex: server: hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128@openssh.com
kex: server: none,zlib@openssh.com
kex: server: none,zlib@openssh.com
kex: server: 
kex: server: 
kex: client: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
kex: client: ssh-ed25519,ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
kex: client: chacha20-poly1305@openssh.com,aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc
kex: client: chacha20-poly1305@openssh.com,aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-ctr,aes192-cbc,aes256-ctr,aes256-cbc
kex: client: hmac-sha2-256,hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
kex: client: hmac-sha2-256,hmac-md5,hmac-sha1,hmac-sha1-96,hmac-md5-96
kex: client: zlib@openssh.com,zlib,none
kex: client: zlib@openssh.com,zlib,none
kex: client: 
kex: client: 
kex result: server->client enc: chacha20-poly1305@openssh.com mac: null compr: zlib@openssh.com
kex result: client->server enc: chacha20-poly1305@openssh.com mac: null compr: zlib@openssh.com
SSH_MSG_KEXDH_INIT sent
expecting SSH_MSG_KEXDH_REPLY
Host '192.168.1.100' is known and matches the Ed25519 host key
SSH_MSG_NEWKEYS sent
SSH_MSG_NEWKEYS received
SSH_MSG_SERVICE_REQUEST sent
SSH_MSG_SERVICE_ACCEPT received
Available server authentication methods: publickey,password
Next authentication method: publickey
Authentication succeeded (publickey).
Caught an exception, leaving main loop due to End of IO Stream Read
Disconnecting from 192.168.1.100 port 22
session is down

#2

You need to provide some context.


#3

Unfortunately we need more/special information from the SSH service on our OSMC system for your current issue.

Please, precisely follow these steps to catch debug information for a specific SSH or SFTP problem

  1. open an SSH connection to the OSMC device with a working SSH client, use credentials user osmc, password osmc
    (the debug information can only be collected for the NEXT SSH-connection after you logged in. So, prepare your environment/clients, so the problem/issue will occur with the next SSH connection to come. For SFTP-transfer problems it means you first have to connect to the OSMC device with your SFTP-client using appropriate credentials and after that activate the sshd debugging on the OSMC device since file transfer will create new/another SSH-session for the transport)

  2. From now, all following commands have to be invoked on the OSMC device you just logged into with a working SSH client using user/password osmc/osmc:
    sudo systemctl stop sshd
    (this stops the sshd father process but your current session process still keeps living)

  3. sudo /usr/sbin/sshd -D -ddd &>my_sshd_debug.txt
    (this starts a debug sshd which is able to accept one session, only)

  4. reproduce the issue like a failed ssh login or failing sftp transfer
    (the called sshd debug program will automatically terminate when the SSH session is closed; otherwise abort it with ctrl+C after the issue occured)

  5. sudo paste-log my_sshd_debug.txt
    (this transfers the debug information and returns a URL)

  6. sudo systemctl restart sshd
    (restarts the sshd service to normal operation, again)

  7. provide the URL from previous step in this forum topic.

Thx for your time investment, we hope to help you, soon.


#4

http://www.jcraft.com/jsch/ I don’t know this Java SSH2 implementation but last known changelog is 2016 for version 0.1.53 but website offers 0.1.54 … without mentioning anything in the changelog of the zip.


#6

sshd isn’t running when I try to login on my Ubuntu laptop


#7

I’m not sure how this is relevant to being unable to ssh into a Pi running OSMC…

But, since you have Ubuntu, what happens if you ssh into the Pi from the command line of the laptop?

It appears that the ssh client you are using is several years out of date.


#8

That’s what didn’t work. When I try to SSH into OSMC from my Ubuntu 18.04 laptop


#9

What do you get from your laptop running this:

ssh -V

This is what I get from Mint:

brian@gelth ~ $ ssh -V
OpenSSH_7.2p2 Ubuntu-4ubuntu2.4, OpenSSL 1.0.2g  1 Mar 2016

#11

@eekfonky Your log shows you’re using a Java-based ssh client solution named “SSH-2.0-JSCH-0.1.53”.
The last update to this stuff is dated 2016 but that is a link to a “0.1.54” version on the website I posted above. For whatever reasons there is no change log for this version 0.1.54.

So, the only interesting thing for us is to see what happens on the OSMC device and is there an issue logged at all or is it a pure ssh client issue on your Ubuntu with this ssh client.

Is there any other machine with a different SSH client you can use to login to the OSMC device and start THERE the sshd logging as described above for the next access try with your Ubuntu?