Skip to content

Projection Signing Key Set Not Initialized

URI: https://docs.ankatech.co/errors/projection-signing-key-set-not-initialized
HTTP Status: 503 Service Unavailable

When you see this

The request reached the platform before its projection signing keys existed. The platform creates them by itself when it first starts, before it reports ready, so this answer is seen only while a fresh installation is still starting. Nothing was changed.

Common Causes

  • The environment was created moments ago and the administration service is still starting.

Response Example

HTTP/1.1 503 Service Unavailable
Content-Type: application/problem+json
Retry-After: <seconds>

{
  "type": "https://docs.ankatech.co/errors/projection-signing-key-set-not-initialized",
  "title": "Projection Signing Key Set Not Initialized",
  "status": 503,
  "detail": "The projection signing key set has not been initialized",
  "instance": "/api/v3/admin/platform/projection-signing-keys",
  "timestamp": 1798596000,
  "extensions": {
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Retry after the Retry-After interval.
  2. If it persists, check that the administration service reports ready and that the deployment key-protection backend is bound: the keys are sealed by it, and they cannot be created until it answers.

See Projection Signing Keys for the screen that lists, rotates and revokes these keys.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.