# WEBHOOKS_NOT_HTTPS

Canonical page: https://docs.ovok.com/errors/webhooks-not-https

**HTTP 409.** Problem type: [`https://docs.ovok.com/errors/webhooks-not-https`](https://docs.ovok.com/errors/webhooks-not-https).

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

You tried to switch `SIGNALS_MTLS_ENABLED` on while some of the project's Signals webhook subscribers still send to an http URL. With mutual TLS on, Signals presents its client certificate over https only, so it would drop every event for those subscribers for good. Nothing was changed. The answer's `subscribers` lists each one by `id` and `name`.

## Troubleshooting [#troubleshooting]

1. Find the subscribers the answer names, in the Console under Signals › Webhooks or with `GET /v1/signals/api/user?role=subscriber`.
2. Move each one to an https URL (`POST /v1/signals/api/user/{userId}` with a new `webhookUrl`), or delete the ones you no longer need.
3. Make sure each receiver accepts Signals' client certificate, signed by the CA under Signals › Settings.
4. Switch `SIGNALS_MTLS_ENABLED` on again.

## Retry safely [#retry-safely]

Retry the switch-on once every subscriber the answer named is on https or deleted. An unchanged request returns the same error, and the setting stays off.

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