Answers: <p>This problem is caused when the person (admin) that tried to execute the pipeline replay had insufficient access to the repository they replayed it on. This can happen when the for example the pipeline is private and they're not member, but an admin hits the replay button. The admin's replay does not have the ability to download from the cache. <strong>This bug is reported as <a href="https://gitlab.com/gitlab-org/gitlab/-/issues/21700" rel="nofollow noreferrer">issue 21700</a> upstream.</strong></p>
  <p>For a temporary workaround, you may opt to make the repository public if possible. Then the admin can replay the job.</p>
  
Answers: CC BY-SA 4.0
Answers: 2023-02-07T22:30:05.850Z
Answers: 2023-02-07T22:36:10.267Z
Answers: 2023-02-07T22:36:10.267Z
Answers: Evan Carroll
Body: <p>Inside of one of my runner's logs, when I try to replay it, I'm getting the following error,</p>
  <pre><code>Reinitialized existing Git repository in /builds/users/repo/.git/
  remote: You are not allowed to download code from this project.
  fatal: unable to access 'https://acme.net/users/repo.git/': The requested URL returned error: 403
  </code></pre>
  <p>How can I resolve this error?</p>
  
Tags: <gitlab><gitlab-ci-runner>
Title: GitLab CI runner: remote: You are not allowed to download code from this project
UserDisplayName: Evan Carroll
ThreadText: # GitLab CI runner: remote: You are not allowed to download code from this project
  
  (Asked by: username_0 on 2023-02-07)
  
  Inside of one of my runner's logs, when I try to replay it, I'm getting the following error,
  
  ```
  Reinitialized existing Git repository in /builds/users/repo/.git/
  remote: You are not allowed to download code from this project.
  fatal: unable to access 'https://acme.net/users/repo.git/': The requested URL returned error: 403
  
  ```
  
  How can I resolve this error?
  
  **Tags:** gitlab, gitlab-ci-runner
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2023-02-07. Score: 3 | Accepted answer
  
  This problem is caused when the person (admin) that tried to execute the pipeline replay had insufficient access to the repository they replayed it on. This can happen when the for example the pipeline is private and they're not member, but an admin hits the replay button. The admin's replay does not have the ability to download from the cache. **This bug is reported as [issue 21700](https://gitlab.com/gitlab-org/gitlab/-/issues/21700) upstream.**
  
  For a temporary workaround, you may opt to make the repository public if possible. Then the admin can replay the job.
  
  
  ---
  
  