Downloading artifacts from coordinator fails status=403 Forbidden token=-id

GitLab CI/CD
,
1

Problem to solve

ERROR: Downloading artifacts from coordinator… forbidden host=cdn.artifacts.gitlab-static.net id=id responseStatus=403 Forbidden status=403 Forbidden token=token on self hosted runner

  • Downloading job artifacts became impossible after Access token had been revoked on May 14
  • successful package job
Runtime platform  arch=amd64 os=linux pid=464950 revision=44feccdf version=17.0.0
./target/debug-infra.jar: found 1 matching artifact files and directories 
Uploading artifacts as "archive" to coordinator... 201 Created  id=6901779193 responseStatus=201 Created token=glcbt-65

image
image1084×767 136 KB

  • failed build job
ERROR: Downloading artifacts from coordinator... forbidden  host=cdn.artifacts.gitlab-static.net id=6901779193 responseStatus=403 Forbidden status=403 Forbidden token=glcbt-65
FATAL: permission denied

image
image1093×590 92.7 KB

Steps to reproduce

  • repo with sample app

  • pipeline

stages:
  - test
  - package
  - build

cache:
  key: maven
  paths:
    - .m2/repository/

variables:
  MAVEN_OPTS: >-
    -Dmaven.repo.local=$CI_PROJECT_DIR/.m2/repository
  MAVEN_CLI_OPTS: >-
    --batch-mode 
    --errors 
    --fail-at-end
    --show-version

test:
  stage: test
  script:
    - mvn $MAVEN_CLI_OPTS test

package:
  stage: package
  needs:
    - package
  cache:
    key: maven
    paths:
      - .m2/repository/
  script:
    - mvn $MAVEN_CLI_OPTS clean package
  artifacts:
    paths:
      - ./target/demo-app.jar
    expire_in: 1 hour

build:
  stage: build
  needs:
    - package
  variables:
    DOCKER_USER: demo
    IMAGE_NAME: debug-app
    CONTAINER_IMAGE: ${DOCKER_USER}/${IMAGE_NAME}:${CI_COMMIT_SHORT_SHA}
    IMAGE_TAG: latest
  script:
    - docker build  -t ${CONTAINER_IMAGE} .
    - docker tag ${CONTAINER_IMAGE} ${DOCKER_USER}/${IMAGE_NAME}:${IMAGE_TAG}

Which troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

  • Update runner binary to v17.0.0
  • reregister the runner

Versions

Please select whether options apply, and add the version information.

Versions

  • GitLab (Web: /help or self-managed system information): v17.0.0
  • GitLab Runner, if self-hosted (Web /admin/runners or CLI gitlab-runner --version): 17.0.0
1 Like
2

We are experiencing the same issue. All of a sudden, it started failing yesterday and we didn’t change any configuration.

We also use a self-hosted runner. Also updated it to 17.0.0. Re-re-re-registered it over and over. And still the same issue.

3

@zubrik I just found a solution: I changed the geographical location of my runner. I couldn’t see a reason why it would suddenly fail apart from some “security policy” change. We use Hetzner and our runner was running in Nuremberg (Germany). We changed it to Falkenstein (Germany) and it could download the artifacts!

4

Having exactly the same problem.
gitlab runner v17.0.0

Trying to get artifacts between pipelines by needs:project feature.

And this is certainly not related to Artifact downloads fail with certain CI_JOB_TOKEN values (#29193) · Issues · GitLab.org / gitlab-runner · GitLab. As token is usual.

1 Like