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

docs: point to the NATS TLS example and carry its CA through Steps 4 and 6

Browse Source
This commit is contained in:
Jack Carter
2026-09-24 15:53:00 +02:00
parent df7724b962
commit 3a44d3c3ca
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/selfhosted/maintenance/scaling/high-availability-from-installer.mdx
+4 -2
View File
@@ -167,6 +167,8 @@ server:
redisAddr: "redis://redis.example.com:6379" redisAddr: "redis://redis.example.com:6379"
``` ```
If your NATS cluster uses TLS, as in the High Availability guide's [NATS example](/selfhosted/maintenance/scaling/high-availability#example-a-self-hosted-cluster-with-docker-compose), write each URL with `tls://` and the client password. If its certificates come from your own CA, also add the CA to the `netbird-server` volumes in `docker-compose.yml` as that example shows, and run `docker compose up -d netbird-server` instead of the restart below.
Restart the server: Restart the server:
```bash ```bash
@@ -296,7 +298,7 @@ From here on, TLS and routing move from the installer's Traefik to your load bal
netbird_data: netbird_data:
``` ```
Keep the installer's `.env` beside it: it supplies the domain, image tags and license key. Keep the installer's `.env` beside it: it supplies the domain, image tags and license key. If you added a NATS CA to the volumes in Step 2, add the same line here.
Before you start the node, change its rules at a network firewall or cloud security group: Before you start the node, change its rules at a network firewall or cloud security group:
@@ -359,7 +361,7 @@ Node 2 runs the same three files as node 1, with no installer and no database of
Node 1 keeps running: these tags name the images it already runs. It switches to them in item 4. Node 1 keeps running: these tags name the images it already runs. It switches to them in item 4.
2. On node 2, create the same directory and copy three files into it from node 1: `config.yaml`, `.env` and `docker-compose.yml`. Two of them hold secrets, so copy them over an encrypted channel, such as `scp` or your configuration management tool's secret store, and keep them readable by root only: 2. On node 2, create the same directory and copy three files into it from node 1: `config.yaml`, `.env` and `docker-compose.yml`, plus `nats-ca.pem` if you added a NATS CA in Step 2. Two of them hold secrets, so copy them over an encrypted channel, such as `scp` or your configuration management tool's secret store, and keep them readable by root only:
```bash ```bash
chmod 600 config.yaml .env chmod 600 config.yaml .env