mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-09 21:10:59 +00:00
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.
This commit is contained in:
1 parent
13f6252298
commit
61682c0173
1 file changed
+4
-7
@@ -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.
|
||||
|
||||
|
||||
Reference in new issue
Block a user