Fingerprint has already been taken gitlab

Question 1

Make sure to cut away everything at the end of the base64 encoded string. Also remove all newlines so the string contains no newlines.

This did the trick for me.

Question 2

In my case; the public key i was trying to add was already used with 'work' Gitlab account and i received the said error upon trying to use the same key with 'personal' Gitlab account.

Solution - Add another public key on the same machine and use that with 'personal' gitlab account (both on same machine).

navigate to .ssh folder in your profile (even works on windows) and run command

ssh-keygen -t rsa

when asked for file name give another filename id_rsa_2 (or any other). enter for no passphrase (or otherwise). You will end up making id_rsa_2 and id_rsa_2.pub

use the command

cat id_rsa_2.pub

copy and save key in 'personal' Gitlab account.

create a file with no extension in .ssh folder named 'config'

put this block of configuration in your config file

Host           gitlab.com
HostName       gitlab.com
IdentityFile   C:\Users\<user name>\.ssh\id_rsa
User           <user name>


Host           gitlab_2
HostName       gitlab.com
IdentityFile   C:\Users\<user name>\.ssh\id_rsa_2
User           <user name>

now whenever you want to use 'personal' gitlab account simply change alias in git URLs for action to remote servers.

for example instead of using

git clone git@gitlab.com:..............

simply use

git clone git@gitlab_2:...............

doing that would use the second configuration with gitlab.com (from 'config' file) and will use the new id_rsa_2 key pair for authentication.

Find more about above commands on this link
https://clubmate.fi/how-to-setup-and-manage-multiple-ssh-keys/

Question 3

Gitlab can use your ssh-key in another account of your past projects for somehow - so, easiest way to solve this problem is to create new ssh-pair, add it to ssh-agent and add id_rsa2.pub to your gitlab account.

$ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"

When it ask:

Generating public/private rsa key pair. 
Enter file in which to save the key (/home/<NAME>/.ssh/id_rsa):

Please enter /home/<NAME>/.ssh/id_rsa2

$ ssh-add ~/.ssh/id_rsa2

Question 4

I got the same error because I already added this key to another account in gitlab.

Question 5

I tried everything already suggested and nothing worked. What ended up working for me was to copy the public key using a command rather than from a text editor (nano in my case):

pbcopy < ~/.ssh/id_rsa.pub

replacing, if necessary, id_rsa with my specific key name. The above command works on OSX. Other systems require a different command, and they are listed on the following page: http://doc.gitlab.com/ce/ssh/README.html.

Question 6

In my case I already had the public key added on another repo.

Fix:

On the same GitLab page (Settings -> Repository -> Deploy Keys)
Scroll down and click to the TAB "Privately accessible deploy keys"
Find your "Deploy key" in the list and click the Enable button

Then you are good to go.

Question 7

My SSH key was stored in an old Gitlab account, I removed it and problem solved.

Question 8

Text editor could be the problem. Try to open key file with Notepad, not Notepad++.

Also add "ssh-rsa " at the beginning of the key.

Question 9

Make a New Key

None of the above solutions worked for me so I backed up my old key and created a new one.

https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/

#osx10.12.6

Question 10

In my case, my public key must have somehow been attached to a specific repository.

I went back and deleted two old repositories and after that it allowed me to add the public key to my GitLab account without any problems.

Question 11

Add new ssh key The pervius ssh key probabley use by another user . When somone else use a ssh key you must get this error dint worry create a new ssh key and use theme.

Question 12

In the same gitlab setting page where you tried to add the deploy key scroll down a little bit and you shall find a tab called "Privately accessible deploy keys". Click it and you shall find the key you tried to add listed there. Just click "Enable" from next to it and it would work !

Question 13

If all these suggestions don't work:

First of all - don't deal with security keys being exhausted or in a hurry, not to do silly mistakes (my case).

Secondly - copy as GitLab deploy key public-key, not the private one (my case as well, despite well understand oh how keys work, just being in a hurry).

Question 14

In my case, I have not added an existing Deploy key to any other project before, and I am was not a member of any project.

In order to be able to enable the deploy key for a new project, you need to add yourself as a member to a project where this key has already been enabled.

Then in the New Project-Settings-Repository-Deploy keys-Privately accessible deploy keys list, you will see this key and the Enable button.

The answer is found in this documentation https://gitlab-docs.creationline.com/ee/user/project/deploy_keys/

In the Privately accessible deploy keys tab, you can enable a private key which has already been imported in a different project. If you have access to these keys, it's because you have either:

Previously uploaded the keys yourself in a different project.

You are a maintainer or owner of the other project where the keys were imported.

But if you have GitLab admin profile, it's enough even to have "User" privileges as a member for the project.