You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I cannot add my SSH key to my account because of this: "Someone has already added that key as an access key to a repository."
I have removed all the old keys but nothing changed. I would need to solve this problem.
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.
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 the repositories of your workspace in order to find out which ones have this key and then remove it. If you still cannot figure out it, please feel free to let me know and I can create a support ticket for you so that you share the public key and we let you know where it is added.
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 (and should) create a new key for your account and use that instead.
Nope, we're not your admins, you'll need to ask them, or Atlassian if you don't know who your admins are.