GitHub Enterprise - Fatal SSL Cert Error
See original GitHub issueDescription: Version 0.8.0 has a fatal error when connecting to a GitHub enterprise server. Rolling back to a previous version fixes this.
Error:
fatal: unable to access 'https://[GitHub Enterprise address]/[user]/Scripts.git/': SSL certificate problem: self signed certificate in certificate chain
(Redacted identifying information)
Version: GitHub Desktop version: 0.8.0
OS version: Windows 7 SP1
Steps to Reproduce:
- Try pushing/fetching from a GitHub enterprise server
Reproduces how often: 100%
Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Error: SSL certificate problem, verify that the CA cert is OK
This error means your CA root certificate is out of date. If your CA root certificate needs to be updated, you won't be...
Read more >Quick fix to Git's fatal 'unable to access SSL certificate' error
Here's a quick fix to the Git 'unable to access GitHub or GitLab' SSL certificate settings error when you attempt to clone from...
Read more >Unable to resolve "unable to get local issuer certificate" using ...
I am using Git on Windows. I installed the msysGit package. My test repository has a self signed certificate at the server.
Read more >SSL cerfrificaion problem: 'unable to get local issuer certificate'
The 'unable to get local issuer certificate ' is a common SSL error faced by devs trying to push, pull, or clone a...
Read more >Unable to clone Git repository due to self signed certificate
Please be advised disabling SSL verification globally might be considered a security risk and should be implemented only temporary. Resolution.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We updated Git from v2.13.0 to v2.14.1 as part of the update from 0.7.2 to 0.8.0, but both versions should be using the Windows Certificate Store (SChannel) to validate certificates. I thought our way of packaging Git was still valid, but maybe this release has regressed this.
@w60001 @AJ1701 could you open the problem repository in Git Shell and run this command:
If this makes fetching/pushing/pulling work then we can set this in the system configuration for our version of Git and get a new update out asap.
@AJ1701 @RussellAnderson thanks for confirming the fix - #2520 will go out for the next update and will address this at a system level for everyone.