Support #6055
closed
[Support] Cannot log into VM
Added by Mohammad Zia over 9 years ago.
Updated over 5 years ago.
Description
Hi,
I have followed the instructions for logging into the VM, specifically, generating a public SSH key and adding it to the SSH Keys in the Arvados workbench interface. Every time I try to connect, I get the following error:
"Permission denied (publickey).
ssh_exchange_identification: Connection closed by remote host"
This error suggests that my public isn't working.
When logging into Arvados, I used my Google account for authentication. This resulted in Arvados listing my Google user name as the login name in the Arvados workbench. My Google username, however, is different from my shell user name ($USER). When attempting to log into Arvados VM, do I use googleuser@shell or my shell user name, meaning $USER@shell?
Thanks,
--Mohammad
Hi Mohammed,
Mohammad Zia wrote:
I have followed the instructions for logging into the VM, specifically, generating a public SSH key and adding it to the SSH Keys in the Arvados workbench interface. Every time I try to connect, I get the following error:
"Permission denied (publickey).
ssh_exchange_identification: Connection closed by remote host"
This error suggests that my public isn't working.
That's right, that seems to be the problem.
When logging into Arvados, I used my Google account for authentication. This resulted in Arvados listing my Google user name as the login name in the Arvados workbench. My Google username, however, is different from my shell user name ($USER). When attempting to log into Arvados VM, do I use googleuser@shell or my shell user name, meaning $USER@shell?
You should use what is listed on your 'manage account' page. Assuming you are on our cloud installation, the link is
https://cloud.curoverse.com/manage_account
Does this help?
Thanks,
Ward.
- Tracker changed from Bug to Support
- Assigned To set to Ward Vandewege
- Target version set to 2015-06-10 sprint
Hi Ward,
I am using the Arvados docker image and not the curoverse installation.
Thanks,
--Mohammad
Hi Mohammad,
Sorry for the delay - this shell image is not fully functional at the moment, it doesn't know how to install user accounts yet - we're tracking this in issue #5625. The workaround is to install the python sdk and the cli tools on the host that your docker images run; would that work for you?
Thanks,
Ward.
- Target version changed from 2015-06-10 sprint to Bug Triage
- Status changed from New to Feedback
- Target version deleted (
Bug Triage)
- Subject changed from Cannot log into VM to [Support] Cannot log into VM
- Status changed from Feedback to Resolved
Also available in: Atom
PDF