Installing HiTechCloud

This installs the host-services stack: every service runs on the host under systemd. The older container (podman/docker) installation is retired and PODMAN_INSTALL.sh is gone; to move a server that still uses it, see Move off the container stack.

Before you start​

• A fresh server (virtual or bare metal) running a supported release: Ubuntu 22.04, 24.04 or 26.04, Debian 11, 12 or 13, or AlmaLinux, Rocky, RHEL or Oracle Linux 8 and above. The installer refuses anything else.
• An amd64 (x86_64) or arm64 (aarch64) CPU.
• Enough memory for what you will run: see System requirements, including the notes for AlmaLinux and RHEL 10.
• A PTR record for the server's IP address if it will send mail.

Install​

1. Log in to the server as root over SSH, or as a user with sudo rights and run sudo -i.
2. Run the installer:

bash <(curl -sSL https://hitechcloud.org)

The installer downloads hitechcloudcli for this machine's architecture from the mirror, checks the release's SHA256SUMS against its Ed25519 signature and the binary against SHA256SUMS, and only then hands over to hitechcloudcli server-install. A download that does not verify is not run, and nothing is installed.

The installer accepts optional flags to choose what is installed, skip steps or show debugging output.

After the install​

1. Sign in. The hosting panel answers on port 2083 and, on Enterprise, the admin panel on port 2087. The installer prints both addresses and the administrator's credentials when it finishes.

2. Turn the firewall on. ConfigServer Firewall is installed switched off, so that a rule cannot lock you out during the install:

   hitechcloudcli firewall on
   

   See hitechcloudcli firewall.

3. Add a licence key if you have one, from the hosting panel's Activate Enterprise page or with hitechcloudcli license <key>. See Community and Enterprise.

4. The customer portals. Mail (2091), DNS (2092) and S3 (2093) are installed and on by default; switch any of them off with hitechcloudcli portals disable <portal>, or install with HITECHCLOUD_NO_PORTALS=1 to leave all three out. See Customer portals.

5. Secure the server for production use: Securing HiTechCloud.

If something failed​

The installer reports what did not install and why, and goes on with the rest where it can. Re-run a single component with hitechcloudcli install --extras-only --with <component>. Common cases (the login page loop, ClamAV, SQL Server on AlmaLinux 10, stuck background tasks) are in Troubleshooting.

If you still need help, post the installer's output on the community forums.