Skip to content

Runner unable to fetch via https - Problem with the SSL CA cert

Summary

After upgrading to version 10.1 the runner fails to fetch the repsoitories. The initial cloning of the repository succeeds when the first CI job is executed. The issue is still present in 10.2.

Steps to reproduce

Setup a ssh runner and execute a CI job. The first job with the initial clone succeeds but all subsequent jobs fail during fetching.

Actual behavior

Runner fails during fetching the repository. See job log below. Also see https://forum.gitlab.com/t/fatal-unable-to-access-https-after-upgrade-to-10-1/11650.

Expected behavior

Runner should be able to fetch the repository as in version 10.0.

Relevant logs and/or screenshots

CI job log:

Running with gitlab-runner 10.2.0 (0a75cdd1)
  on gitserver (cf75516a)
Using SSH executor...
Running on vm1404 via gitserver...
Fetching changes...
HEAD is now at 4b8e35c Update .gitlab-ci.yml
fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@gitserver.domain/paul.jaehne/testpaul.git/': Problem with the SSL CA cert (path? access rights?)
ERROR: Job failed: Process exited with: 1. Reason was:  ()

Environment description

  • custom installation
  • Omnibus GitLab CE 10.2.0 on Ubuntu 16.04
  • executor ssh
  • Gitlab server uses a signed certificate, which is accepted by the browser

Used GitLab Runner version

Version:      10.2.0
Git revision: 0a75cdd1
Git branch:   10-2-stable
GO version:   go1.8.3
Built:        Wed, 22 Nov 2017 09:19:04 +0000
OS/Arch:      linux/amd64