influx server-config
API token hashing is enabled by default in InfluxDB OSS 2.9.0
Stronger token security: tokens are stored as hashes on disk, so a copy of the database file doesn’t expose usable tokens. Existing tokens are hashed on first startup and the original strings can’t be recovered afterward — capture any plaintext tokens you still need before you upgrade.
For more information, see Token hashing.
The influx server-config command displays the InfluxDB runtime server configuration.
To display the server configuration, you must use an operator token.
Usage
influx server-config [flags]
influx server-config [command]Examples
# Show the server configuration.
influx server-config
# Show the server configuration as YAML.
influx server-config --yamlFlags
| Flag | Description | |
|---|---|---|
-c | --active-config | CLI configuration to use for command |
--configs-path | Path to influx CLI configurations (default ~/.influxdbv2/configs) | |
-h | --help | Help for the list command |
--hide-headers | Hide table headers (default false) | |
--host | HTTP address of InfluxDB (default http://localhost:8086) | |
--http-debug | Inspect communication with InfluxDB servers | |
-i | --id | Organization ID |
--json | Output data as JSON (default false) | |
-n | --name | Organization name |
--skip-verify | Skip TLS certificate verification | |
-t | --token | API token |
--toml | Output configuration as TOML instead of JSON | |
--yaml | Output configuration as YAML instead of JSON |
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB OSS v2 and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.