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

# Journal of Changes

> Axottle Change Log Policy and Release Recordings.

This shows product changes from release to release, and the page goes forward: historical releases prior to the initial release are not retroactively described.

## Policy of conduct

Each release of Axottle receives a record of four sections (empty sections are omitted):

| Section | What Hits |
| - | - |
| **New** | New features and capabilities |
| **Modified** | Changes to existing behavior, including incompatible (marked separately) |
| **Corrected** | Error Corrections |
| **Security** | Security-related fixes and enhancements |

> [!NOTE]
>
> The entries describe the behavior of the product that is visible to the operator - interfaces, commands, APIs. Internal implementation changes are not logged. If the release requires actions when updating (for example, new environment variables), this is indicated directly in the record.

How to install updates and how to automatically roll back when an unsuccessful update works – see [Panel Updates](https://docs.axottle.com/en/operations/updates.md).

***

## Additional documentation - 2026-09-22

Instructions for the latest infrastructure changes have been added:

* [Import of Remnawave to Flow](https://docs.axottle.com/en/connection-units/remnawave-import.md): analysis
  approval of the observed image, clarification and transformation into a controlled draft.
* [Park HAProxy](https://docs.axottle.com/en/connection-units/haproxy-park.md): connections, pools
  Operations and port rotation with a compatibility window.
* [WARP](https://docs.axottle.com/en/connection-units/warp.md): local SOCKS proxy and native WireGuard.
* [External PostgreSQL](https://docs.axottle.com/en/remnawave/external-database.md): Installation or verification
  existing base, transfer with confirmation and return of the original connection.
* [Transfer Remnawave](https://docs.axottle.com/en/remnawave/migration.md): transfer of the panel with the data
  Switching an existing Axottle connection.

External database backups are refined, the choice of PostgreSQL tools during the update
and deleting the Telegram proxy with an unavailable node.
2026-09-22; this entry does not declare a release publication or live test.

## Additional documentation - 2026-09-08

Changes since the previous review, including new infrastructure management features and v1.7.1 preparation, have been verified. [Telegram proxy](https://docs.axottle.com/en/connection-units/telegram-proxies.md), [node](https://docs.axottle.com/en/nodes/domains.md), [Bscheck](https://docs.axottle.com/en/health/bscheck.md) and [Separate updates to Statuspage](https://docs.axottle.com/en/statuspage/updates.md)Complemented with Cloudflare, Flow enforcement, notifications, audits and updates of old agents.

## v1.7.1 — 2026-09-08

### Corrected

* Compatible old agents can go to the updater with a result check and a local return to the previous binarnik. A late answer to the problem does not change the completed update result.
* When you install a subscription page next to your local Remnawave, the container connects to the network of the found backend.
* Compatibility of internal host squad restrictions with Remnawave 3.3 and 3.4 formats is maintained.
* Measurements of protection signals, Statuspage status and processing of unavailable statistics have been refined.

The update is launched by the operator from the panel. [Description of the release](https://github.com/Axottle/axottle-releases/releases/tag/v1.7.1).

## v1.7.0 — 2026-09-07

### New.

* Flow Studio: individual draft, applied version and health states; application plans, transit pools, Flow Guard, analytics, and Failure Lab.
* Telegram Proxy Park with MTProto and WEB, separate links and installation operations.
* Multiple domains per node with their own DNS settings and certificates; domain choice in Flow and Telegram WEB
* Built-in Cloudflare setup, mass actions on nodes, Bscheck history and Telegram repeats by category.
* Separate Statuspage updates and feature presentation, history, incidents and service settings.

### Modified.

* The operator name of Connection Unit has been changed to Flow; technical URLs and rights are retained.
* Forced application requires risk-taking and bypasses only limited readiness checks, and configuration errors and detected port conflicts continue to block application.
* Node and group audits reflect transaction results and object differences; older HTTP request records are available as technical history.

[Release Description](https://github.com/Axottle/axottle-releases/releases/tag/v1.7.0). Instructions are code-checked; availability and condition of your infrastructure are checked upon update.

## Reconciliation of documentation - 2026-09-06

The documentation has been updated with the current workbench code, and this record does not announce the release or deployment of a new version.

* Connection Unit in operator instructions is called **Flow**, the panel section is **Configs / Flow Studio**. Documentation addresses and APIs are saved.
* Instructions for drafts, application plans, pool pictures and rollbacks have been updated.
* Transit pools with own canvas, balancing, Flow Guard and Failure Lab are added.
* Fixed the limitations of auto-recovery and described the difference between the calculation, live checks and the version used.
* Assignments of several GeoAssets profiles per node have been specified.
* The current Flow Studio branch, the previous functional branch and installer hotfixes are verified: confirmation of the saved domain, dependency preparation, nginx/TLS and registration of Statuspage.
* Expanded are REALITY checks, managed application of multiple Flows, page placement for proxy, and limited SelfSteal validation.
* Updated signature releases, agreed rollback updates from the database, the history of S3-storage, the queue of the agent and the diagnosis of channel quality.

## v1.5.2 — 2026-08-03

### New.

* Remnawave can be put as a reverse proxy, and the installer offers this option first: this is the only way its web interface works. [Quick start.](https://docs.axottle.com/en/getting-started/quickstart.md).
* The Remnawave update works when it is on a separate server: the agent installed there performs the image change. [Remnawave Update](https://docs.axottle.com/en/remnawave/updates.md).
* The application of the circuit synchronizes the attached Remnawave connection before the gun, and the panel updates the local shot itself every 10 minutes. [The life cycle](https://docs.axottle.com/en/connection-units/lifecycle.md#что-происходит-при-применении).
* The application refuses to publish a domain that does not have a record in the DNS, and offers to confirm the rollout if the record is still on the way.

### Modified.

* Chronicle of tab checks **Health** It was rewritten for the operator: each sample has its own name, the error text is parsed out in ordinary words, a hint is taken to parse, and the raw test response remained in the open line.
* The `not_implemented` validation status is called “Unfulfilled” instead of “Unimplemented.”
* The SelfSteal plaque on the node card lists the unlocked blockers, leads to the desired tab, and hides on the cross. See [Masking](https://docs.axottle.com/en/security/masking.md).

### Corrected

* The service health user was not saved in the panel, which is why all end-to-end checks of schemes answered “not prepared”.

***

## v1.5.1 — 2026-08-02

### New.

* Remnawave panel update from Axottle: version selection, automatic backup before start and rollback if failure. See [Remnawave](https://docs.axottle.com/en/remnawave/updates.md) Update.
* The installer asks which version of Remnawave to put and offers the latest fixed versions from the registry.

### Modified.

* Axottle works with both 2.x and 3.x Remnawave: the version is determined by the panel response. Installer puts the third major, moving the version of the original panel.

### Corrected

* Remnawave installation, broken with 3.0.0 output in the floating tag.
* Remnawave panel binding is brought to the end on a clean installation.

***

## v1.5.0 — 2026-07-31

### New.

* The customer support module within the panel: Telegram channels, ticketing, SLA, attachments, knowledge base and AI circuit. See [Customer Support](https://docs.axottle.com/en/support/overview.md).
* Log in via Telegram and account rights. See [Log in via Telegram](https://docs.axottle.com/en/panel/telegram-login.md), [Access rights](https://docs.axottle.com/en/security/authorization.md).
* Search the entire panel and work from the panel on the phone.
* Move Remnawave to another server from the panel.

***

## 2026-07-11

> [!NOTE]
>
> Initial release of documentation.This entry captures the starting point: the status of the product is documented according to the current version; changes to subsequent releases are described here in the format given above.

### New.

* Published Russian documentation Axottle: start, panel, Connection Units, nodes and agents, health and security, operations (backups, updates), reference (configuration, environment variables, CLI, error codes).

***

> [!NOTE]
>
> Full notes for each release - on the release page in [Axottle/axottle-releases](https://github.com/Axottle/axottle-releases/releases).


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