Self-hosted GitLab / GitHub Enterprise / internal Jenkins / corporate certificate
This page is generated from docs/guide.en.md · Edit this page on GitLab
If the API fails with UNABLE_TO_GET_ISSUER_CERT_LOCALLY or unable to get local issuer certificate (an internal CA unknown to Node):
- the clean way: export the CA (the full chain up to the root) and point
GITLAB_CA_CERT=/path/ca.pemat it (orGITHUB_CA_CERTfor a GitHub Enterprise instance,JENKINS_CA_CERTfor an internal Jenkins); - troubleshooting:
GITLAB_INSECURE_TLS=1/GITHUB_INSECURE_TLS=1/JENKINS_INSECURE_TLS=1.
This is the common case with Jenkins: an internal server is almost always served by a certificate a freshly installed Node does not know. The Jenkins tab's message names both variables directly — the pinned CA first, disabling the check second.
The three settings are independent: pinning your internal GitLab's CA changes nothing for calls to github.com or to your Jenkins. For the clone, git has its own store: either GIT_CLONE_SSH=1 (an SSH key), or the settings above are applied to git as well.