unable to ssh into raspberry pi anymore

[Fransiefrans]

Hi all,

I have Domoticz (domotica system) running on my raspberry pi 2B.
I can't ssh into my raspberry pi anymore. I tried with different programs without any succes.
When I try to connect from inside or outside my network to the raspberry pi i'm asked to insert my password then it connects only for 1 second and then it disconnects again whitout any error.

I put a ssh file to the boot folder on the sd card. this changed nothing.

I was able to get e debug log from JuiceSSH (app on android phone) but I can't find anything in it.
Maybe somebody can help me out with this issue, this would be greatly appreciated!

04-08-2020 22:54: Got a URL: ssh://0b44bcaa-ad1c-4024-a412-0cca284f0243
04-08-2020 22:54: Building TransportChain[2010] with 1 connections chained
04-08-2020 22:54: Building chain member 0
04-08-2020 22:54: Connecting SSH Session
04-08-2020 22:54: ssh_connect: libssh 0.9.3 (c) 2003-2019 Aris Adamantiadis, Andreas Schneider and libssh contributors. Distributed under the LGPL, please refer to COPYING file for information about your rights, using threading threads_pthread
04-08-2020 22:54: ssh_socket_connect: Nonblocking connection socket: 76
04-08-2020 22:54: ssh_connect: Socket connecting, now waiting for the callbacks to work
04-08-2020 22:54: socket_callback_connected: Socket connection callback: 1 (0)
04-08-2020 22:54: ssh_client_connection_callback: SSH server banner: SSH-2.0-OpenSSH_7.9p1 Raspbian-10
04-08-2020 22:54: ssh_analyze_banner: Analyzing banner: SSH-2.0-OpenSSH_7.9p1 Raspbian-10
04-08-2020 22:54: ssh_analyze_banner: We are talking to an OpenSSH client version: 7.9 (70900)
04-08-2020 22:54: ssh_known_hosts_read_entries: Failed to open the known_hosts file '/data/.ssh/known_hosts': No such file or directory
04-08-2020 22:54: ssh_known_hosts_read_entries: Failed to open the known_hosts file '/etc/ssh/ssh_known_hosts': No such file or directory
04-08-2020 22:54: ssh_kex_select_methods: Negotiated curve25519-sha256,ssh-ed25519,aes256-gcm@openssh.com,aes256-gcm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-256-etm@openssh.com,zlib@openssh.com,zlib@openssh.com,,
04-08-2020 22:54: ssh_init_rekey_state: Set rekey after 4294967296 blocks
04-08-2020 22:54: ssh_init_rekey_state: Set rekey after 4294967296 blocks
04-08-2020 22:54: ssh_packet_client_curve25519_reply: SSH_MSG_NEWKEYS sent
04-08-2020 22:54: ssh_packet_newkeys: Received SSH_MSG_NEWKEYS
04-08-2020 22:54: ssh_packet_newkeys: Signature verified and valid
04-08-2020 22:54: connect: Connected successfully to 192.168.1.11
04-08-2020 22:54: connect: Got host key SHA256:PnIZaGku0f9WLm4CVeVtcXwqkVjf8NeFFmVhvltSyII
04-08-2020 22:54: ssh_packet_userauth_failure: Access denied for 'none'. Authentication that can continue: publickey,password
04-08-2020 22:54: ssh_packet_userauth_failure: Access denied for 'none'. Authentication that can continue: publickey,password
04-08-2020 22:54: Received SSH_AUTH_PARTIAL for private key authentication
04-08-2020 22:54: Received SSH_AUTH_SUCCESS for password authentication
04-08-2020 22:54: channel_open: Creating a channel 43 with 64000 window and 32768 max packet
04-08-2020 22:54: ssh_packet_global_request: Received SSH_MSG_GLOBAL_REQUEST packet
04-08-2020 22:54: ssh_packet_global_request: UNKNOWN SSH_MSG_GLOBAL_REQUEST hostkeys-00@openssh.com, want_reply = 0
04-08-2020 22:54: ssh_packet_global_request: Invalid SSH_MSG_GLOBAL_REQUEST packet
04-08-2020 22:54: ssh_packet_channel_open_conf: Received a CHANNEL_OPEN_CONFIRMATION for channel 43:0
04-08-2020 22:54: ssh_packet_channel_open_conf: Remote window : 0, maxpacket : 32768
04-08-2020 22:54: channel_request: Channel request pty-req success
04-08-2020 22:54: channel_rcv_change_window: Adding 2097152 bytes to channel (43:0) (from 0 bytes)
04-08-2020 22:54: channel_request: Channel request shell success
04-08-2020 22:54: ServiceRequest: Registering a new transport chain
04-08-2020 22:54: Starting the connection manager service
04-08-2020 22:54: Creating ConnectionManager Service
04-08-2020 22:54: Received start command
04-08-2020 22:54: Creating Terminal Session
04-08-2020 22:54: Setting backspace mode to default (^?)
04-08-2020 22:54: Setting font to embedded monospace font
04-08-2020 22:54: Transport chain 2010 is now attached
04-08-2020 22:54: Bound to ConnectionManager service and processing recent ServiceRequests
04-08-2020 22:54: Bound to ConnectionManager to process pending requests
04-08-2020 22:54: Processing 1 REGISTERS.
04-08-2020 22:54: Using transport chain 2010 to prevent ConnectionManager from being killed
04-08-2020 22:54: Processing 0 DROPS.
04-08-2020 22:54: Processing 0 GETS.
04-08-2020 22:54: Processing 0 QUERIES.
04-08-2020 22:54: Unbinding from ConnectionManager
04-08-2020 22:54: Setting font to embedded monospace font
04-08-2020 22:54: Resizing terminal to COLUMNS:(98)98 LINES:(90)90 for a 1080x2094px terminal size @ font size 8 with 11.0x23.0px characters
04-08-2020 22:54: Resizing terminal to COLUMNS:(98)98 LINES:(57)57 for a 1080x1318px terminal size @ font size 8 with 11.0x23.0px characters
04-08-2020 22:54: Acquiring a wakelock for ConnectionManagerService
04-08-2020 22:54: Acquiring a wifilock for ConnectionManagerService
04-08-2020 22:54: Transport chain 2010 is now unattached
04-08-2020 22:54: Destroying ConnectionManager Service
04-08-2020 22:54: Releasing wakelock for ConnectionManagerService
04-08-2020 22:54: Releasing wifilock for ConnectionManagerService
04-08-2020 22:54: Shutting down ConnectionManagerService poller

[jbudd]

Are you specifying that you want to connect as user "pi"?
I'm not familiar with juice ssh but when I connect with Termux I have to type ssh pi@<ip address> not just ssh <ip address>

[Fransiefrans]

Yes I use pi to connect (pi@<ip address> ).
I have been connecting and using juice ssh/putty/other ssh programs for a long time on this raspberry pi so I don't know what changed that I can't connect anymore.

[DougieLawson]

Pull the power from your RPi and reboot it. (Doing it once in a blue moon when it's, most likely, idle isn't a big risk.)
Pull the power from your home router and reboot it.

Then re-test.