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

# Panel configuration

> How the Axottle panel is configured: environment variables, axottle.env file, order of safe setting changes.

The Axottle panel is configured by **only through the environment variables** with the prefix `AXOTTLE_*`. There is no separate configuration file in YAML/TOML format: in production, all variables are set in an env file that systemd transmits to the panel process at startup.

The configuration is read once at the start of the process, and the full list of default variables is available on ['s ](https://docs.axottle.com/en/reference/environment-variables.md) environment variables.

> [!NOTE]
>
> For whom: Administrator, SRE. Required rights: root (or sudo) on the panel server - env file is available only to privileged users.

> [!WARNING]
>
> Any change to any `AXOTTLE_*` variable will only take effect after the \*\*\*\* `axottle` service is restarted. editing the env file without restarting does not change the behavior of the running panel.

## Where the configuration lives

| What? | Where. | Commentary |
| - | - | - |
| Env file panel | `/etc/axottle/axottle.env` | Created by installer; rights `640`, owner of `root:axottle` |
| Systemd unit | `axottle.service` | Connects env file via `EnvironmentFile=`, launches `/opt/axottle/bin/axottle serve` from `axottle` user |
| Installation Root | `/opt/axottle` | Binary, migrations, data directory, installer files |
| Data Catalog | `AXOTTLE_DATA_DIR` (in production `/opt/axottle/data`) | panel update log, local backups |

The main data is stored in the **PostgreSQL** (DSN is set by the `AXOTTLE_DB_URL` variable). The migration scheme is applied automatically at each start of the `axottle serve` - before the panel begins to receive traffic.

> [!NOTE]
>
> The administrator password reset command connects directly to PostgreSQL and must see the configuration of the installed panel.The Doctor also uses this configuration to check the database, but does not stop the diagnosis if PostgreSQL is not available.

## Safely modifying the configuration

**1. Save the current version of the env file**

```bash theme={null}
sudo cp /etc/axottle/axottle.env /etc/axottle/axottle.env.bak
```

You'll need a copy to roll back. Don't keep backups of the env file in public directories -- the file contains secrets.

**2. Edit the variables**

```bash theme={null}
sudo nano /etc/axottle/axottle.env
```

The format is `AXOTTLE_PORT=8080` strings, one variable per row. The real values of the secrets are not shown here - use yours.

**3. Restart the service**

```bash theme={null}
sudo systemctl restart axottle
```

The restart briefly interrupts access to the panel and API, and when it starts, the panel automatically applies database migrations.

**4. Check the health of the panel**

```bash theme={null}
curl -s http://localhost:8080/health
```

Expected response:

```json theme={null}
{"status":"ok","timestamp":"2026-07-11T00:00:00Z","version":"<версия>"}
```

Then look at the logs for start errors:

```bash theme={null}
axottle logs backend --tail 50
```

## Verification

> [!TIP]
>
> The panel is considered to be successfully reconfigured when after restart `GET /health` return `"status":"ok"`, `axottle status` pointer `running`There are no initialization errors in the logs.

```bash theme={null}
axottle status
```

Example of conclusion:

```text theme={null}
Status:      running
Version:     <версия>
DB:          connected
Setup done:  true
Uptime:      42s
```

The command ends with non-zero code if the status is different from `running` – convenient for scripts.

## Rollback

**1. Return the saved copy.**

```bash theme={null}
sudo cp /etc/axottle/axottle.env.bak /etc/axottle/axottle.env
```

**2. Restart the service and check.**

```bash theme={null}
sudo systemctl restart axottle
curl -s http://localhost:8080/health
```

## Limitations and risks

* **Restart is mandatory for any change.** A modified env file without restart creates a discrepancy between “what’s on the disk” and “what works” – a common cause of diagnosis confusion.
* **Secrets in the env file.** `AXOTTLE_SECRET_KEY` Encrypt the storage of the secrets of the panel, set a strong value in production and restrict access to the file (installer sets). `640 root:axottle` - do not weaken these rights. [variables](https://docs.axottle.com/en/reference/environment-variables.md#axottle_secret_key).
* **The error DSN base** (`AXOTTLE_DB_URL`) will not allow the panel to rise. Check the logs immediately after restart.

## Typical errors

> [accordion] Changed the variable, but the behavior didn't change.
>
> Most likely, the service is not restarted. Run `sudo systemctl restart axottle` and check `systemctl status axottle`.

> [accordion] The panel does not start after editing the env file.
>
> Check the syntax of the file (one variable per line, no spaces around `=`), then log: `journalctl -u axottle -n 100`. If the reason is not clear, roll back the file and restart the service.

> [accordion] Doctor or password reset can't connect to database
>
> Run commands on the panel server via `sudo`. In TUI, open **Doctor** and select **Attempt safe recovery** — the tool will try to lift PostgreSQL and repeat the check. If this does not help, check the PostgreSQL container or service and the `AXOTTLE_DB_URL` configuration in the env file installed panel.

## Related pages

> [card] [Environment variables](https://docs.axottle.com/en/reference/environment-variables.md)
>
> A complete table of all variables of `AXOTTLE_*`.

> [card] [CLI axottle](https://docs.axottle.com/en/reference/cli.md)
>
> Team status, doctor, logs and others.


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