git clone https/ssl error [duplicate]

Question

I have installed the ssl certificate and key in my git server. But am getting error when i try to clone via https from my mysysgit. Earlier it was working fine with http. Unable to identify where it is failing

$ git clone https://server.name/git/testing.git
Cloning into 'testing'...
* Couldn't find host server.name in the _netrc file; using defaults
* About to connect() to server.name port 443 (#0)
*   Trying server.name...
* Adding handle: conn: 0x274fd60
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x274fd60) send_pipe: 1, recv_pipe: 0
* Connected to server.name(server.name) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: C:\Users\user1\AppData\Local\Programs\Git/bin/curl-ca-bundle.crt
  CApath: none
* SSL certificate problem: self signed certificate
* Closing connection 0
fatal: unable to access 'https://server.name/git/testing.git/': SSL certificate problem: self signed certificate

This has been marked as duplicate of the question relating to self-signed certificates. However, this can happen also with non self-signed certificates when an intermediate certificate is not registered on the server. Please, see: bugs.debian.org/cgi-bin/bugreport.cgi?bug=787281 The explanation: nginx.org/en/docs/http/configuring_https_servers.html#chains And the possible solution (with nginx): futurestud.io/tutorials/… — jplandrain
– jplandrain, Commented Nov 22, 2018 at 15:41

BuZZ-dEE · Accepted Answer · 2015-10-13 09:07:38Z

84

If you are getting an error while doing a git clone, then above needs to be changed to:

git config --global http.sslVerify false

edited Oct 13, 2015 at 9:07

BuZZ-dEE

7,15316 gold badges75 silver badges105 bronze badges

answered Dec 20, 2013 at 10:36

Pradeep S

2,3472 gold badges16 silver badges6 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Travis Reeder Over a year ago

You should probably never do this globally like this. Do it on a per repo basis without the --global.

Alex KeySmith Over a year ago

Agreed Travis the --global poses a significant security risk.

qneill Over a year ago

See the other question/answer stackoverflow.com/questions/11621768/… for how to do this on a per-command basis: git -c http.sslVerify=false clone . . .

EsmaeelE Over a year ago

Works for: fatal: unable to access 'https://github.com/somerepo.git/': Problem with the SSL CA cert (path? access rights?) `

VonC · Accepted Answer · 2018-12-19 09:07:54Z

25

You might have to disable the certificate verification in your case:

cd /path/to/repo
git config http.sslVerify false

(as in "Git: ignore a self signed certificate")

The other option, similar to "Unable to clone Git repository due to self signed certificate" would be to import that certificate into git.

That is: copied it at the end of the file /path/to/git/bin/curl-ca-bundle.crt.

I would not advise git config --global http.sslVerify false, as that would disable certificate verification for all local repositories.

edited Dec 19, 2018 at 9:07

answered Oct 1, 2013 at 11:15

VonC

1.4m568 gold badges4.8k silver badges5.7k bronze badges

3 Comments

Aguid Over a year ago

I got => fatal: not in a git directory. What does meaning ?

VonC Over a year ago

@Aguid It means you have not executed that command in a local git repository (a folder with a .git subfolder in it)

VonC Over a year ago

@Aguid True, but not recommended. See my edited answer.

Andrey Korneyev · Accepted Answer · 2014-10-27 09:28:21Z

4

Check your .gitconfig file.

If you've found the following line, Remove it!

[http]
sslCAinfo = /bin/curl-ca-bundle.crt

It worked for me.

edited Oct 27, 2014 at 9:28

Andrey Korneyev

26.9k16 gold badges73 silver badges72 bronze badges

answered Oct 27, 2014 at 9:05

madholic

661 bronze badge

Collectives™ on Stack Overflow

git clone https/ssl error [duplicate]

3 Answers 3

4 Comments

3 Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

4 Comments

3 Comments

Comments

Linked

Related