From 304ed449660ccd9c26d626f9e6fa896f3935362c Mon Sep 17 00:00:00 2001 From: Blake Blackshear Date: Sun, 23 Apr 2023 07:27:19 -0500 Subject: [PATCH] cleanup --- docs/docs/guides/reverse_proxy.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/docs/docs/guides/reverse_proxy.md b/docs/docs/guides/reverse_proxy.md index 60888ec29..165b4d517 100644 --- a/docs/docs/guides/reverse_proxy.md +++ b/docs/docs/guides/reverse_proxy.md @@ -85,7 +85,7 @@ There are many ways to authenticate a website but a straightforward approach is ``` -## Nginix Reverse Proxy +## Nginx Reverse Proxy This method shows a working example for subdomain type reverse proxy with SSL enabled. @@ -94,27 +94,20 @@ This method shows a working example for subdomain type reverse proxy with SSL en This is set in `$server` and `$port` this should match your ports you have exposed to your docker container. Optionally you listen on port `443` and enable `SSL` ``` - # ------------------------------------------------------------ # frigate.domain.com # ------------------------------------------------------------ - server { set $forward_scheme http; set $server "192.168.100.2"; # FRIGATE SERVER LOCATION set $port 5000; listen 80; - listen 443 ssl http2; - server_name frigate.domain.com; - } - - - +} ``` ### Setup SSL (optional)