From 821c07c5a0d30a8f5096f950d08a049123caeb6d Mon Sep 17 00:00:00 2001 From: Emil Sandnabba Date: Wed, 14 Aug 2024 23:38:58 +0200 Subject: [PATCH] Update docs/docs/guides/reverse_proxy.md Co-authored-by: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com> --- 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 c7bef6bf9..d408a1444 100644 --- a/docs/docs/guides/reverse_proxy.md +++ b/docs/docs/guides/reverse_proxy.md @@ -173,7 +173,7 @@ services: - "traefik.http.routers.frigate.rule=Host(`traefik.example.com`)" ``` -The above configuration will create a "service" in Traefik, automatically adding your container's IP on port 8791 as a backend. +The above configuration will create a "service" in Traefik, automatically adding your container's IP on port 8971 as a backend. It will also add a router, routing requests to "traefik.example.com" to your local container. 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.