This is a third-party deployment note, not official OpenMausBot documentation. It covers the guide’s Path B: a Linux VPS, a domain under your control, Docker Compose, and Caddy for HTTPS.
The useful distinction is between pulling a prepared image and building one with your own configuration. Both use Compose, but they do not produce the same result when ENGINES changes.
Keep the network layout intact
Start with Docker Engine and Compose V2. Point the domain’s A record at the VPS and allow inbound TCP 80 and 443. The hostname entered as DOMAIN must not include https:// .
The supplied deployment has an unusual but deliberate layout: Caddy uses network_mode: service:omb , sharing the application’s network namespace. Public port mappings therefore belong to omb , even though Caddy handles HTTPS.
Caddy forwards normal requests to the loopback application listener and /hooks/* to the separate webhook listener.…