From cead741c1646f0bd53746164df6b84ae1c83bd77 Mon Sep 17 00:00:00 2001
From: tobi <tobi.smethurst@protonmail.com>
Date: Mon, 11 Aug 2025 16:23:55 +0200
Subject: [docs] Revamp trusted proxies warning a bit (#4365)

Closes https://codeberg.org/superseriousbusiness/gotosocial/issues/4352 by mentioning required headers in reverse proxy.

Reviewed-on: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4365
Co-authored-by: tobi <tobi.smethurst@protonmail.com>
Co-committed-by: tobi <tobi.smethurst@protonmail.com>
---
 web/template/page_header.tmpl | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

(limited to 'web')

diff --git a/web/template/page_header.tmpl b/web/template/page_header.tmpl
index ba9cf6e72..f8b01fd02 100644
--- a/web/template/page_header.tmpl
+++ b/web/template/page_header.tmpl
@@ -21,14 +21,17 @@
 {{- .with }}
 <div class="trusted-proxies-rec">
     <p>
-        <strong>Warning!</strong> It looks like <code>trusted-proxies</code> is not set correctly in this instance's configuration.
+        <strong>Warning!</strong> It looks like either <code>trusted-proxies</code> is not set correctly in this instance's configuration,
+        or the upstream reverse proxy is not passing an appropriate <code>X-Forwarded-For</code> or <code>X-Real-IP</code> header.
+    </p>
+    <p>
         This may cause rate-limiting issues and, by extension, federation issues.
     </p>
     <p>
-        If you are the instance admin, you should fix this by adding <code>{{- .trustedProxiesRec -}}</code> to your <code>trusted-proxies</code>.
+        If you are the instance admin, you may be able to fix this by adding <code>{{- .trustedProxiesRec -}}</code> to your <code>trusted-proxies</code>.
     </p>
     <p>
-        For more information, see
+        For more information and other possible fixes for this issue, see
         <a
             href="https://docs.gotosocial.org/en/latest/configuration/trusted_proxies/"
             rel="nofollow noreferrer noopener"
-- 
cgit v1.3