Home › Forums › FABRIC General Questions and Discussion › SSH from Windows Terminal not working
- This topic has 3 replies, 3 voices, and was last updated 9 months, 2 weeks ago by Yuanjun Dai. 
- 
		AuthorPosts
- 
		
			
				
January 17, 2025 at 1:55 am #8079When trying to SSH into VM, I am getting an error. This is my SSH debug log: 
 ssh -v -F ./sshconfig.txt -i ./sliverSSHKey1 centos@1.2.3.4
 OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2
 debug1: Reading configuration data ./sshconfig.txt
 debug1: ./sshconfig.txt line 12: Applying options for *
 debug1: Setting implicit ProxyCommand from ProxyJump: “ssh” -l rsinha8_0000056965 -p 22 -F ./sshconfig.txt -v -W “[%h]:%p” bastion.fabric-testbed.net
 debug1: Executing proxy command: exec “ssh” -l rsinha8_0000056965 -p 22 -F ./sshconfig.txt -v -W “[1.2.3.4]:22” bastion.fabric-testbed.net
 debug1: identity file ./sliverSSHKey1 type 2
 debug1: identity file ./sliverSSHKey1-cert type -1
 debug1: Local version string SSH-2.0-OpenSSH_for_Windows_9.5
 OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2
 debug1: Reading configuration data ./sshconfig.txt
 debug1: ./sshconfig.txt line 5: Applying options for bastion.fabric-testbed.net
 debug1: ./sshconfig.txt line 12: Skipping Host block because of negated match for bastion.fabric-testbed.net
 debug1: Connecting to bastion.fabric-testbed.net [152.54.15.12] port 22.
 debug1: Connection established.
 debug1: identity file ./bapi-bastion-01-private type 2
 debug1: identity file ./bapi-bastion-01-private-cert type -1
 debug1: Local version string SSH-2.0-OpenSSH_for_Windows_9.5
 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.0
 debug1: compat_banner: match: OpenSSH_8.0 pat OpenSSH* compat 0x04000000
 debug1: Authenticating to bastion.fabric-testbed.net:22 as ‘rsinha8_0000056965’
 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@libssh.org
 debug1: kex: host key algorithm: ssh-ed25519
 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
 debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
 debug1: SSH2_MSG_KEX_ECDH_REPLY received
 debug1: Server host key: ssh-ed25519 SHA256:8ZrrCmYlgVJciScTwz3sDTsV3MV0kvcwtTgSOGYGwzg
 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
 Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
 debug1: ssh_packet_send2_wrapped: resetting send seqnr 3
 debug1: rekey out after 134217728 blocks
 debug1: SSH2_MSG_NEWKEYS sent
 debug1: expecting SSH2_MSG_NEWKEYS
 debug1: ssh_packet_read_poll2: resetting read seqnr 3
 debug1: SSH2_MSG_NEWKEYS received
 debug1: rekey in after 134217728 blocks
 debug1: get_agent_identities: ssh_get_authentication_socket: No such file or directory
 debug1: Will attempt key: ./bapi-bastion-01-private ECDSA SHA256:E1nua6fvkIjJVSIqspV1C9GbmFujHNVq/tJty+5BMdQ explicit
 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,gssapi-keyex,gssapi-with-mic
 debug1: Next authentication method: publickey
 debug1: Offering public key: ./bapi-bastion-01-private ECDSA SHA256:E1nua6fvkIjJVSIqspV1C9GbmFujHNVq/tJty+5BMdQ explicit
 debug1: Server accepts key: ./bapi-bastion-01-private ECDSA SHA256:E1nua6fvkIjJVSIqspV1C9GbmFujHNVq/tJty+5BMdQ explicit
 Authenticated to bastion.fabric-testbed.net ([152.54.15.12]:22) using “publickey”.
 debug1: channel_connect_stdio_fwd: 1.2.3.4:22
 debug1: channel 0: new stdio-forward [stdio-forward] (inactive timeout: 0)
 debug1: Requesting no-more-sessions@openssh.com
 debug1: Entering interactive session.
 debug1: pledge: network
 debug1: pledge: agent
 debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
 debug1: Remote: /home/rsinha8_0000056965/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
 debug1: Remote: /home/rsinha8_0000056965/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
 channel 0: open failed: connect failed: Network is unreachable
 stdio forwarding failed
 kex_exchange_identification: Connection closed by remote host
 Connection closed by UNKNOWN port 65535This is my config file: UserKnownHostsFile /dev/null 
 StrictHostKeyChecking no
 ServerAliveInterval 120Host bastion.fabric-testbed.net 
 User rsinha8_0000056965
 ForwardAgent yes
 Hostname %h
 IdentityFile ./bapi-bastion-01-private
 IdentitiesOnly yesHost * !bastion.fabric-testbed.net 
 ProxyJump rsinha8_0000056965@bastion.fabric-testbed.net:22January 17, 2025 at 2:22 am #8080I have tried SSHing from JupyterHub and the end of the log now has these new statements: 
 debug1: Remote: /home/rsinha8_0000056965/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
 debug1: Remote: /home/rsinha8_0000056965/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding
 debug1: client_input_global_request: rtype keepalive@openssh.com want_reply 1
 debug1: client_input_global_request: rtype keepalive@openssh.com want_reply 1
 debug1: client_input_global_request: rtype keepalive@openssh.com want_reply 1
 debug1: client_input_global_request: rtype keepalive@openssh.com want_reply 1
 channel 0: open failed: connect failed: Connection timed out
 stdio forwarding failed
 kex_exchange_identification: Connection closed by remote host
 Connection closed by UNKNOWN port 65535Unsure why connection is timing out. January 17, 2025 at 8:23 am #8081what is the Ip of the machine you are trying to ssh into. From the first post i see 1.2.3.4 which is not a valid IP January 17, 2025 at 8:54 am #8082Hi, It works now. 
- 
		AuthorPosts
- You must be logged in to reply to this topic.
