I have been following the documentation on setting up ssh access to bitbucket.organd cannot seem to authenticate to the server.
I have created the id_rsa from openssl v1.0.1e and have copy-pasted id_rsa.pub to the key store through account management, However even after adding the key via ssh-add and starting the ssh-agent (/bin/bash), I cannot clone one of my repositories. Could you please let me know how to resolve this if this is a common issue.
Cloning into 'blah-blah-myrepo'... Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
You are executing the commands as different user when sudoing.
This is the normal user command and it is using normal user's ssh keys:
ssh -T firstname.lastname@example.org
when sudoing you're not using the normal user's ssh keys but root user instead:
sudo git clone
One possible workaround is to give the normal user rights to work in the /usr/local-directory. Below I have created a project specific subdirectory that is owned by localuser.
sudo mkdir /usr/local/src/<project> sudo chown localuser.localuser /usr/local/src/<project> cd /usr/local/src/ git clone <repo_url> <project>
Hi Jared, try this command: ssh -T email@example.comIf you get a response like "logged in as username.
You can use git or hg to connect to Bitbucket. Shell access is disabled."
The ssh keys were configured correct and the problem may be something else, otherwise you may need to review your keys.
hi there, This is still my output :(
localuser@myserver:/usr/local/src$ ssh -T firstname.lastname@example.org logged in as myusername. You can use git or hg to connect to Bitbucket. Shell access is disabled. localuser@myserver:/usr/local/src$ sudo git clone email@example.com:myusername/autumn-education.git Cloning into 'autumn-education'... Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
I just successfully cloned the repository i was after into my own home directory. Turns out it was a matter of user permissions and the root home dir being searched for the private key because i used sudo. At least this is what i am assuming is the cause.
In conclusion, the solution was to clone the repo into my home directory and the key was correctly picked up. :)
I Guess that i could give my regular user rwx on /usr/local/src if i wanted... but this is the solution for now.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot