Skip to main content
A reference table of all Axottle environment variables, how and where to prescribe them, is available on the panel configuration.
For whom: Administrator, SRE. Required rights: root (or sudo) on the server of the editing panel /etc/axottle/axottle.env.
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

AXOTTLE_SECRET_KEY

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.
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.

Auxiliary variables of backups and updates

CLI variables

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

Variables of the update script

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

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.

Panel configuration

Where does the env file live and how to change settings safely?

CLI axottle

Flags of --api and --token, diagnostic teams.