From 3d173346449e99b10b47a6fcaf25490ebf90ee15 Mon Sep 17 00:00:00 2001
From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com>
Date: Wed, 23 Sep 2026 18:28:15 +0200
Subject: [PATCH] docs: attribute the built-in STUN shutdown to relays, and say
 why stuns is required

---
 .../maintenance/scaling/high-availability-from-installer.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx b/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
index 6c2090cb..ff4f9bd8 100644
--- a/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
+++ b/src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
@@ -174,7 +174,7 @@ server:
     credentialsTTL: "24h"
 ```
 
-Restart the server with `docker compose restart netbird-server`. Setting `relays` turns off the built-in relay, and setting `stuns` turns off the built-in STUN server.
+Restart the server with `docker compose restart netbird-server`. Setting `relays` turns off the built-in relay and its STUN server. That is why `stuns` is required: without it, the server still tells peers to use STUN at `app.example.com:3478`, where nothing answers.
 
 ## Step 4: Put the load balancer in front of node 1