← Go back to Tor Project status

GitLab CI containers failures

April 20, 2026 at 11:58 AM UTC

GitLab

Resolved after 2d 23h 30m April 23, 2026 at 3:28 PM UTC

The GitLab Container Registry is refusing requests to GitLab CI pipelines between projects.

This started on Friday, when the GitLab 18.11 upgrade was deployed. We are hoping for a quick fix from upstream, but in the meantime, we need your help!

Normal GitLab operation should be unaffected. GitLab CI still works, it just fails with images from our own registry when accessed from personal projects.

We’ve found a workaround that requires you to report the failures to us. In tpo/tpa/team#42595, we ask that you write a new comment with the following information:

  • source project: failing project (e.g. group/failing_project)
  • registry project: project it is trying to pull from (e.g. tpo/tpa/base-images)
  • example failed job: URL of the failed job

For example, this was our first report:

You might be able to fix this yourself. If you have access to the “registry project” above, you can manually add the source project to the CI/CD job token allowlist of the registry project", by following:

  1. Settings
  2. CI/CD
  3. Job token permissions
  4. add the “source project” to the allowlist

You MUST keep track of that exception and remove it once this incident is resolved!

Last updated: April 23, 2026 at 11:15 AM UTC