Similar problems to this guy, who got no help and no suggestions in 5 months, which is troubling to me:
We have SSH clone and push working, but not HTTPS.
With Git 2.7.x on Windows clients:
X:\Temp\gitlab\project>git clone https://test-gitlab.ramsoft.biz/wpostma/personal1.git
Cloning into ‘personal1’…
fatal: unable to access ‘https://test-gitlab.ramsoft.biz/wpostma/personal1.git/’: SSL certificate problem: unable to get local issuer certificate
Watching the server logs with gitlab-ctl tail, we see this in the server Log:
> /var/log/gitlab/nginx/gitlab_error.log < 2016/04/26 13:21:25 [crit] 47733#0: *31 SSL_shutdown() failed (SSL: error:140E0197:SSL routines:SSL_shutdown:shutdown while in init) while SSL handshaking, client: 192.168.215.50, server: 0.0.0.0:443
Advanced degrees in Googling Error messages suggests from a stackoverflow post that the above is an OpenSSL bug, but not sure.
Workaround we know about is to type set GIT_SSL_NO_VERIFY=true before we do the git clone, but this is bad as it disables ALL SSL verifications.
Found some references to having to manually set up a chain of certificates for nginx to work:
Use an SSL Checker to verify your SSL Certificate is installed properly http://www.digicert.com/help/
If you are using a paid SSL (not self-signed) you are likely missing Intermediate certificates, which are required to fully validate an SSL certificate.
Unlike Apache, you cannot specify a Chain/Intermediate separately. With NGINX you need to create your own chain by concatenating your certificates.
$ cat www.example.com.crt bundle.crt > www.example.com.chained.crt
Read the full details under “SSL certificate chains” here: