- This topic has 1 reply, 2 voices, and was last updated 3 months, 3 weeks ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Home › Forums › FABRIC General Questions and Discussion › Unable to access VMs
Hi all,
I’m unable to access the machines via Bastion key, is something wrong?
Look the logs:
Starting a new connection to: “bastion.fabric-testbed.net” port “22”
Starting address resolution of “bastion.fabric-testbed.net”
Address resolution finished
Connecting to “128.163.180.149” port “22”
Connection to “bastion.fabric-testbed.net” established
Starting SSH session
Remote server: SSH-2.0-OpenSSH_8.0
Agreed KEX algorithm: curve25519-sha256@libssh.org
Agreed Host Key algorithm: ecdsa-sha2-nistp256
Agreed server-to-client cipher: aes256-gcm@openssh.com MAC: INTEGRATED-AES-GCM
Agreed client-to-server cipher: aes256-gcm@openssh.com MAC: INTEGRATED-AES-GCM
Agreed client-to-server compression: none
Agreed server-to-client compression: none
Handshake finished
Checking host key: c1:1b:df:74:6b:15:ae:70:9b:5d:86:cf:e8:2a:5c:2e
Host “bastion.fabric-testbed.net”:”22″ is known and matches
Authenticating to “bastion.fabric-testbed.net”:”22″ as “rodrigo_0000140592”
Available client authentication methods: publickey,password,keyboard-interactive
Authentication that can continue: gssapi-with-mic,publickey
Authenticating using publickey method
Authentication failed (publickey)
Partial success: no
Authentication that can continue: gssapi-with-mic,publickey
No more authentication methods to try
Regards.,
Rodrigo Moreira
Hi Rodrigo,
It’s possible that your bastion keys have expired. Could you please check the expiration of the keys from the Portal via Experiments -> Manage SSH Keys?
Also, please try running the notebook jupyter-examples-rel1.7.1/configure_and_validate.ipynb
?
This notebook shall regenerate the bastion keys if the keys have expired. Please very SSH access after that.
Please let us know if you still see errors.
Thanks,
Komal