Technical Requirements

Hardware Requirements

The minimum and recommended specifications are details below.

Component

Minimum Requirement

Recommended Requirement

Details

Disk Space

150 GB

300 GB

150 GB should allow for thousands of uploaded results, files, generated PDFs, etc. Monitor and adjust accordingly.

Memory

12 GB

24 GB

Insufficient memory may lead to performance issues, including slow or failed PDF report generation. Monitor and adjust as needed.

Processor

4 Cores @ 1.4 GHz

8 Cores @ 2.0 GHz or faster

Lower processing power may cause slow or failed PDF report generation. Monitor and adjust as needed.

Operating Systems

The following operating systems are supported:

  • Docker via Docker Compose on Ubuntu 20.04 LTS, 22.04 LTS, or 24.04 LTS

  • Red Hat Enterprise Linux (RHEL) 9.7 or later

Earlier versions of Link-Live Private supported a different set of Linux distributions. Customers upgrading from an older version should review the script changes described below.

NOTE: Software dependencies for Link-Live Private (such as Docker or Podman) are installed when you run the start script. All required software is included in the bundle and is installed without an internet connection. The installer never contacts the internet.

Installation Location

On Ubuntu, the recommended location for the installation directory is /opt. Installing elsewhere works, but ubuntu-start.sh prints a warning naming /opt as the recommended location before continuing normally.

On RHEL, install into a directory your regular user owns, such as your home directory. /opt is owned by root, and the RHEL scripts run as your regular user, not root.

Script Naming and Usage

The start script is the only script at the root of the installation directory, and the only one that carries an operating system prefix:

  • Ubuntu – ubuntu-start.sh

  • RHEL – rhel-start.sh

Every other script lives in the toolkit/ subfolder and has a plain name with no prefix, because the bundle you receive is already built for a single platform:

  • toolkit/backup.sh

  • toolkit/restore.sh

  • toolkit/cert-renew.sh

  • toolkit/export-logs.sh

  • toolkit/register-service.sh (RHEL only, and run for you automatically during installation)

On Ubuntu, run the start script and every script in toolkit/ with the sudo command, from inside the installation directory, so that Docker can access the required root privileges. Do not use sudo on RHEL systems, which run rootless Podman.

Ubuntu Examples:

sudo ./ubuntu-start.sh # Run full configuration prompt (required for first install).

sudo ./ubuntu-start.sh signup # Enable or disable users' ability to create a new account from the login page.

sudo ./ubuntu-start.sh host auth # Change the host/IP address used to access Link-Live Private and superuser credentials.

sudo ./toolkit/backup.sh -y -o /home/myuser/ll-backups # Back up to the specified directory.

RHEL Examples:

./rhel-start.sh # Run full configuration prompt (required for first install).

./rhel-start.sh signup # Enable or disable users' ability to create a new account from the login page.

./rhel-start.sh host auth # Change the host/IP address used to access Link-Live Private and superuser credentials.

./toolkit/backup.sh -y -o /home/myuser/ll-backups # Back up to the specified directory.

Required Ports

Link-Live Private serves on port 443, with NGINX handling SSL certificates.

NOTE: Port 80 is not used. There is no HTTP listener and no redirect to HTTPS, so browse to https:// explicitly. Take this into account when placing a reverse proxy or load balancer in front of the server.

By default, Link-Live Private creates an SMTP server container and sends out emails on port 25.

Other ports may be needed and configured by your company.

Automatic Port Configuration on RHEL

On RHEL, the start script makes two system changes so that rootless Podman can serve on port 443. Both persist across reboots, and your security team may want to know about them:

  • It writes /etc/sysctl.d/99-llp-ports.conf containing net.ipv4.ip_unprivileged_port_start=443, which permits an unprivileged process to bind port 443.

  • If firewalld is running, it opens 443/tcp permanently.

Storage and File System Requirements

Link-Live Private does not support installation or operation on NFS (Network File System) clients. The application and database must reside on local or directly attached storage.

Running Link-Live Private on NFS-mounted directories may result in performance issues or data corruption and is not supported.

Privilege Requirements

On Ubuntu, the start script and every script in the toolkit/ folder are run with sudo, from inside the installation directory. Docker requires root privileges to run.

On RHEL systems, scripts must NOT be run using sudo. Attempting to use sudo on RHEL will result in an error.

NOTE: The RHEL start script itself runs as a normal user, but it prompts for a sudo password when it configures the firewall, the unprivileged port range, and session lingering. If your account has no sudo rights, involve your system administrator for those three steps.

Running an Ubuntu script on a RHEL system, or a RHEL script on an Ubuntu system, will produce an error message indicating the incorrect operating system.