Jenkins failed in running bower package with error
exit code of #128 fatal: unable to access
'https://github.com/metafizzy/fizzy-ui-utils.git/': Failed to connect
to github.com port 443: Timed out
It was working well before all the time. No package or version is changed but issue is replicating again & again. Server running jenkins is able to access "https://github.com/metafizzy/fizzy-ui-utils.git", no issue accessing site in https.
What is issue here?
Please help.
Turn out to be github changed something recently that broke this:
On February 22, 2018 19:00 UTC (11:00 am PST) GitHub discontinued
support for the cryptographically weak TLS 1.0 & 1.1 protocols and
only support connections with the TLS 1.2 protocol
See the GitHub Engineering blog post for more details about this change:
https://githubengineering.com/crypto-removal-notice/
Solution
Upgrading git client for windows on which jenkins build happens is the solution for the issue
Related
This was working 1 month back. But recently it is showing following error when I try to either sync or pull from repository.
Error: git.exe pull --progress -v --no-rebase "origin" fatal: unable to access getaddrinfo() thread failed to start
Also I have verified that I am not able to connect github.com. I mean when pinged to github.com it returns no response
I have viewed following threads. Answers / comments given in these threads are not working for me.
*Getting Access Denied while cloning using git clone command
fatal: unable to access <link> getaddrinfo() thread failed to start*
I am using Windows 10 Professional version and Visual Studio 2019
Community Edition.
I am accessing GIT repository from https://xxxx.visaulstudio.com/
Repository URL is HTTPS and not SSH
I have tried following solutions :
Delete credentials from windows credential manager
Uninstall GIT for Windows and installed latest one (2.26.2.1)
Removed GIT folder from location "C:\Program Files (x86)\Microsoft Visual
Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team
Explorer"
Verified Anti Virus (Quick Heal). There is no record or setting for blocking particular domain
5 There is no issue of firewall.
but none of these are working.
I saw following link and same is reported by multiple users. It seems to be issue with compatibility of Git Credential Manager with Azure Devops authentication
https://github.com/microsoft/Git-Credential-Manager-for-Windows/issues
Help is really appreciated.
I have created ssh key using the command ssh keygen and I have added the public key to my bitbucket account and then I have added the key to the ssh agent also, But when I tried to clone repo from bitbucket using sourceTree, I am getting the below Error.
Error: FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
and I know this is repeated question but those solution didn't worked for me, So please help.
Well, It was my mistake actually,
SSH Client type was set to PuTTY/Plink in my SourceTree Settings, So I changed it to openSSH and now that issue is no more.
Sorry & Thanks.
I am using SourceTree to access an enterprise GitHub server, and had the same issue all of a sudden start occurring to me even though it has been working fine for over a year and nothing had changed. Apparently, somehow my SSH Client Type was swapped to PuTTY/Plink. Switching it to openSSH again fixed the issue for me by going to Tools -> Options -> General -> then selecting OpenSSH as the SSH Client under the SSH Client Configuration section.
Changing the SSH Client type to openSSH in Source Tree - tools -> Options -> General solved this error for me.
(I posted the following to atlassian.com bug report)
We had the same issue. We noticed that the Pageant (in the icon tray) would not start.
For us it appears that our antivirus was blocking it somehow. Thus we do the following:
disabled the antivirus
uninstall SourceTree (SourcetreeEnterpriseSetup_3.4.6.msi)
installed SourceTree (SourceTreeSetup-3.4.6.exe)
reconfigured SourceTree
We noticed that Pageant was now running and ssh calls worked.
Reenabled the antivirus.
So far so good.
In my case, I was getting same error but the "pageant" program installed was very very old, but worked after updating it (via the putty installer). Credit to https://superuser.com/users/106302/fabian # https://superuser.com/a/404286/658383
I am trying to setup the jenkins running under our corporate proxy as our servers dont have direct access to internet.
However, it failed to connnect to internet to update plugins through proxy server.
Error logs:
ntlm authentication scheme selected
Aug 04, 2017 8:14:44 AM INFO org.apache.commons.httpclient.HttpMethodDirector processProxyAuthChallenge
Failure authenticating with NTLM <any realm>#proxy-server:8080
The proxy setup as below:
Please advise>
i am able to solve this problem by upgrading to the latest version 2.60.2
I have a fresh CentOS box, installed Tomcat 8.0 and Jenkins 2.5. After entering the secret key for a brand new installation, the next step Install suggested plugins or :Select plugins to install:. After clicking on Install suggested plugins I got an error saying
An error occurred during installation: Forbidden
I assume is related to folder permissions, the question is which one?
UPDATE: The jenkins log says
Found invalid crumb a711b93261896fb36a1d6ffbe163dca6. Will check remaining parameters for a valid one...
May 21, 2016 4:19:34 AM WARNING hudson.security.csrf.CrumbFilter doFilter
No valid crumb was included in request for /jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test. Returning 403.*
Thanks in advance.
If it's any help to anybody, I "fixed it" by restarting Jenkins http://jenkins:8080/restart, or whatever protocol, domain, and port. Then when I went back in it asked me for the secret key again, and then installed all the plugins successfully.
I have faced this problem before. It was because I was using a VPN. Once I closed the VPN, everything returned back to normal.
I was getting the same error when I was using Internet Explorer for JENKINS INSTALLATION on Windows 2019. I installed Chrome before trying again and the error went away!
I was facing this issue because I was using Internet Explorer. Switching the browser fixed the issue for me.
I faced this same issue, Alex's answer helped me.
Here's some addition to it:
I was running Jenkins on docker, so to restart it I had to do the following;
List all the running docker containers on the server:
docker container ls
Copy the container id for the Jenkins container
Restart the docker container for Jenkins using its id:
docker restart <jenkins-container-id>
Visit the URL for Jenkins again:
http://your-url:8080
Input your initial admin password, and then try setting up Jenkins again.
That's all.
I hope this helps
EDIT 2
Okay, turns out this has nothing to do with TFS or MSBuilder. This is entirely a problem with SonarQube. The SonarQube Service is the one who sends back a 401 (Unauthorized) status not TFS. Since I run 5.4 I have no clue as to how I specify a SonarQube user because in Jenkins both of those fields are greyed out.
I am using Jenkins as a Windows Service and about 2 hours ago the service made a successful build. Now, out of seemingly nowhere, Jenkins keeps reporting 401 (Unauthorized) no matter which build job I try to start.
They all start a SonarQube scanner first
Run MSBuild
In order for SonarQube to read the analysis I have to run a rebuild command
Run the End SonarQube analysis step and it collects the data to put on our SonarQube portal.
What I don't understand is that the last change I made to anything, was to go delete a file from an ASP project and now none of the jobs work, even those that have nothing to do with this ASP project. All the projects are stored on our Team Foundation Server (not locally hosted).
The only thing that really changed was that we wanted the IP of the Jenkins and SonarQube services to be accessible outside of the server they are hosted on so we made two sites on the local IIS and made a DNS to point at those. Reading into the error log I first see status 302 which is a redirection, before I reach 402. When I go to "Configure Jenkins" I am told that my proxy settings failed...or something along those lines.
Any idea what might cause this behaviour?
EDIT
Here is a part of the error log:
INFO: SCM changes detected in CSharp Build Job. Triggering #1
Apr 20, 2016 11:04:08 AM com.microsoft.tfs.core.config.httpclient.DefaultHTTPClientFactory logHTTPClientConfiguration
INFO: HttpClient configured for https://omitted.visualstudio.com/, authenticating as it#omitted.dk
Apr 20, 2016 11:04:10 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternal
INFO: SOAP method='GetRegistrationEntries', status=302, content-length=0, server-wait=1164 ms, parse=0 ms, total=1164 ms, throughput=0 B/s, uncompressed
Apr 20, 2016 11:04:11 AM com.microsoft.tfs.core.httpclient.HttpMethodDirector processWWWAuthChallenge
INFO: Failure authenticating with BASIC #omitted.visualstudio.com:443
Apr 20, 2016 11:04:11 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternal
INFO: SOAP method='GetRegistrationEntries', status=401, content-length=0, server-wait=578 ms, parse=0 ms, total=578 ms, throughput=0 B/s, uncompressed
Apr 20, 2016 11:04:11 AM com.microsoft.tfs.core.TFSTeamProjectCollection getServerDataProvider
WARNING: Error getting data provider
com.microsoft.tfs.core.exceptions.TFSUnauthorizedException: Access denied connecting to TFS server https://omitted.visualstudio.com/ (authenticating as it#omitted.dk)
Try to change the Server URL from https://omitted.visualstudio.com/ to https://omitted.visualstudio.com/DefaultCollection. And use Personal access tokens or Alternate credentials for User name and password. Check the screenshot below:
Okay, I have found the solution. It's so stupid I can't believe I didn't think of it.
In my SonarQube.Analysis.xml found at
...Jenkins\.jenkins\tools\hudson.plugins.sonar.MsBuildSQRunnerInstallation\MSBuild_2.0\SonarQube.Analysis.xml
I remembered that I had the username and password written and at some point I went and changed that in SonarQube from the default values to something else. That made all the builds break.