From a758c77a494f26b06e36f29a60751e8dad7914d6 Mon Sep 17 00:00:00 2001 From: Geoffrey Wossum Date: Wed, 5 Nov 2025 11:50:44 -0600 Subject: [PATCH] chore: improve `hostname` documentation for HTTPS usage Clarified hostname requirements for HTTPS in meta node configuration. --- .../v1/administration/configure/config-meta-nodes.md | 4 ++++ 1 file changed, 4 insertions(+) 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 372f999a0..c56bb1b23 100644 --- a/content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md +++ b/content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md @@ -51,6 +51,8 @@ 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. + Environment variable: `INFLUXDB_HOSTNAME` ----- @@ -152,6 +154,8 @@ Use either: * PEM-encoded bundle with both the certificate and key (`[bundled-crt-and-key].pem`) * Certificate only (`[certificate].crt`) +When HTTPS is enabled, [`hostname`](#hostname) must match a hostname or wildcard in the certificate. + Environment variable: `INFLUXDB_META_HTTPS_CERTIFICATE` #### https-private-key