From f784f81be3dffd01c15aeefee8bd69a7ce8b4449 Mon Sep 17 00:00:00 2001 From: Jason Stirnaman Date: Wed, 5 Nov 2025 11:58:57 -0600 Subject: [PATCH] Update content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md --- .../v1/administration/configure/config-meta-nodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md b/content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md index c56bb1b23..a08c07def 100644 --- a/content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md +++ b/content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md @@ -51,7 +51,7 @@ Default is `""`. The hostname of the [meta node](/enterprise_influxdb/v1/concepts/glossary/#meta-node). This must be resolvable and reachable by all other members of the cluster. -If HTTPS is enabled with [`https-enabled`](#https-enabled), `hostname` must match a hostname or wildcard in the TLS certificate specified by [`https-certificate`](#https-certificate). If `hostname` does not match, then `http: TLS handshake error from 127.0.0.1` errors will occur in the meta node logs and the cluster will not function properly. +If HTTPS is enabled with [`https-enabled`](#https-enabled), `hostname` must match a hostname or wildcard in the TLS certificate specified by [`https-certificate`](#https-certificate). If `hostname` does not match, then `http: TLS handshake error from 127.0.0.1` errors are output in the meta node logs and the cluster will not function properly. Environment variable: `INFLUXDB_HOSTNAME`