A more sustainable solution is to edit .bashrc (e.g. vi ~/.bashrc) and then add the following line to it (replace the key name):

KEY="$HOME/.ssh/YOUR_KEY"
if [ -e "${KEY}" ]; then
ssh-add -q "${KEY}"
fi

This will load the key automatically when you start the shell

You can set IdentityFile flag file in ~/.ssh/config file as follows:

Host bitbucket.org
IdentityFile ~/.ssh/id_rsa

When you run

ssh git@bitbucket.org

the ssh client allows you to selects a file from which the identity (private key) for RSA or DSA authentication is read.

SSH Client To Use Given Private Key ( identity file )

Edit: As Dan Swain points out in the comments, from 1 March 2022 this answer will have been superseded by authentication policy changes: https://bitbucket.org/blog/deprecating-atlassian-account-password-for-bitbucket-api-and-git-activity

The same applies to Github repositories as well, FWIW.

Thanks for the heads-up, Dan.

It might make sysadmins recoil in horror, but after suffering this problem (Windows) I gave up on SSH and went back to HTTPS.

You have to type your password in every time but, particularly under Windows where SSH is not as commonly available as with the *nix family, I see this as a minor inconvenience compared with the headaches of SSH.

In my case it solved the problem to add the ssh key from the directory

~/.ssh/id_rsa.pub

on bitbucket.org. I named it also id_rsa.pub on the website.

At the beginning I added another key I created just for bitbucket and named it like that. The first remote actions worked but after some days the request have been denied.

In Windows, @efesaid answer worked for solving issues with the ssh connection test. By the way, you can add a -v to see what keys (by name) are being attempted and why the connection fails.

However, when pushing to bitbucket, using git@bitbucket.org:user/repo.git, it seems that the host is not precisely bitbucket.org so I still was getting permission denied problems. I solved them by (re)naming my key to id_rsa (this is the key name that was being attempted in the ssh test).

This works if you have a single rsa key. For multiple keys, perhaps the host in the config file must be

bitbucket.org:username

but I am no sure this is unde

I faced same issues in Linux (Ubuntu).

I solved it using setup in git:

git config --global user.name "Your Name"
git config --global user.email your.email@example.com

Printing the public key using cat and SSH key to bitbucket.org:

$ cat ~/.ssh/id_rsa.pub

Adding Bitbucket and pushing up the repository:

git remote add origin git@bitbucket.org:<username>/your repository name.git
git push -u origin --all

That's all!

I think that the bitbucket instructions are best. Check if ssh is installed and if not install it

krasen@krasen-Lenovo-Y50-70:~$ ssh -v
usage: ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
[-D [bind_address:]port] [-E log_file] [-e escape_char]
[-F configfile] [-I xxxxx] [-i identity_file]
[-L [bind_address:]port:host:hostport] [-l login_name] [-m mac_spec]
[-O ctl_cmd] [-o option] [-p port]
[-Q cipher | cipher-auth | mac | kex | key]
[-R [bind_address:]port:host:hostport] [-S ctl_path] [-W host:port]
[-w local_tun[:remote_tun]] [user@]hostname [command]


krasen@krasen-Lenovo-Y50-70:~$ ls -a ~/.ssh
.  ..  google_compute_engine  google_compute_engine.pub  identity  identity.pub  known_hosts


krasen@krasen-Lenovo-Y50-70:~$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/home/krasen/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/krasen/.ssh/id_rsa.
Your public key has been saved in /home/krasen/.ssh/id_rsa.pub.
The key fingerprint is:
xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx krasen@krasen-Lenovo-Y50-70
The key's randomart image is:
+--[ RSA 2048]----+
|              .  |
|           xx x  |
|          xxxxx  |
|       xxxxxxxxx |
|      .xxxxxxxx  |
|       xxxxx     |
|     xxxxxxxxxxxx|
|    xxxxxxxxxxxxx|
|     xxxxxxxxxxx |
+-----------------+
krasen@krasen-Lenovo-Y50-70:~$ ls -la ~/.ssh
total 40
drwx------   2 krasen krasen 4096 Jun 29 14:30 .
drwxr-xr-x 110 krasen krasen 4096 Jun 29 13:00 ..
-rw-------   1 krasen krasen 1675 Mar 18  2015 google_compute_engine
-rw-r--r--   1 krasen krasen  409 Mar 18  2015 google_compute_engine.pub
-rw-------   1 krasen krasen 1679 Jun 29 13:15 identity
-rw-r--r--   1 krasen krasen  409 Jun 29 13:15 identity.pub
-rw-------   1 krasen krasen 1679 Jun 29 14:30 id_rsa
-rw-r--r--   1 krasen krasen  409 Jun 29 14:30 id_rsa.pub
-rw-r--r--   1 krasen krasen 4698 Jun 29 13:16 known_hosts


krasen@krasen-Lenovo-Y50-70:~$ ssh-agent /bin/bash

to check if the agent is started

krasen@krasen-Lenovo-Y50-70:~$ ps -e | grep [s]sh-agent
26503 ?        00:00:00 ssh-agent
krasen@krasen-Lenovo-Y50-70:~$ ssh-add ~/.ssh/id_rsa
Identity added: /home/krasen/.ssh/id_rsa (/home/krasen/.ssh/id_rsa)
krasen@krasen-Lenovo-Y50-70:~$ ssh-add -l
2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx /home/krasen/.ssh/id_rsa (RSA)
krasen@krasen-Lenovo-Y50-70:~$ cat ~/.ssh/id_rsa.pub
ssh-rsa xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

get this key and add it as key in the bitbucket settings

Check for exisiting SSH Key

ls -al ~/.ssh

Copy the SSH Key

cat ~/.ssh/id_rsa.pub | pbcopy

Add the copied SSH Key to 'Bitbucket Settings', 'Security', 'SSH Keys'.

In my case on fresh Ubuntu 16 machine I was missing files in ~/.ssh folder so what worked:

1. Go to folder ~/.ssh
2. Run ssh-keygen and name your file i.e. id_rsa
3. Run cat ~/.ssh/id_rsa.pub | xclip -sel clip
   If you miss xclip just apt-get install xclip :)
4. Go to (in url change USERNAME to your bitbucket username:) ) https://bitbucket.org/account/user/USERNAME/ssh-keys/
5. Click Add key and paste the key from the clipboard

Magic - it works now :)

You might be using ssh as the git origin url. Try removing the ssh origin like so

git remote rm origin

Then add new origin with HTTPS url and try pushing again.

git remote add origin https://git@bitbucket.org/SOMETHING/SOMETHING.git
git push -u origin master

Make sure you paste your url from bitbucket as origin.

I got round a similar issue where I had previously used HTTPS to access the repository and had to switch to SSH by setting the url like so;

git remote set-url origin ssh://git@bitbucket.org/...

This may be obvious, but I spent quite a bit of time on it.

Check the destination when running git remote -v

In my case I had the ssh keys perfectly set up but the output from this command was:

origin get@github.com:USERNAME/REPOSITORY.git

(notice the get not git)

and not

origin git@github.com:USERNAME/REPOSITORY.git

Again, this was a very particular case, but be sure to check the strings carefully of this system if you're having trouble.

You can fix this with the following commands:

git remote set-url origin git@github.com:USERNAME/REPOSITORY.git

After setting up git with git config --global user.name "My Name" and git config --global user.email myemail@x.com, I was still having trouble with the Permission Denied, (publickey) error. To solve this, I first generated a new ssh token with

ssh-keygen

and copied it with

pbcopy < ~/.ssh/YOUR_KEY

After that, I went to bitbucket.com to add it as a new SSH key in my settings. Then, I returned to my terminal to add the new key with

ssh-add ~/.ssh/YOUR_KEY.

The big problem that I was having was that I missed the critical ssh-add [key] command.

Make sure your have switched to the correct user on terminal.

In my case root user was not the one which has ssh keys added at the bitbucket settings panel. Running git with sudo makes it run from root user and my own user was the one who has keys added.

My problem was to do with permissions.

My project directory was owned by root, but I was logged in as ubuntu. I would get PERMISSION DENIED if I typed in a git command, e.g. git pull origin master, so I used sudo git pull origin master.

I had registered ubuntu's SSH key from /home/ubuntu/.ssh/id_rsa.pub with BitBucket.

However, I was using sudo. So the SSH key used was actually /home/root/.ssh/id_rsa.pub which was different to what BitBucket had.

Solution for my case

chown -R username_here:username_here project/folder/here

Now it should work if you don't prepend sudo

OR give BitBucket root's key

I had similar problem with BitBucket. in my case, it only fixed after I found out I should remove sudo from git clone command!

According to Attlassian:

You shouldn't use sudo when cloning, pushing, or pulling because the ssh-agent runs on the user level, not the root level.

In my case my issue was that I tried using the .ppk file the putty generated and no matter what I tried nothing worked.

In the end I figured that the it was the wrong file and I had to export it, save it as the id_rsa file and load it, then everything worked.

In source tree select your project right click then you find an option "Convert to SSH"-> Repair -> login this solved for me

If any.ssh fix didn't work or you cloned as https there can be a validation issue. in my case, I fixed this error by providing my username and password when cloning the repo. This issue can occur when you are using multiple accounts in a same machine.

use "git clone https://username:password@github.com/username/repository.git" command with your user name and password and repo URL.

I like the Answers here, but they all kind of miss a possible root cause.

with the command:

ssh -T git@bitbucket.org

replace bitbucket.org with your own bitbucket host.

If you get an answer like:

This deploy key has read access to the following repositories:

team-name/repository-name

that is why pushing to the repository is not working.

This you can also double check in the Bitbucket Web UI, notice the read-only access in the description:

Hope this gives a different perspective to the same problem.

If you are using SourceTree with Bitbucket, the solution is the next:

Go to your personal Bitbucket settings Got to App passwords and create an app password Give the next permissions to the app password:

Repositories (R-W-A-D)
Projects (R-W)
Pull request (R-W)

After that, keep the password generated Try to clone again your repo A password popup will be displayed, input the generated password. That's all.

If you have multiple keys in your computer make sure you add bitbucket to the list such as below in

.ssh/config

# Company account
Host company
HostName github.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_accelya


# Personal account
Host personal
HostName github.com
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_personal




# Personal account bitbucket
Host bitbucket
HostName bitbucket.org
PreferredAuthentications publickey
IdentityFile ~/.ssh/id_rsa_personal_bitbucket

In my case, this issue happened because I had a number of ssh keys in the ~/.ssh. I had to create a bitbucket.org specific entry in ~/.ssh/config as follows:

Host bitbucket.org
Hostname bitbucket.org
IdentityFile <location-of-.ssh-directory>/bb-rsa
IdentitiesOnly=yes

My guess is that since we don't specify a key while cloning, ssh tries all the keys in ~/.ssh which bitbucket thinks as a hacking attempt and rejects our repo clone attempt.

If you're using Fedora 33+ and using the RSA algorithm. Use more secure alogrithm like ECDSA or ED25519 instead:

ssh-keygen -t ed25519 -C "your_email@example.com"

Check out the bitbucket support for more details

Cause

The RSA algorithm is being quickly deprecated across operating systems and SSH clients because of various security vulnerabilities, with many of these technologies now outright denying the use of this algorithm.

(info) For example - here is the announcement from OpenSSH regarding their upcoming deprecation of the ssh-rsa algorithm. In the event that you are using an operating system or SSH client whose version has this algorithm disabled, it's possible that any SSH keys previously generated using this algorithm will no longer be accepted by these technologies.

Resolution

To fully resolve this issue, our team recommends that these deprecated keys be re-generated using a supported and more secure algorithm such as ECDSA and ED25519

I update config file with the top line to get it working

PubkeyAcceptedKeyTypes +ssh-rsa

Host <yourhost>

IdentityFile ~/.ssh/id_rsa

My Solution:

git remote rm origin

• Add you user name before @bitbucket.org to the repo URL

git remote add origin https://{USER_NAME}@bitbucket.org/{NAME}/{REPO_NAME}.git


git push -u origin master