A VPS at a hoster you choose

A small VPS has a public IPv4 address on the machine itself: no router, no port forwarding, and usually a much faster upload than a home line. It is also the way out when your home line is behind CGNAT.

What to rent

Any provider that gives you a Linux machine with a public IPv4 address works; Debian or Ubuntu with Docker is the tested path. One CPU core is enough to start for a small crew; the sizing table shows what screen shares and cameras need, and the upload column matters most. Pick a provider in your country, one you trust, at a price that fits. Nothing ties you to it: moving later is a backup and a restore.

1. Docker

Install Docker Engine with the Compose plugin from docs.docker.com/engine/install.

2. Make the files and start

mkdir mnema-talk && cd mnema-talkdocker run --rm -it --user "$(id -u):$(id -g)" \
  -v "$PWD:/out" ghcr.io/mnema-xyz/mnema-talk setupdocker compose up -d --wait

3. Caddy for HTTPS

Point the A record of chat.example.com at the VPS's address, install Caddy and use the two-line Caddyfile from Domain, DNS and TLS. Caddy gets and renews the certificate by itself.

4. Two firewalls

The machine's own:

sudo ufw allow 80,443/tcp && sudo ufw allow 50000:50050/udp && sudo ufw allow 3479

3479 without a protocol opens UDP and TCP. Docker publishes ports around ufw on some setups; if a port stays closed anyway, check sudo iptables -L DOCKER-USER. The provider's firewall (security group) is a second, separate one with the same ports.

On a VPS the public address is on the machine itself, so voice needs no forwarding and no WEBRTC_NAT_1TO1_IP.

5. Check

Run the layer-by-layer check, then set up backups and copy them off the VPS.

Something wrong on this page? Tell us.