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)
- 02reconDocker Engine + compose plugin present and running? (otherwise, docker step)
- 03reconserver already deployed (container, volume, /opt/bedrock)? healthy → verify and skip; never reset a world or a save
- 04reconport 19132/tcp and range 19140-19159/udp free?
- 05reconRAM ≥ 1 GB free
- 06reconactive firewall (ufw or firewalld)? a port is only opened if one is active
- 07actInstall Docker Engine + Compose (only if missing)verify
- 08actCreate the dedicated bedrock user and its foldersverify
- 09actStart the Bedrock serververify
- 10actOpen 19132/tcp + 19140-19159/udp (only if a firewall is active)verify
- 11actThe server is readyverify
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 Docker Engine + Compose (only if missing)Verified by
systemctl is-active docker && docker compose version - 02verifyCreate the dedicated bedrock user and its foldersVerified by
id -u bedrock && stat -c '%U' /opt/bedrock - 03verifyStart the Bedrock serverVerified by
docker inspect -f '{{.State.Status}}' bedrock - 04verifyOpen 19132/tcp + 19140-19159/udp (only if a firewall is active)Verified by
ufw status 2>/dev/null | grep -cE '19132|19140:19159'; firewall-cmd --list-ports 2>/dev/null; true - 05verifyThe server is readyVerified by
timeout 270 bash -c 'until docker logs bedrock 2>&1 | grep -q "Server started"; do sleep 10; done' && echo ready
SEC.03
Guardrails
Non-negotiable instructions the run must respect, whatever it finds on the server.
Minecraft EULA accepted by the user by launching the recipe. Never reset an existing world (/opt/bedrock/worlds). The container runs as the bedrock user, not root. Open 19132/tcp and the whole published UDP range, only if a firewall is active.
SEC.04
Variables
What you choose before launching — the recipe fills in the rest.
| Name | Meaning |
|---|---|
| ${server_name} | Server name |
| ${max_players} | Max players |
| ${gamemode} | Game mode |
SEC.05
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.06
Deploy on Servor button
Maintain Minecraft Bedrock 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.
Dark background
Light background[](https://servor.app/deploy/install-minecraft-bedrock)SEC.07
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.
- 04Mumble ServerMumble (murmur) voice server from the distro packages, generated SuperUser password, started and verified.
- 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.