Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
AO
Self-host Apache OpenMeetings
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
Apache's browser-based web conferencing server: rooms with audio and video, a shared whiteboard, chat, screen sharing, file import and recording, plus calendar, user and group management and a SOAP/REST API for embedding it in other systems. It is a Java web application on Tomcat that streams media through a Kurento media server, and it can sign users in through LDAP/ADS or OAuth2 and connect phone callers over SIP (Asterisk). The project's Docker image comes in a full build that bundles MySQL and Kurento and a min build that expects you to supply both.
Pick Apache OpenMeetings when you want a conferencing server with a classroom or webinar feel: rooms with a shared whiteboard, chat, screen sharing, document import, recording, a calendar, user and group management and a SOAP/REST API for embedding. It is a Java web application on Tomcat, licensed Apache-2.0, that streams media through a Kurento media server and can sign users in through LDAP/ADS or OAuth2 and connect phone callers over SIP (Asterisk). Our snippet runs the project's `apache/openmeetings` image, pinned to 9.1.1 (pushed to Docker Hub on 2026-08-13; the application inside reports version 9.1.0). That is the "full" build, which bundles MySQL and the Kurento media server in one container and has the administrator account created at image build time; the `min-9.1.1` tag leaves the database and Kurento to you. The docs name Java 21 and Kurento 7.3 or newer as requirements. The installation guide asks for at least 4 GB of RAM (8 GB recommended), which is our floor; one run of the full image used about 1.1 GB just after start. In the catalog, Jitsi Meet needs a domain, ports 80 and 443 and a separate Videobridge but gives you a plain meeting link, and MiroTalk P2P is a single light Node.js container with no accounts; OpenMeetings is heavier, keeps its own users and rooms, and is the one built around moderated sessions with whiteboard and documents.
What you need
Any VPS with at least 4096 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
About an afternoon — budget time for troubleshooting
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# Apache OpenMeetings — video conferencing — based on the project's documented `apache/openmeetings` Docker image (the all-in-one "full" build), pinned to 9.1.1 (pushed 2026-08-13)cat > docker-compose.yml <<'EOF'services: openmeetings: image: apache/openmeetings:9.1.1 restart: unless-stopped network_mode: host volumes: - om_db:/var/lib/mysql - om_data:/opt/openmeetings/webapps/openmeetings/datavolumes: om_db: om_data:EOFdocker compose up -dtimeout 600 bash -c 'until curl -fskL -o /dev/null https://localhost:5443/openmeetings/; do sleep 5; done'# → https://SERVER_IP:5443/openmeetings (bundled self-signed certificate; host networking as in the image README, so firewall 5443 until the password is changed; the image ships an administrator account, om_admin with the password set in the image's OM_PASS variable — change it at first login; camera and microphone need a trusted HTTPS certificate)
OpenMeetings's installation and HTTPS documentation, and the image it publishes, flag these before you rely on it:
non-negotiableThe full image ships a ready administrator account whose name and password are set in the image's own environment (OM_USER=om_admin, OM_PASS is a fixed value printed in the image configuration). Anyone who can read the public image knows it, so sign in straight after the first start and change it, and do not publish the port before you have.
non-negotiableCamera and microphone access needs a trusted HTTPS certificate. The server answers on port 5443 with the bundled self-signed certificate (conf/localhost.jks), which browsers reject for other machines, and the media-server documentation says only a local installation works without a valid certificate. Put a proxy with a real certificate in front, or replace conf/localhost.jks with your own keystore and point server.xml at it (the HTTPS guide's steps use the file name conf/keystore).
non-negotiableMedia needs a TURN server outside a local network. The docs say only a local installation works without one, and the image has TURN_URL, TURN_USER and TURN_PASS variables for it. Our snippet sets no TURN server and follows the image README's --network host run for the full image so that Kurento's media ports are reachable; with host networking the container publishes everything it listens on, so firewall all but the ports you need. Expect audio and video to fail for remote participants until you add a TURN server and a trusted certificate.
non-negotiableThe full image keeps its MySQL data and uploaded files inside the container. Our snippet mounts named volumes (not bind mounts, which would hide the database baked into the image) on /var/lib/mysql and /opt/openmeetings/webapps/openmeetings/data; without them, recreating the container loses rooms and users. The alternative is the min image, whose documented data mount is /opt/omdata, with an external database. The images are only offered as convenience binaries on the Docker Hub page.
non-negotiableAllow time and memory on first start: the Tomcat application took about half a minute to deploy in our test, after MySQL and Kurento start in the same container, and the documented requirement is a Java 21 runtime. The image already includes ImageMagick, Ghostscript, LibreOffice and ffmpeg for document import and recording; on a bare-metal install the docs list them as separate installs.
Apache OpenMeetings used 950 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 4096 MB.
Is the Apache OpenMeetings install snippet verified?
The Apache OpenMeetings install snippet is marked verified on Ubuntu 26.04 (Nov 2026).