From 95e169adfdf10cb04693f0d38db66cfa6749e68c Mon Sep 17 00:00:00 2001
From: Lucie Zhao <lzhao@gitlab.com>
Date: Thu, 24 Oct 2024 15:54:12 +0000
Subject: [PATCH] Add guidance on allowed Geo IPs for 401 troubleshooting

---
 .../geo/replication/troubleshooting/client_http.md              | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/administration/geo/replication/troubleshooting/client_http.md b/doc/administration/geo/replication/troubleshooting/client_http.md
index 3a9c85f6a7489..a61f4e8db6865 100644
--- a/doc/administration/geo/replication/troubleshooting/client_http.md
+++ b/doc/administration/geo/replication/troubleshooting/client_http.md
@@ -79,6 +79,8 @@ and changing the `8k` size, for example by doubling it to `16k`.
 If using a load balancer, ensure that the load balancer's URL is set as the `external_url` in the
 `/etc/gitlab/gitlab.rb` of the nodes behind the load balancer.
 
+On the primary site, go to **Admin > Geo > Settings** and find the **Allowed Geo IP** field. Ensure the IP address of the secondary site is listed.
+
 ### Primary site returns 500 error when accessing `/admin/geo/replication/projects`
 
 Navigating to **Admin > Geo > Replication** (or `/admin/geo/replication/projects`) on a primary Geo site, shows a 500 error, while that same link on the secondary works fine. The primary's `production.log` has a similar entry to the following:
-- 
GitLab