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

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

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 Join to answer
Community showcase
Brian Ganninger
Published Jan 23, 2018 in Sourcetree

Tip from the team: workflow and keyboard shortcuts

Supported Platforms macOS Sourcetree has a lot to offer and, like many developer tools, finding and using it all can be a challenge, especially for a new user. Everyone might not love ...

244 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot