Installation

Install on your own server

Builds for Linux and Windows. A few steps from the archive to a running system — no Docker and no extra setup.

Requirements

What you need before you start

A regular server or computer in the farm network will do: the system is a single program file with a built-in database.

  • LinuxWith systemd, amd64 or arm64Ubuntu, Debian and other distributions with systemd. uname -m shows the architecture: x86_64 means amd64, aarch64 means arm64.
  • WindowsWindows 10 or 11, 64-bitA regular computer in the farm network will do. No installer needed: the system runs from a folder.
  • NetworkThe same network as the minersThe server must reach the miners on TCP ports 4028 and 80.
  • InternetOutbound HTTPSTo hash-hut.net or hash-hut.ru — for the first key activation and a licence check once a day.

Step by step

Up and running in minutes

Pick the system the monitoring will run on.

Four steps for a user with sudo. The installer needs no internet.

  1. Download the archive

    In the cabinet, pick the build for your server's processor: amd64 for Intel and AMD, arm64 for ARM. The "Command for the server" button gives you a ready-made command to download the archive right on the server.

  2. Run the installer

    Unpack the archive and run the installer: it sets the system up as a service and starts it.

    Unpack and install
    mkdir -p /tmp/hhm && tar xzf hashhut-monitor_*_linux_*.tar.gz -C /tmp/hhm && cd /tmp/hhm && sudo ./install.sh
  3. Create the administrator

    Open http://<server>:8443 in a browser — the system runs on port 8443 by default. The command below prints a one-time token: enter it, then choose a login and a password of at least 12 characters.

    One-time token
    sudo -u hashhut /opt/hashhut-monitor/hashhut-monitor -config /etc/hashhut-monitor/config.yaml -bootstrap-token
  4. Activate the key

    Paste the key from the cabinet on the License tab. The first activation goes through the licence server, so internet is needed at this moment.

Under the hood

What the installer does on Linux

A plain POSIX script with no dependencies. Run it again from a newer archive and it becomes an update.

  • Creates the system user hashhut — no shell, no home directory.
  • Puts the program, sing-box and THIRD-PARTY.md into /opt/hashhut-monitor.
  • Creates /etc/hashhut-monitor/config.yaml; an existing config is never overwritten.
  • Prepares /var/lib/hashhut-monitor for the database, readable only by the service.
  • Installs the hashhut-monitor service and the units for in-app updates.
  • Validates the config before the start, starts the service and checks that it came up.

The service runs as hashhut inside a systemd sandbox: no privileges, system directories read-only. Running the installer again from a newer archive updates the program and keeps the config, the database and the users.

Third-party software

The Linux archive includes sing-box — a separate program licensed under the GNU GPL, version 3 or later. It runs as its own process and is used only for the Telegram proxy; if no proxy is configured, it is never started. It is not part of Hash-Hut Monitoring.

Its licence terms are in THIRD-PARTY.md inside the archive; the complete source code is in the project's repository.

sing-box source codegithub.com/SagerNet/sing-box(opens in a new tab)

Ready to install

The archive and a trial key are in the cabinet

Sign in with your Hash-Hut account: the latest version for Linux and Windows and a 14-day key are waiting there.