Documentation

influx config

The influx config command displays the active InfluxDB connection configuration and manages multiple connection configurations stored, by default, in ~/.influxdbv2/configs. Each connection includes a URL, token, associated organization, and active setting. InfluxDB reads the token from the active connection configuration, so you don’t have to manually enter a token to log into InfluxDB.

Usage

influx config [flags]
influx config [command]
influx config <config-name>
Quickly switch between configurations
# Syntax
influx config <config-name>

# Example
influx config local-config

To quickly switch back to the previous configuration, use the following command:

influx config -

Examples

# Show the active connection configuration
influx config

# Set a connection configuration as active
influx config local-config

Subcommands

SubcommandDescription
createCreate a connection configuration
listList connection configurations
deleteDelete a connection configuration
setSet or update a connection configuration

Flags

FlagDescription
-h--helpHelp for the config command

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2

InfluxDB Cloud Serverless