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

# Updating the panel

> Verification of release signature, database backup and agreed rollback of files and data.

The panel detects new versions; the update performs a separate installer process; it survives the Axottle service stop and checks the result after the new version is launched.

## Before the update

1. Check the source of updates and the selected version in the dashboard. Stable and pre-channels can contain different features.
2. Make sure that backup storage, disk space and PostgreSQL tools are available.
3. Create a fresh [backup copy of](https://docs.axottle.com/en/operations/backups.md), check its integrity and save access to the server during the update.
4. View the limitations and migrations of the selected release, then run the update in the panel.

## What's being tested

A modern official installer checks not only the SHA-256 of the archive, but also the signature of the checksum file. A missing or incorrect signature stops the installation. Disabling the check through a flag or environment variable is not a supported bypass.

An old upgrader already installed may not have this verification. When switching from an old installation, use the current official installer from a trusted source; having a signed archive does not in itself update the verification script.

## Procedure for updating

For the database archive, the installer first tries `psql`, `pg_dump` and `pg_restore`.
The `pg_dump` version must not be lower than the main version of PostgreSQL.
For external databases need working client tools and access configured
`AXOTTLE_DB_URL`The neighboring old Docker container is not selected by name only:
Backup path through Docker checks published loopback port and base name
with the panel plugged in.

The verified update dump is stored separately from regular backups:
by default in `/opt/axottle/data/backups/upgrades`, the path can be set through
`--backup-dir` or `AXOTTLE_UPGRADE_BACKUP_DIR`. Save the dump together with the `.meta`;
The exact path is displayed in the update report.

* Before stopping and replacing the panel, the database archive is created and checked. If the preparation of the archive fails, the installed panel is not replaced.
* A set of the previous release is saved: binary, migrations, installation files and associated service release files.
* The service stops, the new kit is installed and started.
* Check the health of the running panel. If you fail, you start a coordinated rollback.

Do not close the report until the final state, the update log and `journalctl -u axottle.service` will help distinguish between a new version failure and a recovery failure.

## Verification

Verify the requested and actually running version, the completion of the operation and the availability of the dashboard. Check the database, agents and key pages. `/ping` availability confirms the start of the process, but does not replace the validation of the desired work scenarios.

## Rollback

If the update fails, the current upgrader first stops the unsuccessful process, then restores the verified database archive and the full saved set of the previous release, then launches the previous panel and checks the health and version.

If the database or files fail to roll back, the panel is left stopped, and the report indicates the cause and path to the stored archive. Do not run an arbitrary version over the partially restored database: complete the recovery of the data and the corresponding set of files.

For a later manual rollback, use the paths and instructions of a specific operation. Returning only the binary and migration catalog is not enough after the new version may have changed the database. If you need to go back to the archive before the update, consider the loss of changes that appeared after its creation.

## Component compatibility

For the capabilities of the old agent, you may need [Preparatory transition update](https://docs.axottle.com/en/nodes/updates.md#старый-агент-без-механизма-отката). For a new service API and Statuspage design, check the [version of the application page](https://docs.axottle.com/en/statuspage/updates.md). The version of the panel itself does not confirm the version of the remaining components.

## Selected updates

[Agents ](https://docs.axottle.com/en/nodes/updates.md), [Remnawave](https://docs.axottle.com/en/remnawave/updates.md) and deployed pages have their own operations. Successful dashboard update does not mean that they all updated at the same time.

Features depend on the installed build; the record does not announce the release.


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