I can not login using ssh

senz · May 29, 2024, 7:54pm

i am trying log into my jetson nano device using SSH, i it is not allowing me to login here is the command that ima trying,

start cmd /k ssh jetson-nl1@jetsonnl1-desktop-ssh.at.remote.it -p 33002

after it will open a other cmd and will show like this →
Connection closed by 127.0.0.1 port 33002

my nano device username is “jetson-nl1” is there any issue with “-”. ?

bstrech · May 29, 2024, 8:24pm

If you are getting a prompt for a password, you are making a connection and the SSH server is on and listening.

I would try to login using verbose mode to see if you can see the hang up reason. If this fails, try making the connection via app.remote.it. If that fails, you may want to try SSH as admin user.

Open your terminal/putty app that you will be using for the SSH session.
Make sure that the connection in the Remote.It Desktop is running
Enter your connect command with verbose flag -v

Example:

ssh -v jetson-nl1@jetsonnl1-desktop-ssh.at.remote.it -p 33002

senz · May 30, 2024, 4:09am

anyway i am not getting a prompt for enter the password and i specified the -v that u mension here is the output ,

OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3
debug1: Reading configuration data C:\Users\ASUS/.ssh/config
debug1: C:\Users\ASUS/.ssh/config line 1: include C:/Users/ASUS/AppData/Local/remoteit/ssh_config matched no files
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to jetsonnl1-desktop-ssh.at.remote.it [127.0.0.1] port 33002.
debug1: Connection established.
debug1: identity file C:\Users\ASUS/.ssh/id_rsa type 0
debug1: identity file C:\Users\ASUS/.ssh/id_rsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_dsa type -1
debug1: identity file C:\Users\ASUS/.ssh/id_dsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa_sk type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519 type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519_sk type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519_sk-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_xmss type -1
debug1: identity file C:\Users\ASUS/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.5
debug1: compat_banner: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.5 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to jetsonnl1-desktop-ssh.at.remote.it:33002 as ‘jetson-nl1’
debug1: load_hostkeys: fopen C:\Users\ASUS/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
Connection closed by 127.0.0.1 port 33002

bstrech · May 30, 2024, 9:48pm

The error message is showing the error. There is no ssh_known_hosts or ssh_known_hosts2 file.
It is trying to find the file to write to it so that it allows the connection.
Typically the first time you connect via ssh to a device you will see a message similar to this (this is not what yours would be.)

The authenticity of host '111.222.333.444 (111.222.333.444)' can't be established.
RSA key fingerprint is f1:cf:58:ae:71:0b:c8:04:6f:XX:a6:b2:XX:1e:0c:8b.
Are you sure you want to continue connecting (yes/no)?

Answering yes will create the ~/.ssh/known_hosts2

Since it isn’t there, it wasn’t created in this path (note there is no extension to this file)
C:\Users\ASUS/.ssh/known_hosts2

You can try creating the connection again and then opening Powershell and running the connection command to see if you get the prompt to continue to connect. Otherwise, you may need to create the file manually. This is not something unique to Remote.It, this is required to validate the authenticity of the server you are connecting to.

senz · May 31, 2024, 5:22am

thanks for your reply …
the thing is i have two nano devices while the nano_board_1 is accessible nano_board_2 has this issue , in both cases OS was installed at two different time but remoreit was installed few days ago
i tried with PowerShell as well as u said , it didn’t work

– nano_board_1 --(os was installed recently)
input -
start cmd /k ssh jetsenz@jetsenz-desktop-ssh.at.remote.it -p 33000

output -
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3
debug1: Reading configuration data C:\Users\ASUS/.ssh/config
debug1: C:\Users\ASUS/.ssh/config line 1: include C:/Users/ASUS/AppData/Local/remoteit/ssh_config matched no files
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to jetsenz-desktop-ssh.at.remote.it [127.0.0.1] port 33000.
debug1: Connection established.
debug1: identity file C:\Users\ASUS/.ssh/id_rsa type 0
debug1: identity file C:\Users\ASUS/.ssh/id_rsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_dsa type -1
debug1: identity file C:\Users\ASUS/.ssh/id_dsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa_sk type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519 type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519_sk type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519_sk-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_xmss type -1
debug1: identity file C:\Users\ASUS/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.7
debug1: compat_banner: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.7 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to jetsenz-desktop-ssh.at.remote.it:33000 as ‘jetsenz’
debug1: load_hostkeys: fopen C:\Users\ASUS/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:CUixHxvQKLHCjt/kZh0xSrBafMUtZ9mgI0oey97ylgc
debug1: load_hostkeys: fopen C:\Users\ASUS/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts2: No such file or directory
debug1: Host ‘[jetsenz-desktop-ssh.at.remote.it]:33000’ is known and matches the ED25519 host key.
debug1: Found key in C:\Users\ASUS/.ssh/known_hosts:34
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory
debug1: Will attempt key: C:\Users\ASUS/.ssh/id_rsa RSA SHA256:kpuOy4otQ6CvIgX3dFTS5D3Zt5tnmxpcji5TJaSbHfc
debug1: Will attempt key: C:\Users\ASUS/.ssh/id_dsa
debug1: Will attempt key: C:\Users\ASUS/.ssh/id_ecdsa
debug1: Will attempt key: C:\Users\ASUS/.ssh/id_ecdsa_sk
debug1: Will attempt key: C:\Users\ASUS/.ssh/id_ed25519
debug1: Will attempt key: C:\Users\ASUS/.ssh/id_ed25519_sk
debug1: Will attempt key: C:\Users\ASUS/.ssh/id_xmss
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>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering public key: C:\Users\ASUS/.ssh/id_rsa RSA SHA256:kpuOy4otQ6CvIgX3dFTS5D3Zt5tnmxpcji5TJaSbHfc
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: C:\Users\ASUS/.ssh/id_dsa
debug1: Trying private key: C:\Users\ASUS/.ssh/id_ecdsa
debug1: Trying private key: C:\Users\ASUS/.ssh/id_ecdsa_sk
debug1: Trying private key: C:\Users\ASUS/.ssh/id_ed25519
debug1: Trying private key: C:\Users\ASUS/.ssh/id_ed25519_sk
debug1: Trying private key: C:\Users\ASUS/.ssh/id_xmss
debug1: Next authentication method: password
jetsenz@jetsenz-desktop-ssh.at.remote.it’s password:

— nano_board_2----(os was installed around 15 months ago)

input -
start cmd /k ssh jetson-nl1@jetsonnl1-desktop-ssh.at.remote.it -p 33002

output -
OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3
debug1: Reading configuration data C:\Users\ASUS/.ssh/config
debug1: C:\Users\ASUS/.ssh/config line 1: include C:/Users/ASUS/AppData/Local/remoteit/ssh_config matched no files
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to jetsonnl1-desktop-ssh.at.remote.it [127.0.0.1] port 33002.
debug1: Connection established.
debug1: identity file C:\Users\ASUS/.ssh/id_rsa type 0
debug1: identity file C:\Users\ASUS/.ssh/id_rsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_dsa type -1
debug1: identity file C:\Users\ASUS/.ssh/id_dsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa_sk type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519 type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519_sk type -1
debug1: identity file C:\Users\ASUS/.ssh/id_ed25519_sk-cert type -1
debug1: identity file C:\Users\ASUS/.ssh/id_xmss type -1
debug1: identity file C:\Users\ASUS/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.6
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.5
debug1: compat_banner: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.5 pat OpenSSH_7.0*,OpenSSH_7.1*,OpenSSH_7.2*,OpenSSH_7.3*,OpenSSH_7.4*,OpenSSH_7.5*,OpenSSH_7.6*,OpenSSH_7.7* compat 0x04000002
debug1: Authenticating to jetsonnl1-desktop-ssh.at.remote.it:33002 as ‘jetson-nl1’
debug1: load_hostkeys: fopen C:\Users\ASUS/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen PROGRAMDATA\ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
Connection closed by 127.0.0.1 port 33002

mycal · June 1, 2024, 11:58pm

I assume that remoteit is running on these devices, make sure you can log into the devices and ssh to itself. IE “ssh jetson-nl1@127.0.0.1” on the device itself if that does not work remote.it will not work.

You can also add a few more v’s to the command line, like -vvv for more verbose output on why it fails.

ssh -vvvv jetson-nl1@jetsonnl1-desktop-ssh.at.remote.it -p 33002

Looks like there is some sort of messed up configuration on the jetson, get it to work without remote.it first, then it should work with remote.it

Topic		Replies	Views
Can not change or update password because login via google account	1	122	February 5, 2024
Keyboard interactive SSH login fails Troubleshooting	1	764	October 6, 2021
Nomachine Report Features	4	1455	May 10, 2021
Cannot connect via SSH, access denied Troubleshooting	2	114	June 16, 2024
Password prompt in ssh: Permission denied, please try again Troubleshooting	3	41	December 23, 2024

I can not login using ssh

Related topics