Permission denied (publickey,keyboard-interactive). fatal: The remote end hung up unexpectedly

Ella Gruber February 20, 2013
Hi,
We recieved the following error when trying to clone a GIT repo hosted on assembla.com
Recieved this error:
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
abort: repository git@git.assembla.com:m-youtube-nissan.git not found!
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Permission denied (publickey,keyboard-interactive).
fatal: The remote end hung up unexpectedly
Thank you

1 answer

1 vote
KieranA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2013

Hi Ella,

This looks like an SSH issue to me, there's various reasons why it could happen. Here's a few things worth troubleshooting:

  1. Some instances have repoted the username being case sensitive, so perhaps check that first.
  2. Test your SSH connection to the server - check if this yields the same results.
  3. Check your public/private keys to ensure they're correct. The servers key may (although shouldn't have) changed.
  4. Just check your ~/.ssh/ folder to make sure the keys are in there (I've made this mistake before on a new set up!)
  5. Go through the set up process for your keys again starting from scratch if all else fails.

Perhaps you could ensure your public key is present in ~/.ssh/ first? And then we can check if it's correct from there, ensuring it matches the servers public key.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events