docs: do not promise NATS TLS instructions the HA guide does not have

This commit is contained in:
Jack Carter
2026-09-24 15:59:15 +02:00
parent e4209eafd6
commit ca2c415bcc
@@ -176,7 +176,7 @@ docker compose logs --since 2m netbird-server | grep -E 'redis cache|Connected t
You should see `using redis cache at redis://redis.example.com:6379`, `Connected to NATS cluster` and `license validated`. You should see `using redis cache at redis://redis.example.com:6379`, `Connected to NATS cluster` and `license validated`.
Protect Redis and NATS with TLS and authentication, as the High Availability guide describes. Their credentials go in these two URLs, and the server writes both URLs to its log at startup, credentials included; the command above prints them. Keep the server's logs as private as `config.yaml`. Protect Redis and NATS with authentication, and with TLS if their traffic crosses a network you do not trust. Their credentials go in these two URLs, and the server writes both URLs to its log at startup, credentials included; the command above prints them. Keep the server's logs as private as `config.yaml`.
## Step 3: Move Relay to separate instances ## Step 3: Move Relay to separate instances