# CERTIFICATE_ALREADY_REGISTERED

Canonical page: https://docs.ovok.com/errors/certificate-already-registered

**HTTP 409.** Problem type: [`https://docs.ovok.com/errors/certificate-already-registered`](https://docs.ovok.com/errors/certificate-already-registered).

## What this means [#what-this-means]

The project has this client certificate registered already. Certificates are known by their SHA-256 fingerprint, so the same certificate cannot be registered twice. Nothing was changed.

## Troubleshooting [#troubleshooting]

1. List the project's certificates with `GET /v1/signals/certs`. The certificate is there under its `sha256`.
2. Register a new certificate instead if you meant to rotate. A renewed certificate has a different fingerprint.

## Retry safely [#retry-safely]

No retry is needed: the certificate is registered.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
