> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Environment variables

> A complete directory of AXOTTLE_* panel environment variables, CLI and update script.

A reference table of all Axottle environment variables, how and where to prescribe them, is available on the [panel configuration](https://docs.axottle.com/en/reference/configuration.md).

> [!NOTE]
>
> For whom: Administrator, SRE. Required rights: root (or sudo) on the server of the editing panel `/etc/axottle/axottle.env`.

> [!WARNING]
>
> There is no hot reboot: the panel reads the configuration once at the start of the process. For all panel variables, the **rule applies "restart: yes"** - the change takes effect only after `sudo systemctl restart axottle`.

All examples use placeholders like `<значение>` -- frame your data. Never copy the examples of secrets from the documentation.

## The main variable panels

| | Default | Mandatory | Controls | Restart | |
| - | - | - | - | - | - |
| `AXOTTLE_HOST` | `0.0.0.0` | no | Address where the panel receives | connections da | |
| `AXOTTLE_PORT` | `8080` | no | Panel port (API + built-in web interface) | da | |
| `AXOTTLE_DB_URL` | local dev base | **da (production)** | DSN PostgreSQL, for example `postgres://<user>:<password>@localhost:5432/axottle?sslmode=disable`. Default value is designed for the development environment - in production, specify explicitly | da | |
| `AXOTTLE_DATABASE_URL` | not specified | no | Separate DSN PostgreSQL for backup dump utility. If not specified, use `AXOTTLE_DB_URL` | da | |
| `AXOTTLE_SECRET_KEY` | built-in | **Yeah (production)** | The master key encrypts the storage of the secrets of the panel; is also used by the backup subsystem. | yes | |
| `AXOTTLE_DATA_DIR` | `./data` | no | Data Catalog: log and block panel updates, local backups. In production - `/opt/axottle/data` | da | |
| `AXOTTLE_PUBLIC_URL` | `http://<host>:<port>` | is recommended by | Public Base URL, where **agents nod** access the panel. Without it, agents receive an address collected from the host/port - for external nodes, specify explicitly | da | . |
| `AXOTTLE_LOG_LEVEL` | `info` | no | Logging Level; `debug` includes debugging logs | da | |
| `AXOTTLE_DEV_MODE` | `false` | No | Development Mode: Includes dev panel settings. **Do not include in production** | da | |
| `AXOTTLE_MIGRATIONS_DIR` | not specified | no | Clear path to database migration catalog. If not specified, the panel looks for migrations by standard paths: `<AXOTTLE_DATA_DIR>/migrations`, `/opt/axottle/migrations`, `/usr/local/share/axottle/migrations`, `./migrations` | da | |
| `AXOTTLE_SUPPORT_SERVER_URL` | not specified | no | Support Server Address for Downloading Support Bands Doctor. Supports outdated synonym `AXOTTLE_MAIN_SERVER_URL` | da | |

### `AXOTTLE_SECRET_KEY`

> [!WARNING]
>
> **Security Critical.** This is a master key for encrypting the storage of panel secrets (integration credentials, tokens, etc. are stored in the database in encrypted form). In production **necessarily** set your own strong value - the built-in default value is designed only for development and is not secure.
>
> The recommended key is 32 bytes of random data; a raw 32-byte value, 64 hex characters, or 44 base64 characters are accepted.
>
> ```bash theme={null}
> openssl rand -hex 32
> ```
>
> Change the key with caution: it is used to decrypt already stored secrets, and after changing the key, previously encrypted data will become unavailable. Store the value only in `/etc/axottle/axottle.env` (`640` rights, `root:axottle`) and in your secret manager.

## Bootstrap Remnawave

These variables are recorded by the installer when installed with the `--with-remnawave` flag. They control the one-time automatic binding of the Remnawave panel during the initial setup.

| | Default | Mandatory | Controls | Restart |
| - | - | - | - | - |
| `AXOTTLE_RW_BOOTSTRAP` | `false` | no | Allows Remnawave Autobound endpoint when first setup. When turned off, autobound request returns `409` | da |
| `AXOTTLE_RW_URL` | `http://127.0.0.1:3000` | no | Loopback address Remnawave | da |
| `AXOTTLE_RW_ADMIN_USER` | `admin` | No | Name of Remnawave super-administrator registered by | da |
| `AXOTTLE_RW_ADMIN_PASSWORD` | is not specified by | Yes (for bootstrap) | Password superadministrator Remnawave | da |
| `AXOTTLE_RW_EXPOSURE` | `localhost` | no | How the Remnawave API saved URL is generated: `localhost`, `domain` or `port` | yes |
| `AXOTTLE_RW_DOMAIN` | not specified by | at `exposure=domain` | Public domain Remnawave | da |
| `AXOTTLE_RW_PUBLIC_PORT` | not specified by | at `exposure=port` | Public port Remnawave | da |

## Auxiliary variables of backups and updates

| | Default | Mandatory | Controls | Restart |
| - | - | - | - | - |
| `AXOTTLE_UPGRADE_SCRIPT` | `/opt/axottle/installer/upgrade.sh` | no | The path to the script that triggers the button **Update now.** panel | yes |
| `AXOTTLE_PG_DUMP_PATH` | not given | no | Clear path to `pg_dump` binarnic for backups (if not in `PATH`) | da |
| `AXOTTLE_PG_RESTORE_PATH` | not given | no | Clear path to `pg_restore` binarnic to restore | da |
| `AXOTTLE_PGTOOLS_CONTAINER` | is not specified by | no | The name of the Docker container inside which to run pg utilities if they are not installed on the host | da |

## CLI variables

These variables are read by the CLI `axottle` every time a command is run – no restart service is needed.

| | Default | Mandatory | Controls | Restart |
| - | - | - | - | - |
| `AXOTTLE_API_URL` | `http://localhost:8080` | no | Basic Panel URL for CLI commands (similar to `--api` flag) | — (read at each CLI launch) |
| `AXOTTLE_API_TOKEN` | not specified | no | Bearer-token for API calls CLI (analogue of the flag `--token`) | — (read at each launch of CLI) |
| `AXOTTLE_LANG` | is not specified by | no | `ru` compulsorily includes Russian CLI output; the language is also determined automatically from `LANG=ru*` | — (read at each CLI run) |

## Variables of the update script

Read the `upgrade.sh` script every time an update is launched.

| | Default | Mandatory | Controls | Restart |
| - | - | - | - | - |
| `AXOTTLE_HTTP_CONNECT_TIMEOUT` | `20` (sec) | no | Timeout of HTTP connection installation when downloading the artifact | — (read when starting the script) |
| `AXOTTLE_HTTP_MAX_TIME` | `600` (sec) | no | Maximum download time of the artifact | — (read when starting the script) |
| `AXOTTLE_HTTP_RETRIES` | `3` | no | Download number | - (read when starting the script) |

## Node agent variables

The agent (`axottle-agent`) is a separate binary with its prefix `AXE_*`. Its variables (`AXE_URL`, `AXE_TOKEN`, `AXE_STATE_PATH`, `AXE_LOG_LEVEL`) are written into the `/etc/axottle-agent/agent.env` with the installation script that generates the panel, and manual editing is not usually required. The change requires a restart of the agent service on the node.

## Safety recommendations

* Set a strong `AXOTTLE_SECRET_KEY` before the panel is commissioned and never use the default value in production.
* Specify `AXOTTLE_DB_URL` explicitly, with a separate database user and a strong password.
* Restrict access to `/etc/axottle/axottle.env` (installer sets `640` rights, owner of `root:axottle` - do not weaken them) and to the panel server as a whole.
* Do not enable `AXOTTLE_DEV_MODE` in production; enable `AXOTTLE_RW_BOOTSTRAP` only during initial setup.

## Related pages

> [card] [Panel configuration](https://docs.axottle.com/en/reference/configuration.md)
>
> Where does the env file live and how to change settings safely?

> [card] [CLI axottle](https://docs.axottle.com/en/reference/cli.md)
>
> Flags of `--api` and `--token`, diagnostic teams.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.