Gitlab - too many authentication errors for git

Question

My git command line has not been working since last week, all I remember is that I run the local folder in a managed version of git and add the remote git ref to it. Then my git cannot push or pull. He shows:

git clone [e-mail] :xxx/myproj.git myproj Cloning into 'myproj'... Received disconnect from 192.168.xxx.xxx: 2: Too many authentication failures for git fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. 

What is strange is that my version control in JetBrain Idea works fine, it can still pull out or click on this project, which cannot be used on the command line.

I add id_rsa.pub to gitlab before, and I add it again again, but it does not work.

Ssh debug info

ssh -v git @ gitlab.xxx.com

 OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 debug1: Reading configuration data /etc/ssh_config debug1: /etc/ssh_config line 20: Applying options for * debug1: Connecting to gitlab.xxx.com [192.168.xxx.xxx] port 22. debug1: Connection established. debug1: identity file /Users/abc/.ssh/id_rsa type -1 debug1: identity file /Users/abc/.ssh/id_rsa-cert type -1 debug1: identity file /Users/abc/.ssh/id_dsa type -1 debug1: identity file /Users/abc/.ssh/id_dsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH_5* debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA d7:11:d8:62:a6:30:1d:4a:c7:f1:99:bd:ba:54:de:60 debug1: Host 'gitlab.corp.com' is known and matches the RSA host key. debug1: Found key in /Users/abc/.ssh/known_hosts:127 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,hostbased debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn0 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn6 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn1 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn2 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn5 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn8 Received disconnect from 192.168.100.218: 2: Too many authentication failures for git abc@LiuzhMacbook :~/.ssh$ abc@LiuzhMacbook :~/.ssh$ ls authorized_keys id_rsa known_hosts tmp/ abc@LiuzhMacbook :~/.ssh$ rm known_hosts abc@LiuzhMacbook :~/.ssh$ ssh -v [e-mail] OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 debug1: Reading configuration data /etc/ssh_config debug1: /etc/ssh_config line 20: Applying options for * debug1: Connecting to gitlab.corp.com [192.168.100.218] port 22. debug1: Connection established. debug1: identity file /Users/abc/.ssh/id_rsa type -1 debug1: identity file /Users/abc/.ssh/id_rsa-cert type -1 debug1: identity file /Users/abc/.ssh/id_dsa type -1 debug1: identity file /Users/abc/.ssh/id_dsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH_5* debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA d7:11:d8:62:a6:30:1d:4a:c7:f1:99:bd:ba:54:de:60 The authenticity of host 'gitlab.corp.com (192.168.100.218)' can't be established. RSA key fingerprint is d7:11:d8:62:a6:30:1d:4a:c7:f1:99:bd:ba:54:de:60. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'gitlab.corp.com,192.168.100.218' (RSA) to the list of known hosts. debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,hostbased debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn0 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn6 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn1 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn2 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn5 debug1: Authentications that can continue: publickey,password,hostbased debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn8 Received disconnect from 192.168.100.218: 2: Too many authentication failures for git 

Answer 1

You can use a different ssh url to refer to the correct public / private key you want.
Add a file named config to your HOUSE /.ssh:

 Host mygitlab Hostname gitlab.xxx.com User git IdentityFile ~/.ssh/id_rsa.gitlab IdentitiesOnly yes 

And change your url:

 git clone mygitlab:xxx/myproj.git myproj 

This way you avoid the default ssh behavior, which presents all the keys for ssh to try.

Answer 2

In SourceTree try changing your SSH Client from PuTTY/Plink to Open SSH .

Answer 3

First of all, set your ssh keys.

If our keys are installed correctly, try restarting ssh-agent

 eval $(ssh-agent) 

You should see the PID of the process, and you will load the r keys.

To add your keys manually, use: ssh-add . This will load the keys from the default .ssh folder

Answer 4

runs on linux
The following worked for me (I'm using gitlab):

  eval $(ssh-agent -s) ssh-add ~/.ssh/<ssh_directory> ssh -T [e-mail] 

and in one command:

  eval $(ssh-agent -s) && ssh-add ~/.ssh/gitlab && ssh -T [e-mail] 

Answer 5

finally - a primitive reboot of the host machine works, but I would like to know what actually happens ...