---
title: Servers
description: "The requirements of a database, DCS or backup server, and how to enroll a server into the private mesh of the console."
sidebar:
  icon: server
search:
  keywords: ["node", "host", "machine", "enroll"]
---

The console reaches each enrolled server through its private mesh. A server
needs no inbound access and no internet access.

## Server requirements

- **OS**: Ubuntu 26.04. On another OS, the preflight `os` row fails, and the
  console does not deploy onto the server.
- **Architecture**: x86_64 or aarch64.
- **Root access**: the enroll command runs under `sudo`.
- **`curl`**, and outbound access to the public URL of the console and to
  the mesh ports of the console: `8090`, `41641/udp` and `3478/udp`.
- **`/usr/bin/python3`**.
- **Fast `sudo`**: if DNS and `/etc/hosts` do not resolve the host name, each
  `sudo` call waits about 20 seconds. Add `127.0.1.1 <host name>` to
  `/etc/hosts`, or fix DNS. The preflight `sudo` row warns at 2 seconds.
- **A silent login shell**: a non-interactive SSH login must print nothing.
  Extra output makes pgBackRest fail. The preflight `clean_shell` row warns.
- **A stable LAN address** (recommended): a static address or a DHCP
  reservation. See [Change IP addresses](/docs/v2026.11.12-beta/operations/change-ip-addresses).
- **The [server packages](/docs/v2026.11.12-beta/server-packages)** for the OS of the server,
  loaded into the console.

The preflight warns when a server has less than these minimums:

| Server | vCPUs | Memory | Free disk |
| --- | --- | --- | --- |
| PostgreSQL | 2 | 4 GB | 10 GB on `/var/lib`, or on the data directory |
| DCS (etcd) | 1 | 1 GB | 2 GB |

## Enroll a server

You need the admin role.

1. **Get the enroll command**

    In **Infrastructure → Servers**, click **Register new server**. Enter an
    optional name and click **Add server**. The **Add a server** panel shows
    a one-line enroll command.

    ![The Add a server panel with the enroll command](/docs/screenshots/v2026.11.12-beta/servers/add-a-server.light.webp)

2. **Run the command on the server**

    Copy the command and run it on the server. The log is
    `/opt/tse/tailscale/enroll.log`.

3. **Wait for the join**

    The panel shows "The server is in the mesh and ready." The server is
    then **Free** in the list. Its health shows within one minute.

- An enroll command works once. It expires after 1 hour. You can retry a
  failed run for 10 minutes after the first run. After that, use
  **Re-enroll command**.
- The mesh agent is Tailscale (service `tse-tailscaled`, interface `tse0`,
  port `41642/udp`). Another Tailscale on the server can block the mesh,
  because both use `100.64.0.0/10`. A member of another tailnet is not
  supported as a database server.
