From 2241f0e8d5b1aa0516ca970f543034bb044cc98a Mon Sep 17 00:00:00 2001 From: Paul Blacknell Date: Thu, 15 Dec 2022 22:59:03 +0000 Subject: [PATCH] Update docs/docs/guides/reverse_proxy.md Co-authored-by: Nicolas Mowen --- docs/docs/guides/reverse_proxy.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/docs/guides/reverse_proxy.md b/docs/docs/guides/reverse_proxy.md index 06fbeafaf..811c4e375 100644 --- a/docs/docs/guides/reverse_proxy.md +++ b/docs/docs/guides/reverse_proxy.md @@ -51,9 +51,6 @@ Here we access Frigate via https://cctv.mydomain.co.uk RewriteCond %{HTTP:Upgrade} !=websocket [NC] RewriteRule /(.*) http://frigatepi.local:5000/$1 [P,L] -``` -### 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). 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 webserver SSL port