Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

chore: improve `hostname` documentation for HTTPS usage 

Clarified hostname requirements for HTTPS in meta node configuration.
pull/6514/head
Geoffrey Wossum 2025-11-05 11:50:44 -06:00 committed by GitHub
parent 7f2178afa5
commit a758c77a49
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/enterprise_influxdb/v1/administration/configure/config-meta-nodes.md
View File

@ -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