Table of contents

Installation

Obtaining the delivery package, running the installer, enrollment and verifying the health of all 14 services.

Deployment methodThe commands on this page apply to the Docker Compose delivery. Open the matching Kubernetes and Helm procedure.

Obtaining the package

The delivery archive massaccess-compose.tar.gz is provided in the control panel at https://massaccess.net/dashboard/on-premise. The archive contains installation data, licensing data, installation and update scripts.

License blocking warningDo not modify the package service files before running and do not run the same licensed package on additional local or test instances — this may lead to license blocking.

Running the installer

Extract the archive, enter the directory and run install.sh pointing to the manifest:

bash

tar -xzf massaccess-compose.tar.gz
cd massaccess-compose
chmod +x install.sh
bash install.sh --manifest ./manifest.json

Pre-flight check (--dry-run)

The --dry-run mode checks the environment without touching Docker: Docker Engine and Compose versions, Linux kernel, Bash/Python/curl, free disk space and ports 10001, 10002, 10011.

bash

bash install.sh --manifest ./manifest.json --dry-run

What the installer checks

Before pulling images, install.sh checks the Docker daemon, Docker Engine 24.0+, Docker Compose v2.24+, Linux kernel 5.x+, Bash, Python 3, curl, base commands, free disk space and ports. CPU and RAM are checked separately: on mismatch the installer prints required and actual values and asks for explicit confirmation. Critical errors are printed as a single list, and until they are fixed the installer does not pull images or start Compose.

Enrollment

The installer activates the connection to the license service. On rejection the administrator is shown the reason (see the Diagnostics section).

First-login credentials

The installer creates a .env file (mode 600) in the installation directory. It stores the credentials for the first login to the control panel: ADMIN_EMAIL (the company administrator email) and ADMIN_PASSWORD. The installer generates the password automatically and prints it in the terminal once during the installation — right after the environment checks — and then saves it to .env. The control panel is available at the local address http://localhost:10011/web/login. The .env file also contains the platform services' passwords and secrets — keep it in a safe place.

Health check

After installation, verify the state of all platform services with healthcheck.sh, then open the control panel at http://localhost:10011/web/login and log in with the credentials from the "First-login credentials" section.

License blocking warningDo not run the same licensed installation package on multiple instances simultaneously. The installer does not delete existing containers or volumes; if the ms-onprem project already exists, installation fails — use upgrade.sh to update.