# SIGNALS_MTLS_CERTIFICATE_UNKNOWN

Canonical page: https://docs.ovok.com/errors/signals-mtls-certificate-unknown

**HTTP 403.** Problem type: [`https://docs.ovok.com/errors/signals-mtls-certificate-unknown`](https://docs.ovok.com/errors/signals-mtls-certificate-unknown).

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

The project has `SIGNALS_MTLS_ENABLED` on, and the client certificate this call presented is not one of the project's registered certificates, or it has expired. Nothing was sent to Signals.

## Troubleshooting [#troubleshooting]

1. List the project's certificates with `GET /v1/signals/certs` and compare their `sha256` fingerprints with your client's certificate (`openssl x509 -in client.crt -noout -fingerprint -sha256`).
2. Check `notAfter`. An expired certificate is refused even while it is still registered.
3. Ask a project admin to register the certificate you use, or point your client at the registered one.

## Retry safely [#retry-safely]

Retry with a registered, unexpired certificate. The refused call changed nothing.

## 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.
