As in the git version 2.5.0.windows.1 trying to clone the repository:
$ git clone https://gitlab1645.mydomen.com:8888/project/project-core.git
get the message:
Cloning into ‘project-core’ …
fatal: unable to access’ https://gitlab1645.mydomen.com:8888/ project / project-core.git / ‘: SSL certificate problem: unable to get local issuer certificate
How does it win?
Answer 1, Authority 100%
There are several options:
-
To use SSH when working with git
-
Disable checking ssl certificate in cloning
GIT_SSL_NO_VERIFY = true git clone / path / to / repo
-
Disable checking ssl certificate globally
git config --global http.sslVerify false
-
If the certificate is self-signed – find instructions on how to add a self-signed certificate in the trusted
.
Answer 2, authority 8%
Another option here
git config –global http.sslbackend schannel
This is the original, SSL disable a bad option.
The problem is that git by default using the “Linux” crypto backend.
Beginning with Git for Windows 2.14, you can now configure Git to use SChannel, the built-in Windows networking layer as the crypto backend. This means that you it will use the Windows certificate storage mechanism and you do not need to explicitly configure the curl Ca storage mechanism: https://msdn.microsoft.com/en-us/library/windows/desktop/aa380123 (v = vs.85) .aspx
Just execute:
git config –global http.sslbackend schannel
That should helps.
Using schannel is by now the standard setting when installing git for windows, also it is recommended to not checkout repositories by SSH anmore if possible, as https is easier to configure and less likely to be blocked by a firewall it means less chance of failure.