Fatal: unable to acess GIT SSl certificate problem: self signed
Asked by Nelson Faustino:

When trying to setup Bamboo to connect to our GIT repo, I receive the following error

```
fatal: unable to access 'https://xxxxxx:8443/scm/xxxx/xxxx.git/': SSL certificate problem: self signed certificate
```

We do use a selfsigned cert, however in bitbucket I was able to fix that with the keytool and adding the cert to bitbucket. How can I fix this in bamboo?


Answers:
author: Daniel Santos
body: > I believe i have added the public into the CACerts using the portecle app.

Assuming Bamboo have no **truststore** configured it should use **cacerts** from JAVA to get the public certificates.
> Not sure what you mean by GIT as a capability

Bamboo will use JGIT (a Java embedded client of git) instead of GIT from your terminal. As a consequence the configuration to avoid the SSL Verification will not take effect.

This is our doc on how to configure it: [Defining a new version control capability - Atlassian documentation](https://confluence.atlassian.com/bamboo/defining-a-new-version-control-capability-289277156.html).
> No, didn't no i had to?

You don't need to do it, but it would be a good test to check if the problem is related to the GIT client used by Bamboo and the server environment variables loaded so far.
> Yes

Good to know, that at least make sense if your configuration has already `http.sslVerify `option set to false.
> I ran the following if thats what you mean.

Yes, that is what I was talking about.[](https://confluence.atlassian.com/bamboo/defining-a-new-version-control-capability-289277156.html)**Please share**

1. the full stack trace of the error reported here.
2. is git capability configured?
3. try to run a script task with the git command you need, so we can validate that this is achievable from Bamboo.


author: Daniel Santos
body: Hello Nelson,

You will need to add the public certificate in Bamboo if you didn't do it yet and add the reference to cacerts in the git configuration.  

The same problem is described here: [Unable to clone Git repository due to self signed certificate - Atlassian Documentation](https://confluence.atlassian.com/fishkb/unable-to-clone-git-repository-due-to-self-signed-certificate-376838977.html). This document is for Fisheye, but the same procedure should fix Bamboo as well.

comments: author: Nelson Faustino
body: I did try using that app and exported the bitbucket pem then imported it into my cacerts but still have the same issue.


author: Daniel Santos
body: Some useful questions to more forward:

* Just to make sure, have you added the public certificate or the private one? (you need the public in Bamboo)
* Are you using GIT as a capability?
* Are you calling git commands from a script task?
* Is git working at the terminal, from outside Bamboo?
* Have you tried the git configuration suggested in the link I shared above?


author: Nelson Faustino
body: Responses in order. Just so you know, my issue is within bitbucket site and bamboo site when trying to link repositories.

I believe i have added the public into the CACerts using the portecle app.

Not sure what you mean by GIT as a capability

No, didnt no i had to?

Yes

I ran the following if thats what you mean.

    git config --global http.sslVerify false