Self-host ejabberd with Levelrail
Robust, scalable XMPP chat and messaging server from ProcessOne. Runs with the default configuration and stores its database on a volume.
- Authorprocessone
- LicenceGPL-2.0-only
- Memory256 MiB
- Services1
How to self-host ejabberd
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/processone/ejabberd:26.09@sha256:ec5cf7bc85627fd9bde47309a34600d6c16895e9808807ec9ff57426f2508115
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on ports 5280, 5222.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Register users with the container command ejabberdctl register, then connect an XMPP client to port 5222. The web admin is on port 5280.
ejabberd requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 5280, 5222
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- GPL-2.0-only, copyleft license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then ejabberd. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the ejabberd docs page.
Deploy ejabberd your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy ejabberd from the CLI
levelrail-cli templates deploy ejabberd --name my-ejabberd Deploy ejabberd with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/ejabberd/deploy ejabberd configuration
ejabberd services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| ejabberd | ghcr.io/processone/ejabberd:26.09@sha256:ec5cf7bc85627fd9bde47309a34600d6c16895e9808807ec9ff57426f2508115 | 5280, 5222 | database -> /opt/ejabberd/database |
ejabberd environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 5280, 5222
- Volumes
- 1 named mount: database -> /opt/ejabberd/database
ejabberd FAQ
How much memory does ejabberd need?
The catalog lists about 256 MiB of memory for ejabberd.
Does ejabberd run on arm64?
For ejabberd, arm64 support is not confirmed; amd64 is unknown.
What licence is ejabberd under?
ejabberd is licensed under GPL-2.0-only, which is copyleft, so changes you distribute must be shared under the same terms.
Does ejabberd need configuration before it starts?
No. The template fills in its own defaults.
Which ports does ejabberd use?
ejabberd listens on ports 5280 and 5222 inside the stack.
Where does ejabberd keep its data?
In a named volume: database mounted at /opt/ejabberd/database.
Can I deploy ejabberd on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for ejabberd, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/processone/ejabberd:26.09@sha256:ec5cf7bc85627fd9bde47309a34600d6c16895e9808807ec9ff57426f2508115 is what you deploy there.