Really sorry to hear you're having trouble again. As mentioned by @that-pat earlier in this thread, I think it would be good for you to reach out to private support so we can collaborate with you to troubleshoot the issue further.
Since we need to do some deeper individual troubleshooting, would you mind submitting a help request in our help portal so that we can follow up with you and get some additional inforomation? You can point at this thread for background information and it would be helpful to know what version of Windows you're using, what git client or clients you've encountered this problem with, and whether you're operating on a personal network or a company network.
Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!
Thank you for your response. I did submit a help request when the problem first arose. I was contacted again by Stacey Burns this morning to see how everything was working. I let her know that unfortunately the issue had returned. She has currently taken the problem to her team to discuss the next steps.
I also included a link to this thread because I think it is important to realize that the problem is with different users across different Windows platforms and my network is not the problem because others in the office are not having a problem. Also, there does not seem to be a problem on Macs, so I am theorizing the problem is with TortoiseGit.
I was able to pull again last week after my IT deleted and recreated a new GIT account, then cloned all of my files and moved them to a different directory. This worked well for a few days last week. However, when I came in this morning after the long weekend.... it is back to saying:
"SSL certificate problem: self signed certificate in certificate chain"
@git did not exit cleanly (exit code 1) (578 ms @ 5/29/2018 10:12:11 AM)
My setup at home worked briefly but then this last weekend I also was back to having the "self signed" error. I was trying to decide what to do when I saw your post. If you are opening a help ticket please post here if you get a good resolution, I don't want to open a duplicate ticket. I'm hoping there's one underlying problem.
thanks - Dave
@daveg-geokon, I did open a help request when I first had the issue. I have tried the things they suggested and have yet to come up with a solution. I sent her a link to this thread for reference and she is asking her team for the next steps. I will let you know as soon as I have a solution.
I am having this problem too. I am not on a corporate network.
$ git --version
git version 2.17.0.windows.1
$ git credential-manager version
Git Credential Manager for Windows version 1.16.1
atal: unable to access 'https://github.com/Synaccord/synaccord.git/': schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.
I just updated to the latest version of windows 10 and .NET and I am still having this problem.
I really appreciate that you want to prevent opening duplicate tickets for our support team. That's super considerate of you. However, in this case, I would definitely recommend opening up an individual support case as well.
The more people who open a support case about this issue, the better we can look for patterns in network styles, Git versions, Git tools, Operating System versions, etc. The more information we have, the quicker we can norrow this down.
We've been analysing the information that we've gotten from a few different reports and I have some additional information.
If you are using the Kaspersky anti-virus with Web Anti-Virus enabled, this seems to install a Kaspersky certificate which causes problems when connecting to GitHub in this way. To solve this problem, you can try the following steps:
If you don't have Kapersky or if this doesn't fix your problem, please follow these instructions and add the output to your open support cases:
openssl s_client -showcerts -connect github.com:443and collect the output
I know this problem is extremely frustrating, so I appreciate your patience as we try to narrow down all of the variables in play with this situation.
Many thanks! Turning off Web Anti-Virus in Kaspersky did the trick. Was it a recent change in Kaspersky or a recent change in GitHub that caused the problem? I see why it was so difficult for you to debug, since for those of us for whom that was the problem didn't think to tell you we were using Kaspersky. I assume the problem comes from some recent change to Kaspersky, not some recent change to GitHub, right?
It's hard to say for certain, but GitHub has made no recent changes that should have caused this impact, but there was changes to Git for Windows which allows for Git to use SChannel instead of OpenSSL for managing certificates. This could also be a recent change with Kaspersky's offerings and how they manage their certificates. Sorry that I can't be more specific at this time.
I learned how to make Kaspersky permit connections to github.com. See this link:
Apparently the issue is that Kaspersky can't trust certain kinds of encrypted transmissions and you have to specify sites you trust such as github.com.