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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,463,496
Community Members
 
Community Events
176
Community Groups

.

Edited

.

2 answers

1 accepted

0 votes
Answer accepted

Hi @T,

I went ahead and created a support ticket using the email of your community account, you should have received an email with a link to the support ticket.

The ticket is visible only to you and Atlassian staff, so you can share the public SSH key you are trying to add and we can check where this key has been added.

Please note that we cannot remove SSH keys, you will need to have access to the repo(s) in question in order to be able to remove it.

Kind regards,
Theodora

0 votes

Welcome to the Atlassian Community!

The most common cause of this problem is that people share keys across their accounts,  The second most common cause is people sharing keys with other people's accounts.

My guess is that you've done the first (It's really easy to fall into it - Nic and (g)root on this laptop tried to upload the same key to Bitbucket - both of them are me, all the time, I didn't think about it properly)

You can ask Atlassian to look for the duplicates, if you are on a supported tier, but if you're not, then the only answers are

1) Talk to the people you shared the key with (which you should not have done)

2) Create a new key.  That is always an option, and it's the best one when you've leaked the old one.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events