From 8615bb92581c92068866df8e2c2aa2e5c43a239f Mon Sep 17 00:00:00 2001 From: "genevera (she/her)" Date: Sun, 27 Apr 2025 16:20:16 -0400 Subject: [PATCH] Update docs/docs/guides/reverse_proxy.md Co-authored-by: Nicolas Mowen --- docs/docs/guides/reverse_proxy.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/docs/guides/reverse_proxy.md b/docs/docs/guides/reverse_proxy.md index d1cb2b4fe2..889a08b6b2 100644 --- a/docs/docs/guides/reverse_proxy.md +++ b/docs/docs/guides/reverse_proxy.md @@ -181,6 +181,7 @@ It will also add a router, routing requests to "traefik.example.com" to your loc Note that with this approach, you don't need to expose any ports for the Frigate instance since all traffic will be routed over the internal Docker network. ## Caddy Reverse Proxy + This example shows a working example of frigate running under a subdomain with logging and a tls cert (in this case a wildcard domain cert obtained independently of caddy) handled via imports ```caddy