Operating System CentOS

How to Install Apache OpenMeetings 9 on AlmaLinux 9 and Rocky Linux 9

Install Apache OpenMeetings 9.1 on AlmaLinux 9 or Rocky Linux 9 with Java 21, PostgreSQL 16, Kurento Media Server and the converters for uploads and recordings.

This guide installs Apache OpenMeetings 9.1 on AlmaLinux 9 or Rocky Linux 9 (the same steps apply to RHEL 9 and CentOS Stream 9). At the end you have the OpenMeetings web application running as a systemd service on port 5443, a PostgreSQL database behind it, Kurento Media Server handling WebRTC audio and video, and the converters needed for whiteboard uploads and recordings.

CentOS 7 reached end of life on 30 June 2024, and current OpenMeetings releases need Java 21, which that system never shipped. OpenMeetings has also changed architecture since the Flash era: media now goes through a separate Kurento Media Server (KMS), and release 9.1.0 requires KMS 7.3.0 or newer.

Requirements

  • AlmaLinux 9 or Rocky Linux 9, x86_64, with at least 4 GB of RAM; the project recommends 8 GB and two to four cores when document conversion and recording are used.
  • A user with sudo rights (the examples use deploy).
  • A DNS name pointing at the server, here meet.example.com on 203.0.113.10. Browsers only allow camera and microphone access over HTTPS, and anything beyond a local test needs a valid certificate.

Step 1: Install Java and the converter tools

OpenMeetings uses ImageMagick for image uploads, Ghostscript for PDF import, LibreOffice for office documents, and FFmpeg and SoX for recordings. ImageMagick and SoX come from EPEL; FFmpeg comes from RPM Fusion, which needs EPEL and the CRB repository.

sudo dnf upgrade -y
sudo dnf install -y epel-release dnf-plugins-core
sudo dnf config-manager --set-enabled crb
sudo dnf install -y --nogpgcheck https://mirrors.rpmfusion.org/free/el/rpmfusion-free-release-$(rpm -E %rhel).noarch.rpm
sudo dnf install -y java-21-openjdk-headless ImageMagick ghostscript sox ffmpeg \
  libreoffice-writer libreoffice-calc libreoffice-impress tar curl

Confirm the Java version. OpenMeetings 9 does not start on Java 17 or older.

java -version

Step 2: Create the PostgreSQL database

OpenMeetings ships with an embedded H2 database, which the project does not recommend for production. Use PostgreSQL 16 from the AppStream module instead:

sudo dnf module enable -y postgresql:16
sudo dnf install -y postgresql-server
sudo postgresql-setup --initdb
sudo systemctl enable --now postgresql

Create a role and a UTF-8 database. The first command asks for the new role's password twice.

sudo -u postgres createuser -P openmeetings
sudo -u postgres createdb -O openmeetings -E UTF8 openmeetings

The OpenMeetings documentation asks for standard_conforming_strings to be on (the PostgreSQL default) and escape_string_warning to be off:

sudo -u postgres psql -c "ALTER SYSTEM SET escape_string_warning = off;"

On this distribution family, pg_hba.conf uses ident for local TCP connections, which rejects password logins from a Java application. Switch the two loopback lines to password authentication and restart:

sudo sed -i -E 's/^(host\s+all\s+all\s+(127\.0\.0\.1\/32|::1\/128)\s+)ident/\1scram-sha-256/' /var/lib/pgsql/data/pg_hba.conf
sudo systemctl restart postgresql

Step 3: Run Kurento Media Server

Every OpenMeetings instance needs its own Kurento Media Server on the same host. Kurento only publishes native packages for Ubuntu, so on the RHEL family the supported route is its Docker image. Install Docker Engine from Docker's CentOS repository, which is also what AlmaLinux and Rocky Linux use:

sudo dnf config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
sudo dnf install -y docker-ce docker-ce-cli containerd.io
sudo systemctl enable --now docker

Create the OpenMeetings account and directories first, because KMS writes recordings into the OpenMeetings data directory and must see it under the same path:

sudo useradd --system --home-dir /opt/openmeetings --shell /sbin/nologin openmeetings
sudo mkdir -p /opt/openmeetings/data

Start KMS with host networking, as the Kurento documentation recommends for media servers, and limit the UDP ports it uses for media so you can open exactly that range in the firewall:

sudo docker run -d --name kurento --restart unless-stopped --network host \
  -e KMS_MIN_PORT=40000 -e KMS_MAX_PORT=40999 \
  -v /opt/openmeetings/data:/opt/openmeetings/data \
  kurento/kurento-media-server:7.3.0

KMS now listens for its control WebSocket on port 8888. OpenMeetings connects to ws://127.0.0.1:8888/kurento by default, so no further configuration is needed. Do not open port 8888 in the firewall.

Step 4: Download and unpack OpenMeetings

Download the release and its checksum from the Apache download servers and verify the archive before unpacking it:

cd /tmp
curl -fLO https://dlcdn.apache.org/openmeetings/9.1.0/bin/apache-openmeetings-9.1.0.tar.gz
curl -fLO https://downloads.apache.org/openmeetings/9.1.0/bin/apache-openmeetings-9.1.0.tar.gz.sha512
sha512sum -c apache-openmeetings-9.1.0.tar.gz.sha512

The command must print OK. If a newer release has replaced 9.1.0, take the file name from the project's downloads page. Unpack into /opt/openmeetings and hand the tree to the service account:

sudo tar -xzf apache-openmeetings-9.1.0.tar.gz -C /opt/openmeetings --strip-components=1
sudo chown -R openmeetings:openmeetings /opt/openmeetings
sudo restorecon -R /opt/openmeetings

Step 5: Create a systemd service

OpenMeetings is delivered inside an Apache Tomcat tree and is started with bin/startup.sh. Create /etc/systemd/system/openmeetings.service:

[Unit]
Description=Apache OpenMeetings
After=network-online.target postgresql.service docker.service
Wants=network-online.target

[Service]
Type=forking
User=openmeetings
Group=openmeetings
Environment=CATALINA_PID=/opt/openmeetings/temp/openmeetings.pid
PIDFile=/opt/openmeetings/temp/openmeetings.pid
ExecStart=/opt/openmeetings/bin/startup.sh
ExecStop=/opt/openmeetings/bin/shutdown.sh
SuccessExitStatus=143
Restart=on-failure

[Install]
WantedBy=multi-user.target
sudo systemctl daemon-reload
sudo systemctl enable --now openmeetings

The first start takes a minute or two. Follow the application log until the server is up:

sudo tail -f /opt/openmeetings/logs/openmeetings.log

Step 6: Open the firewall

Open the HTTPS port of the web interface and the UDP media range you gave Kurento:

sudo firewall-cmd --permanent --add-port=5443/tcp
sudo firewall-cmd --permanent --add-port=40000-40999/udp
sudo firewall-cmd --reload

Port 5080 serves the same application over plain HTTP. Leave it closed unless a TLS-terminating reverse proxy on the same machine needs it.

Step 7: Run the web installer

Browse to https://meet.example.com:5443/openmeetings/install. The server uses a self-signed certificate out of the box, so accept the browser warning for now. In the installer:

  1. Choose PostgreSQL as the database type and enter host localhost, database openmeetings, user openmeetings and the password from step 2.
  2. Create the first administrator account, its e-mail address, the default group and the time zone.
  3. Enter your SMTP server so invitations and password resets can be sent.
  4. Leave the converter paths empty when the tools are on the system PATH, which is the case for the packages from step 1.

When the installer finishes, sign in at https://meet.example.com:5443/openmeetings, enter a room and test the camera, microphone and a short recording. The same installation can be done without a browser using admin.sh in /opt/openmeetings; its options are listed in the project's Command Line Admin page.

Step 8: Certificate and TURN server

Replace the self-signed certificate before inviting users. OpenMeetings reads its certificate from the PKCS12 keystore /opt/openmeetings/conf/keystore: rename the existing file, convert your certificate, key and CA chain with openssl pkcs12 -export, import the result with keytool -importkeystore under the alias openmeetings, and restart the service. The exact commands are in the project's HTTPS guide.

Participants behind NAT or restrictive firewalls also need a TURN server such as coturn. Once you have one, set kurento.turn.url, kurento.turn.user and kurento.turn.secret in /opt/openmeetings/webapps/openmeetings/WEB-INF/classes/openmeetings.properties and restart OpenMeetings. In the same file, replace the default kurento.kuid value with a UUID of your own.

Maintenance and troubleshooting

  • Logs: the application writes to /opt/openmeetings/logs/openmeetings.log; failed document conversions are explained there. Kurento's output is in sudo docker logs kurento.
  • Rooms open but there is no audio or video: check that the kurento container is running, that the UDP range is open in every firewall in front of the server, and that a TURN server is configured for remote users.
  • Recordings are empty or missing: KMS and OpenMeetings must both be able to read and write /opt/openmeetings/data. Check the ownership of the files that appear there after a test recording.
  • Backups: admin.sh -b writes a backup archive that includes uploaded files, and admin.sh -r restores it. Take one before every upgrade.
  • Upgrading: OpenMeetings upgrades are a backup, a fresh unpack of the new release and a restore. To update Kurento, pull the new image tag, remove the container and run the command from step 3 with the new tag.

Frequently asked questions

Can I use MariaDB or MySQL instead of PostgreSQL?

Yes. OpenMeetings supports both, but you have to download the MySQL JDBC driver yourself and place it in webapps/openmeetings/WEB-INF/lib before running the installer, and the server character set must be UTF-8.

Is there an official Docker image for OpenMeetings itself?

The project publishes apache/openmeetings images. The full image bundles a database and Kurento for quick trials, and a min- variant expects an external database and KMS. Both use documented default passwords, so treat the full image as a demo rather than a production setup.

Why does OpenMeetings need Kurento at all?

The web application handles rooms, users, the whiteboard and files. Real-time audio, video, screen sharing and recording are WebRTC streams, and those are terminated and mixed by the media server.

Can I move the web interface to port 443?

The ports are defined in /opt/openmeetings/conf/server.xml. Because the service runs as an unprivileged user, the simpler approach is a reverse proxy on port 443 that forwards to OpenMeetings, including WebSocket upgrades.

Share story:

Continue reading other guides on How VPS.