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.

  1. 01recondistro, version and package manager (apt or dnf)
  2. 02reconMumble already installed? which binary (mumble-server or murmurd)?
  3. 03reconservice name and state (mumble-server on Debian/Ubuntu, murmur elsewhere)
  4. 04reconlocation of the existing config (do not overwrite it)
  5. 05reconport 64738 (tcp + udp) free?
  6. 06reconactive firewall (ufw or firewalld)? a port is only opened if one is active
  7. 07actInstall the Mumble serververify
  8. 08actSet the SuperUser password (/root/mumble-superuser.txt)verify
  9. 09actEnable and start the serviceverify
  10. 10actOpen 64738 (tcp + udp) (only if a firewall is active)verify
  11. 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.

  1. 01Install the Mumble serverVerified bycommand -v mumble-server || command -v murmurd
  2. 02Set the SuperUser password (/root/mumble-superuser.txt)Verified bystat -c '%a' /root/mumble-superuser.txt
  3. 03Enable and start the serviceVerified bysystemctl is-active mumble-server 2>/dev/null || systemctl is-active murmur
  4. 04Open 64738 (tcp + udp) (only if a firewall is active)Verified byufw status 2>/dev/null | grep -cE '64738|64738'; firewall-cmd --list-ports 2>/dev/null; true
  5. 05The server is listeningVerified byss -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.

recipe — fail2ban_setup150+ in catalogue
security4 steps · low risk · idempotentrun
reconsshd present? ufw active? existing jails?✓
actinstall fail2ban · write default jails✓
actenable service · restart sshd (safe)✓
verifytest ban 60s · jails active · sshd alive✓

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.

Deploy on ServorDark background
Deploy on ServorLight background
[![Deploy on Servor](https://servor.app/badges/deploy-on-servor.svg)](https://servor.app/deploy/install-mumble-server)

SEC.06

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.