From d9c620212754d79e21db776fb3df0375225d7097 Mon Sep 17 00:00:00 2001 From: Paul Blacknell Date: Fri, 16 Dec 2022 12:13:43 +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 0a06e4047..22884a4d8 100644 --- a/docs/docs/guides/reverse_proxy.md +++ b/docs/docs/guides/reverse_proxy.md @@ -55,7 +55,7 @@ Here we access Frigate via https://cctv.mydomain.co.uk ### Step 2: Use SSL to encrypt access to your Frigate instance -Whilst this won't, on its own, stop access to your Frigate webserver it will encrypt all content (such as login credentials). +Whilst this won't, on its own, prevent access to your Frigate webserver it will encrypt all content (such as login credentials). Installing SSL is beyond the scope of this document but [Let's Encrypt](https://letsencrypt.org/) is a widely used approach. This Apache2 configuration snippet then results in unencrypted requests being redirected to the webserver SSL port