influxdata/influxdb3-ui repository overview

⁠What is InfluxDB 3 Explorer?

InfluxDB 3 Explorer is a standalone web application designed for visualizing, querying, and managing your data stored in InfluxDB 3. Explorer provides an intuitive interface for interacting with your time series data.

⁠How to use this image

⁠Requirements

To use InfluxDB 3 Explorer, you need a compatible InfluxDB 3 instance, such as InfluxDB 3 Core or InfluxDB 3 Enterprise. See the official InfluxDB Docker image⁠.

⁠Pull the image

docker pull influxdata/influxdb3-ui:1.10.0

⁠Start InfluxDB 3 Explorer

Run InfluxDB 3 Explorer using Docker CLI.

⁠Query mode (default)

To start Explorer in query mode, which lets people query and visualize data but not manage the database:

docker run --detach \
  --name influxdb3-explorer \
  --publish 8080:8080 \
  influxdata/influxdb3-ui:1.10.0

Query mode hides the admin pages and refuses the requests behind them: creating or deleting databases and tables, writing and importing data, managing tokens, triggers, plugins and caches, and changing AI settings.

What Explorer can read is still decided by the token of the connection. Anyone who can reach Explorer uses that token to run queries, so give a query-mode Explorer a token that can only read the databases it should show — not an admin token. A read-only token for Explorer needs, besides db:<database>:read, permission to answer /ping and /health:

influxdb3 create token \
  --permission "db:my_database:read" \
  --permission "system:ping,health:read" \
  --name explorer-read-only

⁠Admin mode

To start Explorer in admin mode with full functionality:

docker run --detach \
  --name influxdb3-explorer \
  --publish 8080:8080 \
  influxdata/influxdb3-ui:1.10.0 \
  --mode=admin

This command:

• Maps container port 8080 to host port 8080 (web UI)
• Runs the container in admin mode

If --mode is not set, the container defaults to query mode.

Access the Explorer UI at http://localhost:8080 in your browser.

⁠Persistent data storage

To preserve Explorer application data across container restarts, mount a local directory:

IMPORTANT: The container runs as non-root user influxui (uid 1500). The mounted directory must be owned by this user.

mkdir -p ./db
sudo chown -R 1500:1500 ./db
chmod 700 ./db

docker run --detach \
  --name influxdb3-explorer \
  --publish 8080:8080 \
  --volume $(pwd)/db:/db:rw \
  influxdata/influxdb3-ui:1.10.0 \
  --mode=admin

Troubleshooting: If you see SQLITE_CANTOPEN errors, fix the directory ownership:

sudo chown -R 1500:1500 ./db
docker restart influxdb3-explorer

⁠Pre-configure InfluxDB connections

To pre-configure InfluxDB connection settings, create a config.json file and mount it:

mkdir -p ./config ./db
sudo chown -R 1500:1500 ./db
chmod 755 ./config
chmod 700 ./db

# Create config file
cat > ./config/config.json << 'EOF'
{
  "DEFAULT_INFLUX_SERVER": "http://host.docker.internal:8181",
  "DEFAULT_INFLUX_DATABASE": "my_database",
  "DEFAULT_API_TOKEN": "your-admin-token",
  "DEFAULT_SERVER_NAME": "my_server"
}
EOF

docker run --detach \
  --name influxdb3-explorer \
  --publish 8080:8080 \
  --volume $(pwd)/config:/app-root/config:ro \
  --volume $(pwd)/db:/db:rw \
  influxdata/influxdb3-ui:1.10.0 \
  --mode=admin

⁠Enable HTTPS

To enable TLS/SSL, mount valid certificate and key files into the container:

Place your TLS/SSL certificate files in your local ./ssl directory: Required files:

Certificate: cert.pem or server.crt Private key: key.pem or server.key

# Create directories
mkdir -p ./ssl ./db
sudo chown -R 1500:1500 ./db
chmod 755 ./ssl

# Place your cert.pem and key.pem files in ./ssl directory

docker run --detach \
  --name influxdb3-explorer \
  --publish 8080:8080 \
  --publish 8443:8443 \
  --volume $(pwd)/ssl:/etc/nginx/ssl:ro \
  --volume $(pwd)/db:/db:rw \
  --env SSL_CERT_PATH=/etc/nginx/ssl/cert.pem \
  --env SSL_KEY_PATH=/etc/nginx/ssl/key.pem \
  influxdata/influxdb3-ui:1.10.0 \
  --mode=admin

Access the UI via HTTPS at https://localhost:8443

The nginx web server automatically uses certificate files when they are present in the mounted path.

⁠Custom SSL certificate paths

You can use custom locations for certificate and key files:

mkdir -p ./ssl ./db
sudo chown -R 1500:1500 ./db
chmod 755 ./ssl

docker run --detach \
  --name influxdb3-explorer \
  --publish 8080:8080 \
  --publish 8443:8443 \
  --volume $(pwd)/ssl:/custom/ssl:ro \
  --volume $(pwd)/db:/db:rw \
  --env SSL_CERT_PATH=/custom/ssl/server.crt \
  --env SSL_KEY_PATH=/custom/ssl/server.key \
  influxdata/influxdb3-ui:1.10.0 \
  --mode=admin

⁠Environment variables

The following environment variables can be used to configure the container:

• DATABASE_URL - Path to SQLite database inside container (default: /db/sqlite.db)
• SESSION_SECRET_KEY - Secret key for session management (recommended for production)
• SSL_CERT_PATH - Path to SSL certificate file (default: /etc/nginx/ssl/cert.pem)
• SSL_KEY_PATH - Path to SSL private key file (default: /etc/nginx/ssl/key.pem)
• PLUGIN_REGISTRY_ALLOWED_HOSTS - Comma-separated hosts plugin registries can be added from (default in this image: github.com). To use your own registry, pass every allowed host with -e, for example -e PLUGIN_REGISTRY_ALLOWED_HOSTS=github.com,registry.example.com; the image sets this variable, so a value in config.json does not override it. * allows any host except loopback, private and link-local addresses
• OPENAI_BASE_URL, ANTHROPIC_BASE_URL, GEMINI_BASE_URL - Base URL of the AI provider's API, for an OpenAI-compatible endpoint, a proxy or a local model (default: the provider's public API). Include the API version: OPENAI_BASE_URL and ANTHROPIC_BASE_URL end in /v1, for example http://host.docker.internal:11434/v1, and GEMINI_BASE_URL ends in /v1beta. An empty value counts as unset; a value that is not an http or https URL makes AI requests fail

Important for production: Always set SESSION_SECRET_KEY in production. When you restart the container, InfluxDB 3 Explorer generates a new key if not explicitly set.

For more information about available options and environment variables, see the InfluxDB 3 Explorer documentation⁠