---
title: Upgrade
description: "Upgrade the console to a new release with the installer: online, bundle and airgapped installs, and the server packages of the new release."
sidebar:
  icon: circle-arrow-up
---

Run the installer of the new release in the install directory, and select
**Upgrade or repair** (the default). The installer keeps `.env`.

- **Online install**: run the `curl ... | sh` command of
  [The installer menu](/docs/v2026.11.7-beta/installation#the-installer-menu) again, with the same `--dir`.
- **Bundle install**: extract the new bundle into the install directory, then run the
  installer:

  ```bash
  cd /path/to/timescale-enterprise
  tar -xzf /path/to/timescale-enterprise-<new-tag>-console-<arch>.tar.gz
  ./timescale-enterprise.sh
  ```
- **Airgapped install**: see [Airgapped install](/docs/v2026.11.7-beta/installation-airgapped#upgrade).

At the end, the installer shows `Upgraded the console from <old> to <new>`.

:::warning
The console is down while it restarts. Do not reboot database servers during the upgrade. A
server that restarts while the console is down joins its cluster again only when the console
is back. See [Console outage](/docs/v2026.11.7-beta/operations/console-outage#a-node-restarts-during-the-outage).
:::

After the upgrade, the installer asks `Download them now? [Y/n]` for the server packages of the new
release. Answer `y`, or download them later in **Administration → Server packages**. Until
you load them, new services use the server packages of the earlier release, and the console
shows a warning (see
[Server packages of an earlier release](/docs/v2026.11.7-beta/server-packages#server-packages-of-an-earlier-release)).
Existing services keep their versions until you [upgrade them](/docs/v2026.11.7-beta/operations/upgrade-a-service).

Always upgrade in the same directory. If the installer finds console data on the host but no
`.env` in the directory, it stops.

## Installer update

On a terminal, a downloaded `timescale-enterprise.sh` (not the installer of a bundle) first
looks for a newer release. If there is one, it asks `A newer installer is available: <new>
(this is <old>). Update it now? [Y/n]`. `y` downloads the new installer and runs it with the
same options. Before it asks, the installer checks the signature of `SHA256SUMS` of the new
release with its [release signing key](/docs/v2026.11.7-beta/verify-a-release#the-release-signing-key), and the
sha256 of the new installer against that `SHA256SUMS`. If a check fails, it prints a warning
and continues with the old installer. To keep the installer of a specific release, set `TSE_INSTALL_SELF_UPDATE=0`.
