FATAL: permission denied

gitlab-ci-multi-runner 1.1.3 (a470667)
Using Docker executor with image node ...
Pulling docker image node ...

Running on runner-8a2f473d-project-1105238-concurrent-0 via runner-8a2f473d-machine-1461385085-d9cc10e5-digital-ocean-4gb...
Cloning repository...
Cloning into '/builds/scturtle/connectfour'...
.............

$ npm install -g elm
..............

$ LANG=C.UTF-8 elm-make --yes Main.elm --output public/index.html
Downloading circuithub/elm-array-extra
Downloading elm-lang/core
Packages configured successfully!
Success! Compiled 33 modules.
Successfully generated public/index.html

Uploading artifacts...
public: found 2 matching files                     
ERROR: Uploading artifacts to coordinator... forbidden  id=1168227 token= vpDmDtz
FATAL: permission denied                           

ERROR: Build failed: exit code 1

cc @tmaczukin

Milestone changed to v1.2

This happened on GitLab.com? Could you post the date and time of this - I would try to search what was the problem.

There is a 403 Forbidden response from the artifacts upload API endpoint. This could happen if:

• artifacts are not enabled (if this is GitLab.com then this is not the case),
• build token is not valid,
• build is not in running state,
• build have been erased.

It's hard to say what happened here.

Milestone changed to v1.3

@scturtle Can you check if this still happens?

@ayufan Same error. See https://gitlab.com/scturtle/connectfour/builds/1923659.

Milestone changed to %v1.4

Same error with custom gitlab server. Gitlab version: 8.9.4, runner version: 1.3.2.

How can I check if artifacts are enabled?

You can check that in Admin Area in Application Settings.

@ayufan I've Gitlab 8.9.4 and unfortunately I can't find artifact-enabling option in Application Settings page. The only option that contains word artifact is Maximum artifacts size (MB) in section Continuous Integration and it has value 100 Mb.

Then artifacts should be enabled by default.

Could you try newer version of runner? It shows more information when uploading artifacts.

I have got the same issue

ERROR: Uploading artifacts to coordinator... forbidden  id=32 responseStatus=403 Forbidden token=UQqMVSxh
FATAL: permission denied                           

ERROR: Build failed: exit status 1

I have resolved it, edit nginx.conf, pass_proxy http://gitlab-workhorse (/var/opt/gitlab/gitlab-workhorse/socket)

@ltz1990 In my configuration gitlab installed on different host that nginx, so I've specify pass_proxy via http port (not via unix socket). Could you show your location dircetive for this pass_proxy (or whole location section)? Thanks!

@alexiss When i specify pass_proxy via http port which is 8080, i have got this error

ERROR: Uploading artifacts to coordinator... forbidden  id=32 responseStatus=403 Forbidden token=UQqMVSxh
FATAL: permission denied                           

ERROR: Build failed: exit status 1

and then i have changed my pass_proxy via unix socket, it works well.

upstream gitlab-workhorse {
  server unix:/var/opt/gitlab/gitlab-workhorse/socket;
}
...others...
  location / {
    proxy_redirect          off;

    proxy_http_version 1.1;

    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto http;

    proxy_pass http://gitlab-workhorse;
  }

you can find this section in gitlab's nginx.conf (/var/opt/gitlab/nginx/conf/gitlab-http.conf)

Status changed to closed

mentioned in issue #2629 (closed)