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

Question

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

KieranA · Answer

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:

* Some instances have repoted the username being case sensitive, so perhaps check that first.
* Test your SSH connection to the server - check if this yields the same results.
* Check your public/private keys to ensure they're correct. The servers key may (although shouldn't have) changed.
* Just check your ~/.ssh/ folder to make sure the keys are in there (I've made this mistake before on a new set up!)
* 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.