SEC.01
The playbook
The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.
- 01recondistro, version and package manager (apt or dnf)
- 02reconMumble already installed? which binary (mumble-server or murmurd)?
- 03reconservice name and state (mumble-server on Debian/Ubuntu, murmur elsewhere)
- 04reconlocation of the existing config (do not overwrite it)
- 05reconport 64738 (tcp + udp) free?
- 06reconactive firewall (ufw or firewalld)? a port is only opened if one is active
- 07actInstall the Mumble serververify
- 08actSet the SuperUser password (/root/mumble-superuser.txt)verify
- 09actEnable and start the serviceverify
- 10actOpen 64738 (tcp + udp) (only if a firewall is active)verify
- 11actThe server is listeningverify
SEC.02
What it verifies
Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.
- 01verifyInstall the Mumble serverVerified by
command -v mumble-server || command -v murmurd - 02verifySet the SuperUser password (/root/mumble-superuser.txt)Verified by
stat -c '%a' /root/mumble-superuser.txt - 03verifyEnable and start the serviceVerified by
systemctl is-active mumble-server 2>/dev/null || systemctl is-active murmur - 04verifyOpen 64738 (tcp + udp) (only if a firewall is active)Verified by
ufw status 2>/dev/null | grep -cE '64738|64738'; firewall-cmd --list-ports 2>/dev/null; true - 05verifyThe server is listeningVerified by
ss -tulnH "sport = :64738"
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
The SuperUser password stays in /root/mumble-superuser.txt (600), never in logs or output. Do not overwrite an existing config (back up before any change). The service runs as its dedicated user, not root. Only open 64738 tcp+udp, and only if a firewall is active.
SEC.04
How a recipe runs in Servor
Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.
search by intent — type “firewall”, get ufw
- 01Read-only reconnaissance before any change
- 02Every command signed by your browser, approved by you
- 03Each step verified before the run moves on, every run kept in the history
SEC.05
Deploy on Servor button
Maintain Mumble Server or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.
SEC.06
More game servers recipes
- 01Minecraft Server (Java)Minecraft Java server (Paper, Vanilla, Fabric or Forge) under a dedicated user, as a systemd service, with the right Java.
- 02Valheim ServerDedicated Valheim server via Docker, under a dedicated user, world and backups in /opt/valheim.
- 03Factorio ServerDedicated Factorio server (stable release) via Docker, non-root, saves in /opt/factorio.
- 04Minecraft Bedrock ServerDedicated Minecraft Bedrock server via Docker, under a dedicated user, world in /opt/bedrock.
- 05Terraria ServerDedicated Terraria (TShock) server via Docker, worlds in /opt/terraria.
Verified recipe
Run this recipe on your server
Connect a server, launch the recipe, and approve each step as Servor executes and verifies it. Free plan, no card required.