Skip to content
Callaba
PricingSign inDeploy Callaba on AWS

Install Callaba 8.8.4 on Ubuntu

By Founder of CallabaUpdated
On this page

Self-hosted installation · 8.8.4

Install Callaba 8.8.4 on your Ubuntu server, open the dashboard, and activate your licence. Choose the CPU or NVIDIA instructions below. If Callaba is already installed, go to the update steps.

Short answer: on Ubuntu 22.04 or 26.04 x86_64, clone the 8.8.4 installer repository, run the CPU or NVIDIA command that matches the host, sign in at the server address, change the default password, then activate the self-hosted licence in account settings. The installer installs missing Docker and Docker Compose components and enables Avahi.

Before you install

Supported host

Ubuntu 22.04 or 26.04 on an x86_64 server, with internet access to fetch files and images.

Access and credentials

Have the Callaba registry login and password ready. They are distinct from the dashboard account you use after installation and from the self-hosted licence activation.

Processing choice

Choose CPU, or NVIDIA only when the host already has a compatible GPU, driver, and NVIDIA container runtime.

Plan the host and network

Size CPU, memory, storage, DNS, TLS, and firewall policy for the intended workflow. Confirm the required network rules with the team operating the host.

Install Callaba 8.8.4

  1. Download the installer files. Run these commands on the target host, then stay in the resulting directory.
    Install steps 
    git clone https://gitlab.callabacloud.com/callaba-8/8.8.4.git
cd 8.8.4
  2. Run one installation command. Enter the registry credentials when prompted and confirm the installation.

    CPU host

    Use this for CPU processing.

    Command 
    sudo bash install.sh 8.8.4

    Prepared NVIDIA host

    Requires compatible hardware, host driver, and NVIDIA container runtime.

    Command 
    sudo bash install.sh 8.8.4 nvidia
  3. Wait for readiness, then open the dashboard. Browse to http://<server-ip>. Use http://127.0.0.1 only from a browser running on that server. A remote workstation needs the server’s reachable address.

First login, password, and licence

A fresh dashboard uses admin and password. Sign in, change that default password before exposing the server to other users, and activate the self-hosted licence from account settings. Registry credentials authenticate image access during installation; they are not the dashboard’s initial login and they do not replace licence activation.

First check: confirm the dashboard sign-in, then validate one live workflow with its actual sender and receiver.

Configure a domain and HTTPS when the host is ready

Use Configure Domain/SSL in Server settings when you are ready to configure HTTPS. The 8.8.4 wizard supports a Callaba domain with managed DNS and SSL, your own domain with automatic SSL, or your own uploaded certificate. For your own domain, point its DNS records at the server before issuing the certificate.

Choose the provider and follow the wizard’s readiness checks before switching the browser to HTTPS. To reuse a managed Callaba domain on a replacement server, use the separate, confirmed Reset SSL/Domain action on the old server first; it releases that managed name without deleting media modules. For a domain you own, DNS remains an external task: update its records with your DNS provider for the server you intend to use.

Update an existing installation

Back up the current configuration and important media first. A supported update preserves persistent Callaba volumes—including configuration, uploaded media, recordings, and certificates—but it restarts services and interrupts active sessions. Schedule a maintenance window.

Move an earlier 8.8 installation to 8.8.4

Use the current 8.8.4 installer files for a version-changing update. If you do not already have that checkout, clone it on the host; then run the update from the 8.8.4 directory. The updater detects the installed processing mode when no mode is supplied.

Install steps 
git clone https://gitlab.callabacloud.com/callaba-8/8.8.4.git
cd 8.8.4
sudo bash update.sh 8.8.4

This is the supported version-change path, not a rollback procedure. Keep the backup and maintenance window in place until readiness checks and a representative workflow test succeed.

Refresh an existing 8.8.4 installation

  1. Refresh the existing 8.8.4 checkout. Use the current checked-out installation files and keep the installation metadata and local configuration in place.
  2. Run the normal update. The updater reads the saved processor mode.
    Command 
    sudo bash update.sh 8.8.4
  3. Choose a mode explicitly only when needed.

    CPU update

    Command 
    sudo bash update.sh 8.8.4 cpu

    NVIDIA update

    Command 
    sudo bash update.sh 8.8.4 nvidia
Preserve the update context. Keep STACK_VERSION.txt and PROCESSOR_TYPE.txt in the installation directory so the updater can identify the installed release and processing mode. The same update command applies a newly published 8.8.4 patch.

Verify the result and recover access

Let the updater complete its readiness checks, then sign in and confirm the dashboard is reachable through the intended address. Run a representative workflow test with its actual sender and receiver before relying on it for a live event.

If you lose the dashboard password, reset it from the installation directory:

Command 
sudo bash reset-password.sh

The script asks for confirmation and resets the admin password to password. Sign in with that default only to change it again before exposing the server to other users.

For help with a configured system, use Ask AI in the dashboard or open Show logs from an SRT server’s settings to inspect its connection events.

Uninstall Callaba (destructive)

Do not use removal as an update step. After confirmation, this script removes containers and data volumes matching Callaba, LiveKit, ingress, or egress names, removes Callaba registry images, and prunes unused Docker networks. It also removes the installer’s internal-port firewall rules.

Command 
sudo bash remove.sh

On a shared Docker host, check the name matches and network-pruning scope first: unrelated workloads with matching names may be affected. Back up any data you need before removal. Do not substitute broad Docker cleanup commands: they can affect containers, volumes, images, or networks outside this Callaba installation.

Next steps

With the server available and the initial account secured, choose one real workflow to validate end to end. For SRT contribution and server operations, start with the SRT Server guide; check the sender and receiver as well as the Callaba dashboard. For the release overview, read what is new in Callaba 8.8.4.

Source: official Callaba 8.8.4 installer repository.

Continue with your self-hosted account

Use the account path to activate or review the licence needed for the modules your team plans to run, then return to this guide whenever you update the host.

Open your subscriptions →

Put the workflow to work

Run this workflow in Callaba

Deploy on AWS, then verify the same path with your own source and destination.

Deploy Callaba on AWSReview the deployment guide