Upgraded Jenkins to 2.332.1 and a few plugins to try to stay up to date. Now getting the following error: `Failed to connect to repository : Command “/usr/bin/git ls-remote -h git-repo-link HEAD” returned status code 128: stdout: stderr: ssh_exchange_identification: Connection closed by remote ho…

[image] DappleZapple: I can connect to my repo without problem from command line by cloning and/or running ssh -T git@repo-url Credentials Plugin v2.6.1 Git Plugin v4.11.0 Git Client Plugin v3.11.0 GIT Server Plugin v1.10 Any help besides working through hours of manually downgrades is grea…

[Screen Shot 2022-03-31 at 10.03.03 PM] All plugins are fully up to date. I do get this message with the Credentials plugin. I am on the latest stable jenkins version 2.332.1 Still having the same issue sadly. Do I need to downgrade the version of Jenkins that I am on?

I’m not aware of anything in the upgrade to 2.332.1 that would break ssh credentials, so long as you followed the instructions in the upgrade guide and updated all plugins. Are you certain that the credential you’re using in the Jenkins job definition is the same credential that is being used in th…

I have created new credentials in the UI to make sure the right private key was being used within the job and am still experiencing this problem. I am on CentOS 7.4. I can revisit permissions. I can see that the jenkins user has ownership and access to the ssh directory and the private key within t…

[image] DappleZapple: I am on CentOS 7.4. I don’t know if that’s the cause, but CentOS 7.4 is a very old version of CentOS 7. The current version is CentOS 7.9. [image] DappleZapple: All plugins are up to date … only message I have is the screenshot I posted above that relates to the Cr…

Thank you for your help. I am going to keep working on debugging. What has been really odd is that when I ssh onto the host and change user to the jenkins user I can clone and connect to the repo no problem. The second I try to run ssh -T git@repo-url in an execute shell I get ssh_exchange_identific…

I have created brand new ssh username and private key credentials using the Jenkins UI using a private key I know connects to my repo properly. When setting up my repo in a job under Source Code Management, Git refuses to connect to my repository properly. Are there any logs that I can look at for …

You may find this technique helpful [image] How to trace git connections? Issue Our git connections are failing but the error does not give enough information We need to see the process to connect to our git server Environment CloudBees CI (CloudBees Core) on modern c... …

Thanks Mark. That didnt provide too much more information. Atleast not much that appears to be all that helpful unfortunately. I am beginning to consider opening a bug report with Jenkins for continued support working through this.

LOL … I opened a bug report and it looks like it auto assigned to you Mark… Apologies for the redundancy, I just dont know where else to turn for help working past this.

Failed to connect to git repository after upgrade to Jenkins 2.332.1 with Git Source Code Management

Using Jenkins Ask a question

Topic		Replies	Views
Bitbucket connection fails after upgrade from 2.263.1 to 2.387.1 Using Jenkins question	9	1916	June 23, 2023
Timeout connecting to GitHub Ask a question	11	9499	April 4, 2022
Projects running fine but source codes all have a failure credentials error Ask a question question	1	799	November 13, 2024
Built-In Node Not Working After Plugin Upgrades Ask a question question	5	140	May 27, 2025
ERROR: Error fetching remote repo 'origin' Failed to setup credentials Ask a question	4	1984	October 11, 2024

Failed to connect to git repository after upgrade to Jenkins 2.332.1 with Git Source Code Management

Related topics