administrator/frigate
1
0
Fork 0
mirror of https://github.com/blakeblackshear/frigate.git synced 2026-02-03 09:45:22 +03:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Update docs/docs/guides/reverse_proxy.md

Browse Source 
Co-authored-by: Nicolas Mowen <nickmowen213@gmail.com>
This commit is contained in:
Paul Blacknell 2022-12-15 22:59:03 +00:00 committed by GitHub
parent 5f424b1047
commit 2241f0e8d5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/docs/guides/reverse_proxy.md
View File

@ -51,9 +51,6 @@ Here we access Frigate via https://cctv.mydomain.co.uk
RewriteCond %{HTTP:Upgrade} !=websocket [NC] RewriteCond %{HTTP:Upgrade} !=websocket [NC]
RewriteRule /(.*) http://frigatepi.local:5000/$1 [P,L] RewriteRule /(.*) http://frigatepi.local:5000/$1 [P,L]
</VirtualHost> </VirtualHost>
```
### 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. 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 This Apache2 configuration snippet then results in unencrypted requests being redirected to webserver SSL port