Install RabbitMQ on your VPS
Infraa installs RabbitMQ on your VPS from the distro's default apt repository — 3.9 on Ubuntu 22.04, 3.10 on Debian 12, 3.12 on Ubuntu 24.04 — with the distro's matched Erlang runtime pulled in automatically, so there's no third-party repo or Erlang version juggling. Local apps can connect at amqp://guest:guest@localhost:5672 as soon as the one approval finishes.
- Versions
- RabbitMQ 3.9 on Ubuntu 22.04; 3.10 on Debian 12; 3.12 on Ubuntu 24.04 (distro packages)
- Works on
- Ubuntu 22.04, Ubuntu 24.04, and Debian 12
- Package source
- Distro apt repository
What does the RabbitMQ install do?
- Installs the rabbitmq-server package — plus the distro's matched Erlang runtime — via apt. No third-party repository or signing key.
- Enables and starts the rabbitmq-server systemd unit.
- Writes no configuration: you get the stock setup — AMQP on port 5672, the default / vhost, and the loopback-only guest user.
- Never overwrites a broker config you already have: users, vhosts, plugins, and TLS are added later through chat.
How do I install RabbitMQ with Infraa?
Connect your server
Run the Infraa install one-liner (curl install.infraa.sh | sh) on your VPS. The agent registers over an outbound connection in about 30 seconds — no inbound ports, no SSH keys to share.
Pick the service
Choose it from the one-click catalog in the dashboard, or just ask in chat. Infraa turns your request into a concrete, reviewable plan.
Review and approve
Read exactly what will run, then approve. The agent executes only the approved, cryptographically signed steps and streams progress live.
What happens after the install?
Infraa checks RabbitMQ every 60 seconds — the rabbitmq-server unit and port 5672. The stock config listens on all interfaces (AMQP on 5672, plus Erlang's epmd on 4369 and the inter-node port on 25672), so Infraa's standing recommendation is to restrict those ports with your provider's firewall or bind to localhost. Real users, vhosts, and the management UI are one chat message away.
RabbitMQ on Infraa — common questions
01Can remote apps connect to RabbitMQ right away?
Not with the default login — the built-in guest/guest user is refused from anywhere but localhost. Remote connections need a user you create (ask in chat to run rabbitmqctl add_user), and since the AMQP port listens on all interfaces, pair that with a firewall rule.
02Why the distro's RabbitMQ instead of the latest release?
The distro package pulls in its own matched Erlang runtime, so there's no third-party repo, signing key, or Erlang compatibility juggling. The versions trail upstream but are distro-supported and fine for a standard broker.
03Does the install include the management UI?
No — the install deliberately writes no broker configuration. Plugins like the management UI are enabled afterwards through chat, so an existing broker setup is never overwritten.
Connect a server in 30 seconds, then install RabbitMQ from the catalog or just ask in chat.
