GitLab CE Runner Certificate doesn't provide parent URL: exiting the loop

Summary

Hi, we have GitLab CE on a AWS EC2 Instance with an LB with HTTPS. We just created a GitLab Runner on Ubuntu (EC2) and we registered the instance to our GitLab. When we try to run some pipelines we always get the next error:

Feeding runners to channel                          builds=0
Checking for jobs... nothing                        runner=11dbc741
^[[AFeeding runners to channel                          builds=0
Checking for jobs... nothing                        runner=11dbc741
Feeding runners to channel                          builds=0
Checking for jobs... nothing                        runner=11dbc741
Feeding runners to channel                          builds=0
Checking for jobs... received                       job=202 repo_url=https://ourgitlabinstance/ucrea/deploy/ucrea.git runner=11dbc741
Processing chain                                    chain-leaf=[0xc00047d180 0xc00047d700 0xc00024d080] context=certificate-chain-build
Certificate doesn't provide parent URL: exiting the loop  Issuer=Amazon Root CA 1 IssuerCertURL=[] Serial=143266978916655856878034712317230054538369994 Subject=Amazon Root CA 1 context=certificate-chain-build
Processing chain                                    chain-leaf=[0xc00047d180 0xc00047d700 0xc0000acb00 0xc0005e6000] context=certificate-chain-build
Certificate doesn't provide parent URL: exiting the loop  Issuer=Starfield Services Root Certificate Authority - G2 IssuerCertURL=[] Serial=0 Subject=Starfield Services Root Certificate Authority - G2 context=certificate-chain-build
Processing chain                                    chain-leaf=[0xc00047d180 0xc00047d700 0xc0000acb00 0xc0000ad080 0xc0005c5180] context=certificate-chain-build
Certificate doesn't provide parent URL: exiting the loop  Issuer= IssuerCertURL=[] Serial=0 Subject= context=certificate-chain-build
Failed to requeue the runner                        builds=1 runner=11dbc741
Running with gitlab-runner 13.4.1 (e95f89a0)        job=202 project=139 runner=11dbc741
  on GitLab Runner 11dbc741                         job=202 project=139 runner=11dbc741
Preparing the "shell" executor          job=202 project=139 runner=11dbc741
Shell configuration: environment: []
dockercommand:
- sh
- -c
- "if [ -x /usr/local/bin/bash ]; then\n\texec /usr/local/bin/bash --login\nelif [
  -x /usr/bin/bash ]; then\n\texec /usr/bin/bash --login\nelif [ -x /bin/bash ]; then\n\texec
  /bin/bash --login\nelif [ -x /usr/local/bin/sh ]; then\n\texec /usr/local/bin/sh
  --login\nelif [ -x /usr/bin/sh ]; then\n\texec /usr/bin/sh --login\nelif [ -x /bin/sh
  ]; then\n\texec /bin/sh --login\nelif [ -x /busybox/sh ]; then\n\texec /busybox/sh
  --login\nelse\n\techo shell not found\n\texit 1\nfi\n\n"
command: bash
arguments:
- --login
passfile: false
extension: ""
  job=202 project=139 runner=11dbc741

Steps to reproduce

curl -L https://packages.gitlab.com/install/repositories/runner/gitlab-runner/script.deb.sh | sudo bash
export GITLAB_RUNNER_DISABLE_SKEL=true; sudo -E apt-get install gitlab-runner
sudo gitlab-runner register
gitlab-runner --debug run

concurrent = 1
check_interval = 0

[session_server]
  session_timeout = 1800

[[runners]]
  name = "GitLab Runner"
  url = "https://ourgitlabserver/"
  token = "ourtoken"
  executor = "shell"
  [runners.custom_build_dir]
  [runners.cache]
    [runners.cache.s3]
    [runners.cache.gcs]
    [runners.cache.azure]

What is the current bug behavior?

The pipeline freeze with this info:

What is the expected correct behavior?

Connect correctly with our EC2 Instances under HTTPS LoadBalancer.

Other Info

Server Runner:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"
NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"

Runner Version:

Version:      13.4.1
Git revision: e95f89a0
Git branch:   13-4-stable
GO version:   go1.13.8
Built:        2020-09-25T20:03:43+0000
OS/Arch:      linux/amd64