Unable to SSH

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
ifndefx
Posts: 2
Joined: Wed Sep 25, 2019 2:08 pm

Unable to SSH

Post by ifndefx »

Hi,
I've just installed dietpi on a raspberry pi 3 model b+, and I have used OpenSSH. The installation is completed, however, I'm finding that I'm unable to ssh into it from my pop_os machine :

Code: Select all

▶ ssh -v 192.168.1.102
OpenSSH_7.9p1 Ubuntu-10, OpenSSL 1.1.1b  26 Feb 2019
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.1.102 [192.168.1.102] port 22.
debug1: Connection established.
debug1: identity file /home/matt/.ssh/id_rsa type -1
debug1: identity file /home/matt/.ssh/id_rsa-cert type -1
debug1: identity file /home/matt/.ssh/id_dsa type -1
debug1: identity file /home/matt/.ssh/id_dsa-cert type -1
debug1: identity file /home/matt/.ssh/id_ecdsa type -1
debug1: identity file /home/matt/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/matt/.ssh/id_ed25519 type -1
debug1: identity file /home/matt/.ssh/id_ed25519-cert type -1
debug1: identity file /home/matt/.ssh/id_xmss type -1
debug1: identity file /home/matt/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.9p1 Ubuntu-10
ssh_exchange_identification: read: Connection reset by peer
I'm able to connect to my ubuntu server without any problems.

I've tried :
- adding ssd: ALL to /etc/hosts.allow
- changing from OpenSSL to dropbear (same issue)
- restarting as some had suggested on stackexchange

Is there anything else I need to do ?

User avatar
MichaIng
Site Admin
Posts: 2199
Joined: Sat Nov 18, 2017 6:21 pm

Re: Unable to SSH

Post by MichaIng »

Could you paste the output of:
journalclt -u ssh
journalctl -u dropbear

depending on which server you currently use.

Also probably journalctl -r (general system log, including PAM authentication etc, sorted from newest to oldest entry (-r = reverse)) could give a hint.

I am not sure about the meaning of your client log. It seems to go through SSH client keys, not sure if -1 means that that those do not exist. However it should be user+password authentication by default anyway. Do you authenticate via user+password to your Ubuntu server as well or via key authentication?

Post Reply