Closed Jannomag closed 3 years ago
Does it work if you connect manually from powershell? Can you pass -vvv to get some debugging? (ssh -vvv ...)
Connection through Putty, Kitty and Powershell works fine, also through ssh using Ubuntu 20.10. Output of Powershell using -vvv:
PS C:\Users\***no> ssh ***@homeserver -p 49*** -vvv
OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
debug3: Failed to open file:C:/Users/***no/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug2: resolving "homeserver" port 49***
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to homeserver [192.168.1.26] port 49***.
debug1: Connection established.
debug3: Failed to open file:C:/Users/***no/.ssh/id_rsa error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_rsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_rsa type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_rsa-cert error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_rsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_rsa-cert type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_dsa error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_dsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_dsa type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_dsa-cert error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_dsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_dsa-cert type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_ecdsa error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_ecdsa.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_ecdsa type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_ecdsa-cert error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_ecdsa-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_ecdsa-cert type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_ed25519 error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_ed25519.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_ed25519 type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_ed25519-cert error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_ed25519-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_ed25519-cert type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_xmss error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_xmss.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_xmss type -1
debug3: Failed to open file:C:/Users/***no/.ssh/id_xmss-cert error:2
debug3: Failed to open file:C:/Users/***no/.ssh/id_xmss-cert.pub error:2
debug1: key_load_public: No such file or directory
debug1: identity file C:\\Users\\***no/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_7.7
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9p1 Raspbian-10+deb10u2
debug1: match: OpenSSH_7.9p1 Raspbian-10+deb10u2 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to homeserver:49*** as '***'
debug3: put_host_port: [homeserver]:49***
debug3: hostkeys_foreach: reading file "C:\\Users\\***no/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\***no/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from [homeserver]:49***
debug3: Failed to open file:C:/Users/***no/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:1VIwXEaZlpA/D/WGRpCpKRnYYRC//1wL9GlfqD2FZ4o
debug3: put_host_port: [192.168.1.26]:49***
debug3: put_host_port: [homeserver]:49***
debug3: hostkeys_foreach: reading file "C:\\Users\\***no/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\***no/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from [homeserver]:49***
debug3: Failed to open file:C:/Users/***no/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug3: hostkeys_foreach: reading file "C:\\Users\\***no/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\***no/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from [192.168.1.26]:49***
debug3: Failed to open file:C:/Users/***no/.ssh/known_hosts2 error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug1: Host '[homeserver]:49***' is known and matches the ECDSA host key.
debug1: Found key in C:\\Users\\***no/.ssh/known_hosts:1
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug3: unable to connect to pipe \\\\.\\pipe\\openssh-ssh-agent, error: 2
debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory
debug2: key: C:\\Users\\***no/.ssh/id_rsa (0000000000000000)
debug2: key: C:\\Users\\***no/.ssh/id_dsa (0000000000000000)
debug2: key: C:\\Users\\***no/.ssh/id_ecdsa (0000000000000000)
debug2: key: C:\\Users\\***no/.ssh/id_ed25519 (0000000000000000)
debug2: key: C:\\Users\\***no/.ssh/id_xmss (0000000000000000)
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: C:\\Users\\***no/.ssh/id_rsa
debug3: no such identity: C:\\Users\\***no/.ssh/id_rsa: No such file or directory
debug1: Trying private key: C:\\Users\\***no/.ssh/id_dsa
debug3: no such identity: C:\\Users\\***no/.ssh/id_dsa: No such file or directory
debug1: Trying private key: C:\\Users\\***no/.ssh/id_ecdsa
debug3: no such identity: C:\\Users\\***no/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: C:\\Users\\***no/.ssh/id_ed25519
debug3: no such identity: C:\\Users\\***no/.ssh/id_ed25519: No such file or directory
debug1: Trying private key: C:\\Users\\***no/.ssh/id_xmss
debug3: no such identity: C:\\Users\\***no/.ssh/id_xmss: No such file or directory
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
debug3: failed to open file:C:/dev/tty error:3
debug1: read_passphrase: can't open /dev/tty: No such file or directory
***@homeserver's password:
debug3: send packet: type 50
debug2: we sent a password packet, wait for reply
debug3: receive packet: type 52
debug1: Authentication succeeded (password).
Authenticated to homeserver ([192.168.1.26]:49***).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Requesting no-more-sessions@openssh.com
debug3: send packet: type 80
debug1: Entering interactive session.
debug1: pledge: network
debug1: console supports the ansi parsing
debug3: Successfully set console output code page from:850 to 65001
debug3: Successfully set console input code page from:850 to 65001
debug3: receive packet: type 80
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug3: send packet: type 98
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
WILLKOMMEN!
.',;:cc;,'. .,;::c:,,. root@homeserver
,ooolcloooo: 'oooooccloo: OS: Raspbian 10 buster
.looooc;;:ol :oc;;:ooooo' Kernel: armv7l Linux 5.4.83-v7l+
;oooooo: ,ooooooc. Uptime: 1d 17h 50m
.,:;'. .;:;'. Packages: 714
.... ..'''''. .... Shell: 1176
.''. ..'''''. ..''. CPU: ARMv7 rev 3 (v7l) @ 4x 1.5GHz [43.3°C]
.. ..... ..... .. GPU:
. .''''''' .''''''. . RAM: 173MiB / 7874MiB
.'' .'''''''' .'''''''. ''.
''' ''''''' .'''''' '''
.' ........... ... .'.
.... ''''''''. .''.
'''''. ''''''''. .'''''
'''''. .'''''. .'''''.
..''. . .''..
.'''''''
......
Sat *** 23 05:00:01 CET 2021
BACKUP FEHLGESCHLAGEN! PLADDE NICHT GEFUNDEN!
Linux homeserver 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat *** 23 15:04:03 2021 from 192.168.1.2
debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
debug3: send packet: type 98
WILLKOMMEN!
.',;:cc;,'. .,;::c:,,. root@homeserver
,ooolcloooo: 'oooooccloo: OS: Raspbian 10 buster
.looooc;;:ol :oc;;:ooooo' Kernel: armv7l Linux 5.4.83-v7l+
;oooooo: ,ooooooc. Uptime: 1d 17h 50m
.,:;'. .;:;'. Packages: 714
.... ..'''''. .... Shell: 1176
.''. ..'''''. ..''. CPU: ARMv7 rev 3 (v7l) @ 4x 1.5GHz [43.3°C]
.. ..... ..... .. GPU:
. .''''''' .''''''. . RAM: 173MiB / 7874MiB
.'' .'''''''' .'''''''. ''.
''' ''''''' .'''''' '''
.' ........... ... .'.
.... ''''''''. .''.
'''''. ''''''''. .'''''
'''''. .'''''. .'''''.
..''. . .''..
.'''''''
......
Sat *** 23 05:00:01 CET 2021
BACKUP FEHLGESCHLAGEN! PLADDE NICHT GEFUNDEN!
Linux homeserver 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat *** 23 15:04:03 2021 from 192.168.1.2
Wi-Fi is currently blocked by rfkill.
Use raspi-config to set the country before use.
***@homeserver:~ $ debug2: client_check_window_change: changed
debug2: channel 0: request window-change confirm 0
debug3: send packet: type 98
***@homeserver:~ $
By default, FT uses Mosh -- it doesn't look like you've got that installed on your RPi, but I'm guessing you were smart enough to uncheck that box. I can also see that you use password login to access your RPi - I don't personally use password-based login, so I haven't tried that with FT. Can you try adding your id_*.pub to the RPi's authorized_hosts file, then use the corresponding private key in the "Identity file path" setting?
I created the key using powershell command ssh-keygen.exe -t rsa -C "USERNAME"
.
Now I'm getting this in FT:
Load key "C:\\Users\\janno\\.ssh\\id_rsa.pub": invalid format
The connection using powershell works with this key file.
And somehow the ssh connection worked using password ... at least for now.
I had something similar happen with my keys recently. For me, the solution was to remove any line-breaks in the keys.
I created the key using powershell command
ssh-keygen.exe -t rsa -C "USERNAME"
. Now I'm getting this in FT: Load key "C:\Users\janno\.ssh\id_rsa.pub": invalid format The connection using powershell works with this key file. And somehow the ssh connection worked using password ... at least for now.
The identity file path
in Fluent should point at the private ssh key, not the public one (change from id_rsa.pub
to id_rsa
).
Good catch. I totally glossed over that part.
Selecting the id_rsa
instead of id_rsa.pub
fixed it for me. I can login with it now. Thanks!
Hi, I recently switched to a Raspberry Pi 4 as my homeserver, with installed Raspberry OS Buster. Before this my homeserver ran on an old laptop mainboard and Ubuntu 20.04 Server. Since I switched I can't use FluentTerminal anymore to connect via SSH to my homeserver. This is what happens:
It happens to my homeserver, only. I can connect to a similar build at a friend. Also RPi 4 with Raspberry OS Buster, nothing different.
I enabled the log, which has this in it after I tried to connect:
I alread reinstalled and reset the application. I have this issue on both, my desktop and laptop, both running Windows 10 x64 20H2 Build 19042.746.