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. 01recondistribution, version and package manager (apt or dnf)
  2. 02reconRabbitMQ already installed? which version?
  3. 03reconservice active?
  4. 04reconAMQP 5672 / management 15672 ports already taken?
  5. 05reconexisting config (rabbitmq.conf) and architecture (Team RabbitMQ Erlang repo = amd64)
  6. 06actAdd the Team RabbitMQ repositoriesverify
  7. 07actInstall Erlang + RabbitMQverify
  8. 08actListen on localhost onlyverify
  9. 09actEnable managementverify
  10. 10actEnable and restart the serviceverify
  11. 11actCreate an admin accountverify

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. 01Add the Team RabbitMQ repositoriesVerified byls /etc/apt/sources.list.d/rabbitmq.list /etc/yum.repos.d/rabbitmq.repo 2>/dev/null | head -1
  2. 02Install Erlang + RabbitMQVerified byrabbitmqctl version
  3. 03Listen on localhost onlyVerified bygrep -c -E '127.0.0.1' /etc/rabbitmq/rabbitmq.conf
  4. 04Enable managementVerified byrabbitmq-plugins list -e | grep -c rabbitmq_management
  5. 05Enable and restart the serviceVerified bysystemctl is-active rabbitmq-server
  6. 06Create an admin accountVerified bycurl -s -o /dev/null -w '%{http_code}' -u "admin:$(cat /root/rabbitmq-admin.password)" http://127.0.0.1:15672/api/overview

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

If RabbitMQ is already installed, do not reinstall and do not touch existing accounts. Only delete guest on a fresh install. Expose neither 5672 nor 15672 on 0.0.0.0. The admin password stays in /root/rabbitmq-admin.password.

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 RabbitMQ 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-rabbitmq)

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.