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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Someone has already added that key as an access key to a repository



When trying to generate SSH key I'm getting the following error - 

Someone has already added that key as an access key to a repository

I checked the accounts I have and. they are not using any ssh key.


Can you please help me. 


2 answers

1 vote
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 21, 2022

Hi @Roni Ezrati,

The error message indicates that the public SSH key you are trying to add is already added as an Access key to a repo (and not to an account).

An SSH key can be added as an Access key to a repository if you open the repository on Bitbucket Cloud website, go to Repository settings and then select Access keys. On this page, you can also view and remove existing Access keys from repos (you need to have admin access to a repo in order to access the Repository settings and the Access keys pages).

Access keys provide Read-only access to repositories. A certain public key can be added as an Access key to multiple repositories, however, it is not possible to use it as an account's SSH key at the same time.

You can follow the steps I mentioned above with any repositories you have admin access to in order to find out which ones have this key and then remove it. If you still cannot figure this out, I see that you have access to a workspace on a paid billing plan. You can therefore create a ticket with the support team where you can share the public SSH key you are trying to add and we can check where this key has been added.

You can create a ticket via, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. Please make sure to provide the workspace-id of the workspace that is on a paid billing plan, in order to be able to proceed with the ticket creation.

Please feel free to let me know if you have any questions.

Kind regards,

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 19, 2022

There's no easy way to work this out because the keys that belong to other accounts should not be shared.

If you shared the key with someone, you should know who.  If you were given the key by someone, then you'll need to ask them.  

If you have no luck chasing it down, you can raise a support request with Atlassian, and they can search out the key for you and hence identify the account you shared it with.

If you don't want to spend ages chasing down the share, then you can create a new key for your account and use that instead.  You should do this anyway, so you are not sharing keys.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events