Skip to content
On this page

Beta and release candidate testing


If there is a beta or release candidate available, we will announce it via our Discord server or our forum.

In the last few months, we have seen a growing number of issues when releasing minor and major updates. To prevent this from happening, we have decided to setup a beta apt server so we can push more regular updates, enabling us to test at a larger scale than only 4 or 5 users.

Activating the beta repo on an existing install


Betas and release candidates might still contain bugs and can possibly break your server. We cannot guarantee it will be fixed directly! Please be careful when testing on servers in production or containing important data!

Run the following commands as root:

# Collecting system data
case $(arch) in x86_64) ARCH="amd64" ;; aarch64) ARCH="arm64" ;; esac
codename="$(lsb_release -s -c)"

# Add the beta repo to hestia.list
sed -i 's/^/#/' $apt/hestia.list
echo "deb [arch=$ARCH signed-by=/usr/share/keyrings/hestia-beta-keyring.gpg] $codename main" >> $apt/hestia.list
curl -s "" | gpg --dearmor | tee /usr/share/keyrings/hestia-beta-keyring.gpg > /dev/null 2>&1

# Update to the beta version
apt update && apt upgrade

Install from beta repo

If you want to install a new Hestia installation form the beta server.

# Debian
# or Ubuntu

Then install via bash or bash

Disabling the beta repo

Edit /etc/apt/sources.list.d/hestia.list and remove the # in front of, and add a # in front of

Once that’s done, run apt update && apt upgrade to rollback to the regular release.

Reporting bugs

If you encounter a bug, please open an issue or submit a Pull Request. You can also report it on our forum or our Discord server

Released under the GPLv3 License.