How to rectify SSH error: Authenticity of host can't be established?

I'm new to SSH. I'm working my way through the BitBucket tutorial "Set up SSH for Git":

I'm at step 6.9:

Return to the terminal window and verify your configuration by entering the following command

ssh -T

I get the error:

The authenticity of host ' (' can't be established.
RSA key fingerprint is ....

I would be grateful for any advice.


2 answers

1 accepted

24 votes
Accepted answer

This is actually normal. It’s not actually an SSH error. The Atlassian people really should have documented that this will probably happen in their instructions. Omitting it is bad on their part.

What’s happening is that SSH is being cautious. That’s part of being secure. Whenever SSH tries to log in to a host it hasn’t seen before, it will put up a message like this.

You didn’t paste in the whole message. It looks like this:

$ ssh -oUserKnownHostsFile=/dev/null -T
The authenticity of host ' (' can't be established.
RSA key fingerprint is 97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40.
Are you sure you want to continue connecting (yes/no)?

SSH is saying “I haven’t seen this host before. It has this IP. It identifies itself with this fingerprint. Do you really want to connect?” And in really secure environments, you’d actually compare the fingerprint with the fingerprint that you had been given before to make sure you’re not connecting with an imposter host.

In this particular case, you don’t have any other fingerprint to compare it to. But you really are trying to connect to So you can go ahead and say “yes” and you should continue logging in.

SSH will also save the hostname and fingerprint in the ~/.ssh/known_hosts file. The next time you try to log in, it will see that you’ve connected to bitbucket.orgbefore, and has the same fingerprint, so it won’t put up that message again.

The security comes in in case some bad guy tries to impersonate Since forging fingerprints is really hard, he likely won’t be able to impersonate that, so when you try to log in to the bad site, you’ll get a message like this:

Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
Please contact your system administrator.
Add correct host key in ~/.ssh/known_hosts to get rid of this message.
Offending key in ~/.ssh/known_hosts:1
RSA host key for has changed and you have requested strict checking.
Host key verification failed.

Now, that’s an error.

Wow! Thanks for v. detailed response. All OK now. (Not sure if "Thanks" is permitted on this forum. If so - I can delete it.)

Thank you very much!

That's really helped me!

So I just needed to continue with YES option.

Very useful answer and well explained. Thank  you so much smile

0 votes

Also please make sure that you have added the SSH Key in your bitbucket account under settings. I had a similar message migrating from GitHub to bitbucket.

btw, here is an an updated link the last one is down 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

432 views 6 9
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