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

adding instructions for Nginix reverse proxy

Browse Source 
adding an example of subdomain reverse proxy for nginx
This commit is contained in:
vajonam 2023-04-19 11:04:01 -04:00 committed by GitHub
parent 433bf690e3
commit 2eb7433b14
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 46 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -84,3 +84,49 @@ There are many ways to authenticate a website but a straightforward approach is
</Location> </Location>
</VirtualHost> </VirtualHost>
``` ```
## Nginix Reverse Proxy
Setting up a reverse proxy for Nginix is also possible. This method shows a working example for subdomain type reverse proxy. This example also shows SSL enabled.
```
# ------------------------------------------------------------
# frigate.domain.com
# ------------------------------------------------------------
server {
set $forward_scheme http;
set $server "192.168.100.2"; # FRIGATE SERVER NAME
set $port 5000;
listen 80;
listen 443 ssl http2;
server_name frigate.domain.com;
# Let's Encrypt SSL
include conf.d/include/letsencrypt-acme-challenge.conf;
include conf.d/include/ssl-ciphers.conf;
ssl_certificate /etc/letsencrypt/live/npm-1/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/npm-1/privkey.pem;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;
access_log /data/logs/proxy-host-40_access.log proxy;
error_log /data/logs/proxy-host-40_error.log warn;
location / {
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_http_version 1.1;
}
}
```