Jenkins Failed to connect to repository

Question

I m trying to connect jenkins on a github repo   When I specify the Repo URL jenkins return the following error message       Failed to connect to repository   Command  git ls-remote -h git github com adolfosrs jenkins-test git HEAD  returned status code 128    stdout    stderr  Host key verification failed    fatal  Could not read from remote repository    Please make sure you have the correct access rights   and the repository exists    When using the HTTPS    Url jenkins returns      Failed to connect to repository   Failed to connect to   https   github com adolfosrs jenkins-test git  status   407    I could successfully clone the repo at the same machine where jenkins is running and I also run the git ls-remote -h git github com adolfosrs jenkins-test git HEAD command  So I have the right SSH at github

User · Answer

Make sure that the RSA host key and the IP of the bitbucket server is added to the 'known hosts' file. The contents should look like

bitbucket.org,xx.xx.xx.xx ssh-rsa host_key

Remember to change ownership to Jenkins for all the files in /var/lib/jenkins/.ssh/

User · Answer

Check with below settings  That always work for me   Jenkins Configuration     1  Check whether git executable is appropriately specified   2  Provide SSH repository link git blahblah   3  Under credentials    Select Username and Authentication key  go to your server  Generate SSH keys ssh-keygen    Copy keys to JENKINS HOME  ssh  You should be able to connect to your GIT repository from Jenkins

User · Answer

In our case git had to be installed on the Jenkins server

User · Answer

I had the exact same problem  The way I solved it on Mac is this    Switch to jenkins user  sudo -iu jenkins  Run  ssh-keygen  Note - You are creating ssh key pairs for jenkins user now  You should see something like this   Enter file in which to save the key   Users Shared Jenkins  ssh id rsa    Keep pressing Enter for default value till end Run the command showing in the Jenkins error message  on your teminal  eg    git ls-remote -h git github com adolfosrs jenkins-test git HEAD   You will be asked if you want to continue  Say yes The Github repo will be added to your known hosts file in    Users Shared Jenkins  ssh  Go back to Jenkins portal and try your Github SSH url It should work  Good Luck

User · Answer

In my case I resolved this issue by    clicking button Add which is next to the  Credentials  text adding credentials  login and password  selecting these credentials on the popup menu  which is on the left of the Add button waiting for a couple of seconds   My environment was Jenkins installed in the Windows  The UI question was why the warning was placed before the tool to resolve it

User · Answer

This is a very tricky issue - even if you re familiar with how things are working in https with certificates  OTOH if you see my workaround  it seems very logical     If you want to connect to a GIT repository via http s  from shell  you would make sure to have the public certificate stored  as file  on your machine  Then you would add that certificate to your GIT configuration     git config  --global  http sslCAInfo  certificate     replace  certificate  with the complete path name of the PEM file     For shell usage you would as well e g  supply a   netrc  provding your credentials for the http-server login  Having done that  you shall be able to do a  git clone https        without any interactive provisioning of credentials   However  for the Jenkins-service it s a bit different     Here  the jenkins process needs to be aware of the server certificate - and it doesn t use the shell settings  in the meaning of the global git configuration file   gitconfig    P  What I needed to do is to add another parameter to the startup options of Jenkins          -Djavax net ssl trustStore  keystore         replace  keystore  with the complete path name like explained below     Now copy the keystore file of your webserver holding the certificate to some path  I know this is a dirty hack and not exactly secure    and refer to it with the  -Djavax net ssl trustStore   parameter   Now the Jenkins service will accept the certificate from the webserver providing the repository via https  Configure the GIT repository URL like     https   yourserver com your-repositorypath   Note that you still require the   netrc  under the jenkins-user home folder for the logon     Thus what I describe is to be seen as a workaround     until a properly working credentials helper plugin is provided  IMHO this plugin  in its current version 1 9 4  is buggy   I could never get the credentials-helper to work from Jenkins no matter what I tried     At best I got to see some errors about the not accessible temporary credential helper file  etc  You can see lots of bugs reported about it in the Jenkins JIRA  but no fix     So if somebody got it to work okay  please share the knowledge        P S   Using the Jenkins plugins in the following versions   Credentials plugin 1 9 4    GIT client plugin  1 6 1    Jenkins GIT plugin 2 0 1

User · Answer

The problem was that somehow I created the ssh files with the root user  So the files owner was root    The solution was just change the ownership to the jenkins user    chown jenkins id rsa pub  chown jenkins id rsa

User · Answer

I faced a similar issue when I tried to connect jenkins in my Windows server with my private GIT repo  Following is the error returned in the source code management section of Jenkins job  Failed to connect to repository   Command  quot git exe ls-remote -h ssh   git my server repo git HEAD quot  returned status code 128  stdout  stderr  Load key  quot C  Windows TEMP ssh4813927591749610777 key quot   invalid format  git my server  Permission denied  publickey   fatal  Could not read from remote repository  Please make sure you have the correct access rights and the repository exists   This error is thrown because jenkins is not able to pick the private ssh key from its user directory  I solved this in the following manner Step 1 In the jenkins job  fill up the following info under Source Code Management  Repositories Repository URL  ssh   git my server repo git Credentials  -none-  Step 2 In my setup jenkins is running under local system account  so the user directory is C  Windows System32 config systemprofile  This is the important thing in this setup that is not very obvious   Now create ssh private and public keys using ssh-keygen -t rsa -C  quot key label quot  via git bash shell  The ssh private and public keys go under  ssh directory of your logged in user directory  Just copy the  ssh folder and paste it under C  Windows System32 config systemprofile Step 3 Add your public key to your GIT server account  Run the jenkins job and now you should be able to connect to the GIT account via ssh from jenkins

User · Answer

In my case  I edited the known hosts file with root user  So it changed the file ownership to root and jenkins user started throwing  git github com xxxxxx xxxx git HEAD  returned status code 128  stdout  stderr  Host key verification failed  error while cloning git image  Reverting the ownership resolved the issue

User · Answer

On Ubuntu  placed your id rsa and id rsa pub files in  var lib jenkins  ssh  Make Jenkins own them sudo chown -R jenkins  var lib jenkins  ssh   Make sure that Jenkins key is added as deploy key with RW access in GitHub  or similar  - use the id rsa pub key for this   Now everything should jive with the SCM Sync Plugin

User · Answer

Let me add here that one very minor issue that could generate this type of error is the missing  git extension in the repository URL  Ensure you enter the fully qualified URL ending with  git  I use bitbucket so what I do do is do click   clone  and the fully qualified URL is automatically generated for me  There is a similar approach with github

User · Answer

Not mentionned here so far  but this can come also from stash  We encountered the same issue  the root cause for our problem was that the stash instance we use for jenkins did crash   Restarting stash solved it in our case

User · Answer

Jenkins runs as another user  not as your ordinary login  So  do as this to solve the ssh problem    Log on as jenkins su jenkins  you may first have to do sudo passwd jenkins to be able to set the password for jenkins  I couldn t find the default     Generate ssh key pair  ssh-keygen Copy the public key  id rsa pub  to your github account  or wherever  Clone the repo as jenkins in order to have the host added to jenkins known hosts which is neccessary to do  Now you can remove the cloned repo again if you wish

[git] Jenkins: Failed to connect to repository

Examples related to git

Examples related to github

Examples related to ssh

Examples related to jenkins