I am trying to install HestiaCP on ubuntu 24.04
but get the error. How I can install?
Installation aborted
====================================================================
ERROR: Install script version does not match package version!
Please download the installer from the release branch in order to continue:
https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
To test pre-release versions, build the .deb packages and re-run the installer:
./hst_autocompile.sh --hestia branchname no
./hst-install.sh .. --with-debs /tmp/hestiacp-src/debs
Error: Installation aborted
I found this information on the forum and then installed it on ubuntu:
apt install systemd-timesyncd
It really seems that ubuntu 24.04 and not even Amazon 22.04 have this feature installed.
I don’t know if a later installation will solve the problem or if I’ll have to install hestia again.
According to Copilot IA:
systemd-timesyncd is a daemon that synchronizes the system clock with a remote time server using the Simple Network Time Protocol (SNTP). It is designed to be a simple and efficient solution for keeping the system clock synchronized, especially on systems that don’t have a real-time clock (RTC) or on embedded devices.
I would suggest that if timesyncd is required then it needs to go on a pre-requisite list or be added to the list of packages hestia downloads when you install it.
@tucano2000 I assume you are not running live workloads on this server as it’s beta… so it would probably be good for the community and for the dev team if you could create a clean server, install timesyncd then install hestia and see if that resolves the issue.
(my 2p worth, I am not part of the dev team)
(edit to correct spelling)
@garethw I installed it on clean, newly-created server instances, both on 24.04 and 22.04, just running the apt update and apt upgrade commands before installation to make sure that before installing Hestia, the latest versions of the Ubuntu packages were up to date.
My reply was kinda in response to this bit. Personally I’d wipe the server, update package repos and packages, install timesyncd then re-try the Hestia install to see if it works without error this time.
That way you have a known good system (with the “it’s beta” caveat.) and the team know that installing timesyncd probably needs to be a pre-requisite. Unless you are happy to go edit the installer, put it in yourself and then issue a patch / pull (I’ve not looked at how the project does colaboration stuff)