Skip to main content
General·HTTP 403·API, CLI, FE

No repository access

connection_no_access

The Git connection exists, but it is not allowed to read this repository.

What this means​

The connection was installed for a chosen set of repositories, and this one is not among them.

How to fix it​

On your Git provider, open the connection's settings and add this repository to the ones it can read, then try again.

Retry behavior​

Retry after the connection's access has been changed.

How it appears in the response​

ComputeSphere returns errors as RFC 7807 Problem Details. The type field is the docs URL for this page — switch on code in your client.

{
  "type":    "https://docs.computesphere.com/errors/connection_no_access",
  "title":   "No repository access",
  "status":  403,
  "code":    "connection_no_access",
  "detail":  "The Git connection exists, but it is not allowed to read this repository.",
  "instance": "/v2/…",
  "request_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "trace_id":   null
}

The Content-Type header is application/problem+json. On field-level validation errors a non-empty errors[] array also appears, each entry carrying its own docs_url for the offending field.