From 61682c01737c87ca28491c5b2684b65741a27cf0 Mon Sep 17 00:00:00 2001
From: Antonius Moritz <5209092+tarantila@users.noreply.github.com>
Date: Sun, 7 Jun 2026 16:13:40 +0200
Subject: [PATCH] fix(docs): remove redundant Nginx Proxy Manager directives

With Websockets Support enabled, NPM already injects the upgrade directives via its conditional connection-upgrade map and sets the standard forwarded headers by default. Re-declaring them in the Advanced block is redundant and the hardcoded Connection "upgrade" can break the proxy host. Keep only the HealthLog-specific 300s read timeout.
---
 docs/self-hosting/reverse-proxy.md | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/docs/self-hosting/reverse-proxy.md b/docs/self-hosting/reverse-proxy.md
index 6426d842c..471e630ed 100644
--- a/docs/self-hosting/reverse-proxy.md
+++ b/docs/self-hosting/reverse-proxy.md
@@ -97,16 +97,13 @@ In the NPM UI:
 6. **Advanced tab — Custom Nginx Configuration:**
 
    ```nginx
-   proxy_set_header X-Real-IP $remote_addr;
-   proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-   proxy_set_header X-Forwarded-Proto $scheme;
-   proxy_set_header Host $host;
-   proxy_http_version 1.1;
-   proxy_set_header Upgrade $http_upgrade;
-   proxy_set_header Connection "upgrade";
    proxy_read_timeout 300s;
    ```
 
+   Nginx Proxy Manager configures the standard forwarded headers
+   automatically and adds the WebSocket upgrade directives when
+   Websockets Support is enabled.
+
    The 300-second read timeout matters for long-running insight
    generations — anything shorter will cut streamed responses mid-flight.