Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Someone has already registered that SSH key

I have my public key set in some users repo and I can't remove it from there. 

Went through this KB article : .

At the bottom it says "Then visit the account for that username and remove or update the SSH key configuration." .  How do I do that? I went to the users page I can't do anything there. Any instructions?

I tried to contact that user numerous times and he's not responding. 




5 answers

0 votes
Ana Retamal Atlassian Team Oct 03, 2017

Hi Tomaz, if you don't have access to the Bitbucket account where your SSH key has been registered, you won't be able to remove it. You'll need to create a new one following the steps at Set up an SSH key.

Let us know if you have any questions!



I've remove the key from the other account and I'm still getting the same error.

Like # people like this

Nevermind, Just try again  couple of minutes later and it works :) 

Ana Retamal Atlassian Team Jan 16, 2018

Glad to hear that, Favio! Have a nice day :)


Hi! In my case, I did a full Atlassian account delete without removing the SSH key. Why this error occurs? So, you're not deleting also any service/setting related to that deleted account?? If it's a full delete then everything should be deleted including the SSH key.

Am I correct to assume Atlassian is not really deleting the account but only tagging it as deleted that's why it still says "someone has already registered that ssh"?

I have added my ssh key to the email account of an employer, and now I dont have that account. What shall I do now ?

Situation 1 :

You could always create another ssh key without damaging the setup that the other employee has done on this machine using that key (if he ever comes back to work on it)

Solution : Add a new key by using key-gen command (specify a different key file name and use it at the ssh section in your profile.)

Note : You might want to consider configuring git to use different keys for different domains. (


Situation 2 :

You and your employer are both ok to ruin the previous setups and the employee is never gonna come back.

Solution : Just completely over write the previous key by using the key-gen command and over writing the key (just press enter at both steps when asked for key file name and re-entering the name)



Arun Anson

You should just give the solution to use the same key. 

Ana Retamal Atlassian Team Oct 22, 2019

Hi @Thibault Jamme , and welcome.

You won't be able to use the same SSH key if it's already in use within Bitbucket. The solution is to generate a new SSH key, as explained in our documentation

Hope that helps.


Thanks for your reply.

You should fix that problem.


How many keys does Atlassian think a user can have :)?

If I am a freelancer for example, do you expect me to generate a new key for every single project ?

I understand the security "explanation", and it sort of makes sense, but this is why we "invented" the SSH keys in the first place, to have a secure and convenient way to authenticate, and this is ruining it.

Also, SSH keys have passwords attached, so even if the key is compromised, it cannot be used in most of cases.

I would say that refactoring Bitbucket to use key-per-project is a big change and nobody wants to invest time in it, that's why people talk about security...


Meanwhile, I will generate the 10'th key I have to use just because of this :)

Ana Retamal Atlassian Team Nov 19, 2019

Hi @andrian.jardan , welcome!

Bitbucket shouldn't be asking you to have a different SSH key for every project, it should only be asking you for a different SSH key for every Bitbucket account. If each of your projects belongs to a different account, then in those cases you'll indeed need different SSH keys. 

Can you let us know if that is your case? If not, can you show us a screenshot where we can see that you need different keys for each project?

Best regards,


Hello @Ana Retamal


Yes, I unfortunately have to use different accounts for project related reasons, and that is troublesome. Even when I created a different key for the accounts, when I have all the keys added to my SSH agent, just one key is being served (the default one), so I get "Forbidden", unless I only load the proper key :)


Quite annoying...

Is there any chance Bitbucket will change that? I am a freelancer working for different companies and sometimes some of them have bitbucket. Imagine the headaches this causes.

Right now i have my SSH key registered to an account with company X and i want to start using BitBucket for a newly formed company of mine. I am gonna stick with github until i can think a solution that doesn't add headaches in my daily workflow.

Any ideas anyone? (Except having multiple keys and letting GIT knows) 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

441 views 4 4
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you