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.
- 01recondistribution, version and package manager (apt or dnf)
- 02reconRabbitMQ already installed? which version?
- 03reconservice active?
- 04reconAMQP 5672 / management 15672 ports already taken?
- 05reconexisting config (rabbitmq.conf) and architecture (Team RabbitMQ Erlang repo = amd64)
- 06actAdd the Team RabbitMQ repositoriesverify
- 07actInstall Erlang + RabbitMQverify
- 08actListen on localhost onlyverify
- 09actEnable managementverify
- 10actEnable and restart the serviceverify
- 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.
- 01verifyAdd the Team RabbitMQ repositoriesVerified by
ls /etc/apt/sources.list.d/rabbitmq.list /etc/yum.repos.d/rabbitmq.repo 2>/dev/null | head -1 - 02verifyInstall Erlang + RabbitMQVerified by
rabbitmqctl version - 03verifyListen on localhost onlyVerified by
grep -c -E '127.0.0.1' /etc/rabbitmq/rabbitmq.conf - 04verifyEnable managementVerified by
rabbitmq-plugins list -e | grep -c rabbitmq_management - 05verifyEnable and restart the serviceVerified by
systemctl is-active rabbitmq-server - 06verifyCreate an admin accountVerified by
curl -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.
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.
SEC.06
More database recipes
- 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
- 02MySQLMySQL Server, secured, bound to localhost, started and verified.
- 03MariaDBMariaDB, secured, bound to localhost, started and verified.
- 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
- 05MemcachedMemcached in-memory cache, bound to localhost.
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.