From cd231e996b0d513d64ad782bfd8285ed65df57fc Mon Sep 17 00:00:00 2001 From: "GL.iNet-Yongping.Xie" Date: Wed, 24 Dec 2025 19:12:07 -0800 Subject: [PATCH] fix: clarify reverse proxy mode configuration Add brief comments explaining the reverse proxy mode switch. Signed-off-by: GL.iNet-Yongping.Xie --- docker-compose/.env.example | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docker-compose/.env.example b/docker-compose/.env.example index 273693f..cf7af2b 100755 --- a/docker-compose/.env.example +++ b/docker-compose/.env.example @@ -4,6 +4,22 @@ COTURN_IMAGE=coturn/coturn:edge-alpine # Enable reverse proxy mode (e.g. Nginx in front of GLKVM Cloud). # When enabled, TLS is handled by the proxy and GLKVM Cloud runs in plain HTTP. +# +# Note: +# In reverse-proxy mode, remote device access depends on the correct forwarded headers +# from the front-end proxy. If these headers are missing or incorrect, GLKVM Cloud may +# generate redirect URLs with the internal port (e.g. :10443). +# +# Please make sure your Nginx config includes: +# proxy_set_header Host $host; +# proxy_set_header X-Forwarded-Host $host; +# proxy_set_header X-Forwarded-Proto $scheme; +# proxy_set_header X-Forwarded-Port $server_port; +# proxy_set_header X-Real-IP $remote_addr; +# proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; +# +# Reference (verified working example): +# https://github.com/gl-inet/glkvm-cloud/blob/main/docker-compose/nginx-reverse-proxy-example.conf REVERSE_PROXY_ENABLED=false # GLKVM access IP seen by devices/users.