From 3cad6a397c4108da2ad65030c5a46cf391c2d956 Mon Sep 17 00:00:00 2001 From: Paul Blacknell Date: Sun, 27 Nov 2022 16:16:17 +0000 Subject: [PATCH] Update reverse_proxy.md --- 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 0492dcf76..946ef9933 100644 --- a/docs/docs/guides/reverse_proxy.md +++ b/docs/docs/guides/reverse_proxy.md @@ -8,7 +8,7 @@ A reverse proxy accepts HTTP requests the public internet and redirects them tra The suggested steps are: - **Configure** a 'proxy' HTTP webserver (such as [Apache2](https://httpd.apache.org/docs/current/)) and only expose ports 80/443 from this webserver to the internet -- **Encrypt** the proxy webserver by installing SSL (such as with [Let's Encrypt](https://letsencrypt.org/)). Note that SSL is then not required on your Frigate webserver as the proxy encrypts all requests for you +- **Encrypt** content from the proxy webserver by installing SSL (such as with [Let's Encrypt](https://letsencrypt.org/)). Note that SSL is then not required on your Frigate webserver as the proxy encrypts all requests for you - **Restrict** access to your Frigate instance at the proxy using, for example, password authentication :::caution