From 9f88384f12aaec6ad8bedfcd8af7c5680bc45fcc Mon Sep 17 00:00:00 2001
From: szaimen <szaimen@e.mail.de>
Date: Fri, 6 May 2022 01:01:17 +0200
Subject: [PATCH] document that nginx-proxy is not supported

Signed-off-by: szaimen <szaimen@e.mail.de>
---
 reverse-proxy.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/reverse-proxy.md b/reverse-proxy.md
index e81c7b16..f594dfc7 100644
--- a/reverse-proxy.md
+++ b/reverse-proxy.md
@@ -12,7 +12,7 @@ In order to run Nextcloud behind a reverse proxy, you need to specify the port t
 
 ### 1. Add this to your reverse proxy config
 
-⚠ **Please note:** Since the Apache container gets spawned by the mastercontainer, there is **NO** way to provide custom docker labels for the Apache container. So please do not attempt to do this because you will fail!
+⚠ **Please note:** Since the Apache container gets spawned by the mastercontainer, there is **NO** way to provide custom docker labels or custom environmental variables for the Apache container. So please do not attempt to do this because you will fail!
 
 #### Caddy
 
@@ -61,6 +61,16 @@ Of course SSL needs to be set up as well e.g. by using certbot and your domain m
 
 </details>
 
+#### Nginx-Proxy
+
+<details>
+
+<summary>click here to expand</summary>
+
+Unfortunately it is not possible to configure nginx-proxy in a way that works because it completely relies on environmental variables of the docker containers itself. Providing these does not work as stated above.
+
+</details>
+
 #### Traefik 2
 
 <details>