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

# Encryption and TLS

> TLS for panel, node certificates and data encryption in Axottle.

Encryption in Axottle covers transport (TLS for panels and nodes) and disk data (secrets and backups). This page describes what is automatically configured and what requires operator attention.

> [!NOTE]
>
> For whom: Administrator and SRE.

## TLS for panel

TLS for the panel is configured automatically during the installation phase: the installer deploys a reverse proxy that completes the TLS and publishes the panel on your domain.

> [!WARNING]
>
> The panel cannot be published without a built-in proxy with TLS. Do not open the panel port directly to the Internet - all external traffic must go through a reverse proxy over HTTPS.

**1. Select a domain when installing**

Specify the domain of the panel - the installer will configure the release and update of certificates.

**2. Prefer automatic certificates**

Let’s Encrypt – Recommended: Certificates are issued and renewed without manual intervention.

**3. Check availability of release ports**

To issue certificates, the installer checks the availability of standard HTTP/HTTPS ports.

## Certificates of nodes

Each node has a certificate mode:

| Mode | Value | |
| - | - | - |
| `none` | Certificate not used by | |
| `auto_issue` | Panel initiates automatic release of | |
| `install_later` | Release Delayed by | |
| `existing` | Uses the existing | certificate |

Inspection and issuance of the certificate are performed as agent tasks. Each node panel displays the metadata of the certificate: publisher, expiration date, rest of days, DNS names, last error, source. Before release, the panel can automatically create the desired DNS record through AutoDNS integration and returns an understandable error if there is no suitable DNS zone. [DNS](https://docs.axottle.com/en/cdn/dns.md).

The status of the certificate is also taken into account in the readiness checklist of the cloaking site: an expired or missing certificate blocks the installation. [Cloaking](https://docs.axottle.com/en/security/masking.md).

## Data on the disk

* **Secrets.** Third-party credentials are encrypted into a secret repository under a master key – see [Secrets](https://docs.axottle.com/en/security/secrets.md).
* **Backups.** Backup Archives can be encrypted (included in the backup profile) - see [Backups](https://docs.axottle.com/en/operations/backups.md).
* **Database Dashboard.** The database is not encrypted at the entire application level. Protect it with host tools: limit access to the server and database files, use disk encryption if necessary, and store encrypted backups in a separate location.

## Transport panel  ⁇  agent

Agents are authenticated on the panel with specific node tokens and access the public address of the panel. Transport encryption provides the same reverse proxy with TLS as for the web interface - so a properly configured TLS panel protects communication with agents.

## Verification

> [!TIP]
>
> The panel only opens on `https://` with a valid certificate; direct HTTP access to the port of the panel is closed from the outside; the nodes in the panel show the validity of certificates with a positive balance of days.

## Rollback

* Problem Node Certificate Reissue the Release Task or Switch Node Certificate Mode.
* TLS panel settings are controlled by the installer’s reverse proxy; if you have issues with release, check for DNS and port availability, then re-release.


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