From 2eb7433b14a18c32479455abdde3bee537a7c881 Mon Sep 17 00:00:00 2001
From: vajonam <152501+vajonam@users.noreply.github.com>
Date: Wed, 19 Apr 2023 11:04:01 -0400
Subject: [PATCH] adding instructions for Nginix reverse proxy

adding an example of subdomain reverse proxy for nginx
---
 docs/docs/guides/reverse_proxy.md | 46 +++++++++++++++++++++++++++++++
 1 file changed, 46 insertions(+)

diff --git a/docs/docs/guides/reverse_proxy.md b/docs/docs/guides/reverse_proxy.md
index 2e284eede..39973edaf 100644
--- a/docs/docs/guides/reverse_proxy.md
+++ b/docs/docs/guides/reverse_proxy.md
@@ -84,3 +84,49 @@ There are many ways to authenticate a website but a straightforward approach is
     </Location>
 </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;
+  }
+
+}
+```