Actions
Task #2189
closedCant push changes to gerrit via ssh: "Too many authentication failures"
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Tags:
URL:
Description
Cant push to gerrit:
git push logerrit HEAD:refs/for/master Enter passphrase for key '/home/bjoern/.ssh/id_tdfgerrit2017': Received disconnect from 89.238.68.148 port 29418:2: Too many authentication failures Connection to gerrit.libreoffice.org closed by remote host. fatal: Could not read from remote repository.
This was with my old key, so I generated a new key as per https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/ ... which yields the above too.
Attaching output of "ssh -vvvv logerrit".
Updated by Guilhem Moulin over 7 years ago
I'm in a hurry so time for proper debugging at the moment, but there are these in the logs
[2017-03-17 16:22:02,917 +0000] fbd58cd6 Sweetshark - AUTH FAILURE FROM xxx.xxx.xxx.xxx no-matching-key
[2017-03-17 16:22:22,556 +0000] 5bddb8fc Sweetshark - AUTH FAILURE FROM xxx.xxx.xxx.xxx no-matching-key(time is UTC).
Updated by Bjoern Michaelsen over 7 years ago
- Status changed from New to Resolved
Eh, had too many keys on that machine. Solved it with:
IdentitiesOnly yes
in my .ssh/config (via https://superuser.com/questions/187779/too-many-authentication-failures-for-username)
Curious how ssh lets you authenticate, and then tells you "nah, you wont get in, that was too many keys" afterwards.
Updated by Beluga Beluga about 5 years ago
- Status changed from Resolved to Closed
Actions