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

I'm not able to clone, pull and push my repository via ssh



despite being the administrator of the repository, I cannot execute any of the basic commands - such as git pull and git push - via ssh. I always get the error message The requested repository either does not exist or you do not have access. If you believe this repository exists and you have access, make sure you're authenticated.
fatal: Could not read from remote repository.".

And when I try to add my public ssh key through access key of the repository I always get the error "Someone has already added that SSH key to another account.".


Where I'm being wrong?






1 answer

1 vote
Mateus T Atlassian Team Aug 02, 2022

Hi @Fabio Marras!

Welcome to the Atlassian Community!

Based on the behavior you mentioned on this thread, I believe that your Git authentication through SSH is failing due to your private SSH key not being added to your local SSH agent. In order to check this, you can run the following commands locally:

$ eval `ssh-agent`

$ ssh-add ~/path/to/private_key

These commands should start your local agent and add your private key to it, making sure that your local machine is able to authenticate with your remote Bitbucket repositories.

You can also check more about the SSH setup process through the following documentation:

Set Up an SSH Key 

In case you are still facing this issue after spinning up your agent and locally adding your private key, please run the following commands locally and share the output with us so we can have a deeper look into it!

$ ssh -Tv

Make sure to scatter through the logs and mask any sensitive information before sharing it in this thread!


Mateus T

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events