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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I created a new SSH key and added it to my keys, checked that I could access the repo and got the correct response but when I try to pull from the repo, I get "authentication failed". Here is my consol session:
...
[centos@ip-10-2-1-239 laravel]$ eval `ssh-agent`
Agent pid 137198
[centos@ip-10-2-1-239 laravel]$ ssh-keygen -t ed25519 -b 4096 -C "denewey@gmail.com" -f ~/.ssh/id_rsa_apr_net
Generating public/private ed25519 key pair.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/centos/.ssh/id_rsa_apr_net.
Your public key has been saved in /home/centos/.ssh/id_rsa_apr_net.pub.
The key fingerprint is:
SHA256:5vXPHPZx8kBs6zmbiJf64jqscHTWXFuyHIVX+US8Auo denewey@gmail.com
The key's randomart image is:
+--[ED25519 256]--+
| ..++|
| .....o|
| . =...o|
| + o O ..|
| . S + + = |
| . = E . o . |
| . ... ..*..|
| o o ..oB.Oo|
| ...++=o Ooo|
+----[SHA256]-----+
[centos@ip-10-2-1-239 laravel]$ ssh-add ~/.ssh/id_rsa_apr_net
Enter passphrase for /home/centos/.ssh/id_rsa_apr_net:
Identity added: /home/centos/.ssh/id_rsa_apr_net (denewey@gmail.com)
[centos@ip-10-2-1-239 laravel]$ less ~/.ssh/id_rsa_apr_net.pub
[centos@ip-10-2-1-239 laravel]$
[centos@ip-10-2-1-239 laravel]$
[centos@ip-10-2-1-239 laravel]$ ssh -T git@bitbucket.org
authenticated via ssh key.
You can use git to connect to Bitbucket. Shell access is disabled
[centos@ip-10-2-1-239 laravel]$ git pull
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.
Please make sure you have the correct access rights
and the repository exists.
...
Any idea what I might be doing wrong?
Hi @David Newey and welcome to the community!
The private SSH key you created may not be offered during the git pull operation.
I would suggest creating a file named config in your ~/.ssh folder and adding the following lines (if the file exists, just add the following content)
Host bitbucket.org
AddKeysToAgent yes
IdentityFile /home/centos/.ssh/id_rsa_apr_net
This will ensure that this specific SSH key is offered every time you clone/pull/push to a Bitbucket Cloud repo.
I would also suggest double-checking permissions: premissions should be 700 for the ~/.ssh directory, 644 for the public SSH key, and 600 for the private key.
Please feel free to let us know how it goes and if you need any further help!
Kind regards,
Theodora
I am assuming you have access to the repository as Nic has mentioned above.
Add the contents of your public key to bitbucket as mentioned here. Check the application Cloud / DC version etc. I think you are using cloud by the ssh command used.
You can find it here, but I think you have copied it?
/home/centos/.ssh/id_rsa_apr_net.pub
Is this a git repository you are in already?
Can you use interactive authentication to clone the repository?
e.g.
git clone https://user@bitbucket.org/PKEY/repo-name.git
If the above works and as already mentioned, you have added your public key to bitbucket
git clone ssh://git@bitbucket.org/PKEY/repo-name.git
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian Community!
Have you added the key to Bitbucket? And does the account have access to the repositories?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.