Manually connect to HTTPS git repositories with self-signed SSL certificates or other SSL issues

GITHUB ENTERPRISE GITLAB CE/EE

When connecting to a private HTTPS git repository, a problem may be caused by a custom (self-signed) certificate. See below for the steps to workaround this issue:

1. Configure the repository to disable verification of the SSL certificate:

   • Run git config http.sslVerify false in the repository folder.

     Example:

     cd project.git
     git config http.sslVerify false

2. On the Manage integrations page, click on Add integration.

   

3. Add the repository via Plain Git integration or Quick start on the Add integration page.

   

4. Enter Host URL and login credentials on the next screen. If 2FA is enabled on this account, enter PAT as the password.

5. Click Add integration and continue to the end to complete this setup.

   

6. If there’s an SSL verification error, click Ignore certificate errors and continue connection to proceed.

There are alternative solutions to make Java trust this certificate. Refer to the good articles from Atlassian which focuses on helping to resolve SSL Verification Issues:

1. Unable to Connect to SSL Services due to PKIX Path Building Failed

2. Connecting to SSL services

For related topics on connecting repositories from other git hosts, see Integration Guide.

Prev: Automatically connect to HTTPS git repositories with self-signed SSL certificates or other SSL issues

Next: Managing repository or integration configuration