Issue With SSH

Help and Support Help
1

I have three computers. A linux system and iMac and a MacBook.
I can successfully SSH into Volumio with the MacBook but not the iMac or the Linux one.
The issue with the iMac and Linux computers is after typing in the password for gaining ssh access it never returns and just hangs.

Any idea on why the ssh works one on and not the others?

2

Rather a strange problem. On Linux you can run ssh verbosely to get more info:

ssh -v volumio@192.168.x.y

No idea for your iMac.

3

please have a look here https://volumio.github.io/docs/User_Manual/SSH.html

4

I tried it with the -v option as you suggest and the ouput is below (not sure how to interpret it though):
After entering the password it hangs and never returns.

[DaffyDuck]:(999)%ssh -v volumio@volumio.local
OpenSSH_6.9p1, OpenSSL 1.0.1k-fips 8 Jan 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 56: Applying options for *
debug1: Connecting to volumio.local [192.168.1.110] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/jack/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/jack/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/jack/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/jack/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/jack/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/jack/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/jack/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/jack/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Raspbian-5+deb8u4
debug1: match: OpenSSH_6.7p1 Raspbian-5+deb8u4 pat OpenSSH* compat 0x04000000
debug1: Authenticating to volumio.local:22 as 'volumio'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: kex: curve25519-sha256@libssh.org need=64 dh_need=64
debug1: kex: curve25519-sha256@libssh.org need=64 dh_need=64
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:SKjGv3wqJCd3jhjdTrMu7xgmiS6i6LrHMDQZYOmRvHg
debug1: Host 'volumio.local' is known and matches the ECDSA host key.
debug1: Found key in /home/jack/.ssh/known_hosts:5
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/jack/.ssh/id_rsa
debug1: Trying private key: /home/jack/.ssh/id_dsa
debug1: Trying private key: /home/jack/.ssh/id_ecdsa
debug1: Trying private key: /home/jack/.ssh/id_ed25519
debug1: Next authentication method: password
volumio@volumio.local's password: 
debug1: Authentication succeeded (password).
Authenticated to volumio.local ([192.168.1.110]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
5

I suggest you try the same thing from the Macbook (which does work) and compare the output.

You can also get even more verbose output by adding more 'v’s (i.e. “ssh -vvv” instead of “ssh -v”).

6

You could also try to get more info by logging in from your Macbook and start logging ‘sudo journalctl -f’ continuously. Next try sshing from Linux and see if the log throws anything suspicious up.

7

I got it working on all three machines.

With the MacBook, which was the only one that was working, I was connecting with ssh via WiFi while the others were hard wired. When I tried it with the iMac and Linux system using WiFi ssh worked.

I am clueless why it works with WiFi and not while hardwired though. Any ideas why it would behave like this?

Thanks for tips…
Jack