Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
'SSL certificate problem: unable to get local issuer certificate' when trying to clone repos
See original GitHub issueDescription
[Cannot clone repositories]
Version
GitHub Desktop version: [1.0.11]
OS version: [Microsoft Windows [Version 10.0.17063.1000]]
Steps to Reproduce
- [Clone a Repository]
- [Choose a repository]
- [and so on]
Expected behavior: [Repository cloned]
Actual behavior: [Cloning into ‘path’… fatal: unable to access ‘url’: SSL certificate problem: unable to get local issuer certificate]
Reproduces how often: [100%]
Logs
2017-12-26.desktop.production.log
Additional Information
Issue Analytics
- State:
- Created 6 years ago
- Comments:23 (5 by maintainers)
Top Results From Across the Web
Unable to resolve "unable to get local issuer certificate" using ...
Go to remote repository's site. Ex: github.com, bitbucket.org, tfs.example... Click Lock icon on the upper left side and click Certificate ...
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 git...
Read more >SSL certificate problem: Unable to get local issuer certificate
Resolution #1 - Self Signed certificate · Ensure the root cert is added to git.exe's certificate store. · Tell Git where to find...
Read more >Git Bash: "Unable to get local issuer certificate" - ShellHacks
“Unable to get local issuer certificate” error usually happens when the Git server's SSL certificate is Self-Signed or it has been issued by...
Read more >Cant clone from GitHub : SSL certificate problem: unable to ...
sslbackend set to openssl , which means GitHub Desktop isn't using the Windows certificate store. Running the command git config --global http.
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 Free
Top 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
I go this error in VS2017 and solved it by opening Git bash and then $ git config --global http.sslBackend schannel. Thanks to https://stackoverflow.com/questions/16668508/how-do-i-configure-git-to-trust-certificates-from-the-windows-certificate-store
I solved it on windows 10 by enabling “Use the native Windows Secure Channel library” when (re-)installing git instead of “Use the OpenSSL library”