Host an MKWMP server
Back to MKWMP
A Vultr VM and one command. About US$5 a month runs a server for dozens of players. You need a Vultr account, an SSH key, and a few minutes.
You log in to the VM with a key, not a password. If you don't have one, create it on your own computer (PowerShell on Windows, a terminal on macOS or Linux) and press Enter at each question:
Your public key is now in ~/.ssh/id_ed25519.pub (on Windows, C:\Users\<you>\.ssh\id_ed25519.pub). Add it at Vultr: Account → SSH Keys → Add SSH Key. Never share id_ed25519 without .pub: that's the private half.
Pick a region close to most of your players: the relay and the voice and camera relay run on this VM. When it's running, note its public IPv4 address.
| Where | Deploy → Cloud Compute, Shared CPU (Regular) |
|---|---|
| Size | 1 vCPU, 1 GB RAM, about US$5 a month |
| Image | Ubuntu 24.04 LTS x64 |
| Login | your SSH key |
Vultr filters traffic before it reaches the VM. Create a firewall group with these inbound rules and attach it to the VM. The script opens the same ports inside the VM (ufw), so the two layers agree. Leave outbound traffic open.
| Protocol | Ports | From | What it carries |
|---|---|---|---|
| TCP | 22 | your IP (or anywhere) | SSH |
| TCP | 7000 | anywhere | the seat API: the launcher signs in and takes a seat (80 and 443 instead with a domain) |
| TCP | 8905 | anywhere | the game's online services (TLS) |
| TCP | 8906 | anywhere | Gamesync, the game's match data |
| UDP | 3478 | anywhere | the TURN relay, for players who can't reach each other directly |
| UDP | 49152–49407 | anywhere | the TURN relay's sockets |
| UDP | 8907 | anywhere | voice chat and camera relay (friend rooms) |
| UDP | 10025 | anywhere | the NAT check |
In Vultr: Network → Firewall → Add Firewall Group, add the rules, then add your VM on the group's Linked Instances tab.
Log in and run it as root:
ssh root@<IPv4> curl -fsSL https://anarqz.github.io/mkwmp/deploy-mkwmp-server.sh | sudo bash
It asks for the server's name and region, then:
downloads the server from the latest MKWMP release and checks it against the release's signed checksums, with the MKWMP release key built into the script (it stops if anything doesn't match);
creates the
mkwmpuser and/var/lib/mkwmp: keys, the gamertag database, the config and your privacy policy;installs two services,
mkwmp-seatfor launchers andmkwmp-lobbyfor the game, and keeps their logs for 7 days;opens the ports in ufw, keeping SSH open;
lists the server in the server directory, so it shows up in everyone's launcher;
checks that it answers from outside and that the directory lists it, then prints the address players use.
Without questions:
curl -fsSL https://anarqz.github.io/mkwmp/deploy-mkwmp-server.sh | sudo bash -s -- \ --name "Friday kart" --region eu-west --capacity 24 --yes
--name | the name in the launcher and the server list: up to 32 letters, digits, spaces and _ . - |
--region | a short tag for the server list, like sa-east, us-east or eu-west |
--capacity | players seated at once (50 by default); the rest wait in a queue |
--public-ip | the address players reach the VM at, if it isn't the VM's own |
--domain | HTTPS with Caddy (step 5) |
--privacy-file | your own privacy policy (Markdown) |
--no-announce | stay out of the public server list; players type your address |
--version | a given release, like v1.4.0 |
--no-firewall | leave ufw alone |
--uninstall | remove the services, the program and the ufw rules; keeps /var/lib/mkwmp (add --purge to delete it too) |
Your privacy policy
Players see /var/lib/mkwmp/privacy.md in the launcher and accept it. The script writes a template the first time: edit it so it's true for your server (who you are, how to reach you, how long you keep logs), then run systemctl restart mkwmp-seat. Every edit is a new version, and players are asked to accept it again.
Over plain http://, PINs travel unencrypted. With a domain:
Create a DNS A record, like
mkw.example.net, pointing at the VM's public IPv4. At Cloudflare, make it DNS only (grey cloud) at first, so the certificate can be issued.In the cloud firewall, open TCP 80 and 443 (you can close 7000).
Run the script again with
--domain mkw.example.net. It installs Caddy, which gets and renews a Let's Encrypt certificate, keeps the seat API on the VM only, and listshttps://mkw.example.netin the directory.
The game's own ports (8905, 8906 and the UDP ones) still go straight to the VM's IP address.
/var/lib/mkwmp is everything: registry.db (gamertags, PIN hashes, friends) and keys/ (your server's identity). Stop mkwmp-seat, archive the folder, start it again. Keep backups private and delete old ones: they hold your players' data.journalctl -u mkwmp-seat -u mkwmp-lobby -f, kept for 7 days.sudo -u mkwmp /opt/mkwmp/bin/server admin list --config /var/lib/mkwmp/server.toml, and the other admin commands in the hosting guide.| Symptom | Check |
|---|---|
| The script stops at "signature does NOT verify" | The download was altered or cut short. Run it again; don't install by hand. |
| "/ping did not answer from this VM" | The cloud firewall isn't attached or lacks TCP 7000 (or 80 and 443 with a domain). With --domain, the A record may not point at the VM yet. |
| Not listed in the directory | journalctl -u mkwmp-seat | grep announce. "HTTP 400 … endpoint" means a private address (use --public-ip); "connect" means outbound HTTPS is blocked. |
| Launchers connect, but the game can't | TCP 8905 and 8906 closed in the cloud firewall; systemctl status mkwmp-lobby. |
| Players can't race or talk together | The UDP ports (3478, 49152–49407, 8907, 10025) closed in the cloud firewall. |
For friends or a LAN party, download the server zip from the latest release and run server.exe (Windows) or ./server (Linux). The first run asks for the address players reach your PC at, creates mkwmp-data next to it, and runs until you close it. Over the internet, forward the ports above on your router. Players set the launcher's server to http://<that address>:7000.
Docker, a by-hand systemd setup and every option: the full hosting guide on GitHub.