sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-10-17 19:19:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: explain why the old Signal route is removed after the switch

Browse Source
This commit is contained in:
Jack Carter
2026-09-24 10:59:59 +02:00
parent 23cb41b586
commit 85931bedf9
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
+1 -1
View File
@@ -329,7 +329,7 @@ Plan this step for a maintenance window. Peers learn the Signal URL when they lo
Setting `signalUri` turns off the server's built-in Signal.
2. Restart the server: `docker compose restart netbird-server`.
3. On every device that was connected during the change, run `netbird down` and then `netbird up`. Include devices that are always on, such as routing peers, exit nodes and servers. Each one connects to `signal.example.com` straight away. Check with `netbird status`, which shows `Signal: Connected to https://signal.example.com:443`.
4. Remove the `/signalexchange.SignalExchange/*` route from the `app.example.com` load balancer. Nothing serves it any more.
4. Remove the `/signalexchange.SignalExchange/*` route from the `app.example.com` load balancer. It carried Signal only until this step.
## Step 6: Add node 2