From d79bafc5b7990529b5753024079fbe2320f0a2f5 Mon Sep 17 00:00:00 2001 From: Emil Sandnabba Date: Wed, 14 Aug 2024 23:18:52 +0200 Subject: [PATCH] Update docs/docs/guides/reverse_proxy.md Co-authored-by: Nicolas Mowen --- docs/docs/guides/reverse_proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/guides/reverse_proxy.md b/docs/docs/guides/reverse_proxy.md index 148dd49db..001ca4609 100644 --- a/docs/docs/guides/reverse_proxy.md +++ b/docs/docs/guides/reverse_proxy.md @@ -12,7 +12,7 @@ Before setting up a reverse proxy, check if any of the built-in functionality in |-|-| |TLS|Please see the `tls` [configuration option](../configuration/tls.md)| |Authentication|Please see the [authentication](../configuration/authentication.md) documentation| -|IPv6|[Advanced configuration #enabling-ipv6](../configuration/advanced.md#enabling-ipv6) +|IPv6|[Enabling IPv6](../configuration/advanced.md#enabling-ipv6) **Note about TLS** When using a reverse proxy, the TLS session is usually terminated at the proxy, sending the internal request over plain HTTP. If this is the desired behavior, TLS must first be disabled in Frigate, or you will encounter an HTTP 400 error: "The plain HTTP request was sent to HTTPS port."