---
title: Troubleshoot Telegraf Controller installation
description: Resolve common installation and startup issues with Telegraf Controller.
url: https://docs.influxdata.com/telegraf/controller/install/troubleshoot/
estimated_tokens: 2574
product: Telegraf
version: v1
---

# Troubleshoot Telegraf Controller installation

#### Telegraf Controller is in Public Beta

Telegraf Controller is in public beta and will be part of the future Telegraf Enterprise offering. While in beta, Telegraf Controller is **not meant for production use**. The Telegraf Controller documentation is a work in progress, and we are actively working to improve it. If you have any questions or suggestions, please [submit an issue](https://github.com/influxdata/docs-v2/issues/new?labels=Telegraf%20Controller). We welcome any and all contributions.

Beta expectations

-   **No configuration or agent limits**  
    While in beta, Telegraf Controller doesn't place any limits on the number of configurations you can store or the number of Telegraf agents you can track. However, upon being generally available, the free distribution of Telegraf Controller will have limits introduced, with the option to increase limits through a Telegraf Enterprise license.
-   **Potential breaking changes**  
    While in beta, we will do our best to no longer make breaking changes to Telegraf Controller, however, they may be necessary. The majority of changes we make will be additive and non-breaking, and include any necessary migrations. When we do need to make breaking changes, we will do our best to communicate them clearly and in advance to minimize disruption.
-   **Flexible release schedule**  
    While in beta, we will continue to create new releases of Telegraf Controller, but likely at irregular intervals. We will provide [Telegraf Controller release notes](/telegraf/controller/reference/release-notes/) to make it easy to track updates.

Provide beta feedback

-   Use the **Feedback** feature in the Telegraf Controller UI.
-   [Join the InfluxDB Community Slack](https://influxdata.com/slack) and post feedback in the **#telegraf-enterprise-alpha** channel.
-   Post feedback in the [InfluxData Community](https://community.influxdata.com).

Join our public channels

-   [InfluxDB Community Slack *(Preferred)*](https://influxdata.com/slack)
-   [InfluxData Community](https://community.influxdata.com)
-   [InfluxDB Subreddit](https://reddit.com/r/influxdb)

Resolve common installation and startup issues with Telegraf Controller. Check the symptoms below and apply the recommended fix before continuing with configuration.

-   [Port Already in Use](#port-already-in-use)
-   [Permission Denied (Linux/macOS)](#permission-denied-linuxmacos)
-   [Database Connection Issues](#database-connection-issues)
-   [Firewall Configuration](#firewall-configuration)
-   [Security Considerations](#security-considerations)

## Port already in use

If the default ports (8888 and 8000) are already in use, use the following configuration options to specify alternative ports:

| Description | Environment Variable | Command Flag |
| --- | --- | --- |
| Web Interface and API | APP_PORT | --port |
| Heartbeat server | HEARTBEAT_PORT | --heartbeat-port |

*For more information, see the [General section of the configuration options reference](/telegraf/controller/reference/config-options/#general).*

<!-- Tabbed content: Select one of the following options -->

**Use Environment Variables:**

<!-- Tabbed content: Select one of the following options -->

**Linux/macOS:**

```sh
APP_PORT=3000
HEARTBEAT_PORT=3001

telegraf_controller
```

**Windows (Powershell):**

```powershell
$env:APP_PORT=3000
$env:HEARTBEAT_PORT=3001

./telegraf_controller.exe
```

<!-- End tabbed content -->

**Use Command Flags:**

<!-- Tabbed content: Select one of the following options -->

**Linux/macOS:**

```sh
telegraf_controller --port=3000 --heartbeat-port=3001
```

**Windows (Powershell):**

```powershell
./telegraf_controller.exe --port=3000 --heartbeat-port=3001
```

<!-- End tabbed content -->

<!-- End tabbed content -->

## Permission denied (Linux/macOS)

If you do not have permission to run the `telegraf_controller` executable, ensure the file has executable permissions:

```sh
chmod +x telegraf_controller
```

### macOS: Remove the quarantine attribute

macOS places a quarantine attribute on executable files downloaded from a browser and restricts file execution. To remove the quarantine attribute, use **Terminal** or **System Settings**.

#### Remove the quarantine attribute in Terminal

```bash
xattr -d com.apple.quarantine telegraf_controller
```

#### Remove the quarantine attribute in System Settings

1. Attempt to run the `telegraf_controller` executable.
2. In macOS, navigate to **System Settings** > **Privacy & Security**.
3. Scroll to the bottom of the window.
4. Next to the message about Telegraf Controller, click **Allow**.

## Database connection issues

If there are database connection issues, check the following depending on which database you’re using:

### SQLite

-   Check file permissions for SQLite database directory

### PostgreSQL

-   Ensure PostgreSQL is running
-   Check the format of and credentials in your data source name (DSN or database URL)
-   Verify network connectivity

## Firewall configuration

Ensure the following ports are open in your network Firewall configuration:

-   **Web Interface and API**: TCP `8888` (or custom port)
-   **Heartbeat server**: TCP `8000` (or custom heartbeat port)

## Security considerations

-   **SSL/TLS**: Set the [`SSL_CERT_PATH` and `SSL_KEY_PATH`](/telegraf/controller/reference/config-options/#tls) environment variables for production deployments
-   **Firewall**: Restrict access to the web interface and heartbeat ports
-   **Database Security**:
    -   **PostgreSQL**: Use strong passwords
    -   **SQLite**: Ensure the database file is protected with restricted permissions (`chmod 600`)

#### Related

-   [Telegraf Controller configuration options](/telegraf/controller/reference/config-options/)