Server in Gitlab.com: tls: failed to verify certificate: x509: certificate signed by unknown authority

My repo is hosted in Gitlab.com and I have a 2 job pipeline.

The first job runs on a Shared Runner, download some files with Gitlab CI API and make them artifacts. It works fine.

The second job is running on a Project runner on my own machine (runner on Linux, Docker executor).
As soon as this job begins, i get this error:

ERROR: Downloading artifacts from coordinator... error couldn't execute GET against https://gitlab.com/api/v4/jobs/..... : tls: failed to verify certificate: x509: certificate signed by unknown authority id=xxxx token=xxxx

Even with this error, i get the artifacts from the first job without problem.
I have done everything here but still, no luck to skip this error.

But, why should i import Gitlab’s certificates? Ιsn’t Gitlab.com considered trusted by default?

  • gitlab: 16.4.0
  • gitlab-runner: 16.3.0

This would mean issues with CA trust on the machine where your “other” GitLab Runner is running. It has nothing to do with GitLab.com or the document you have linked.

Usually, it’s enough to update/patch the Linux OS from it’s official repositories so latest CA trust bundle is on your machine.

1 Like