Documentation

Renew or update a license key or file

Use this procedure to renew or update an existing license key or file, switch from a license key to a license file, or switch from a license file to a license key.

Note: To request a new license to renew or expand your InfluxDB Enterprise cluster, contact sales@influxdb.com.

To update a license key or file, do the following:

  1. If you are switching from a license key to a license file (or vice versa), delete your existing license key or file.
  2. Add the license key or file to your meta nodes and data nodes configuration settings. For more information, see how to configure InfluxDB Enterprise clusters.
  3. On each meta node, run service influxdb-meta restart, and wait for the meta node service to come back up successfully before restarting the next meta node. The cluster should remain unaffected as long as only one node is restarting at a time.
  4. On each data node, run killall -s HUP influxd to signal the influxd process to reload its configuration file.

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