Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / RabbitMQ on Ubuntu 24.04 LTS

RabbitMQ on Ubuntu 24.04 LTS — Support & Quick Start

RabbitMQ 4.3 message broker with management UI on Ubuntu 24.04 LTS and a unique per-VM admin password.

Email support Product page Azure Marketplace listing

At a glance

Application ports5672 (AMQP), 15672 (management UI)
Open in browserhttp://<VM-IP>:15672/
Admin credential filesudo cat /opt/rabbitmq/admin-password
Sign in asdcaadmin-<random> (RABBITMQ_ADMIN_USER in the credential file — not `admin` or `guest`)
Service(s)rabbitmq-server
Configuration/etc/rabbitmq/rabbitmq.conf; /etc/rabbitmq/enabled_plugins
Logs/var/log/rabbitmq/; journalctl -u rabbitmq-server -f
VersionRabbitMQ 4.3.6 (Erlang/OTP 27.3.4.18)
PlatformUbuntu 24.04 LTS

Quick start

  1. Deploy from the Azure Marketplace (Get It Now → Create), choosing your SSH key at the Administration step.
  2. Allow inbound SSH (22) for yourself plus the application port(s): 15672 (management UI) to your IP; 5672 (AMQP) to your application subnets — restrict to your own IP where possible. The in-image firewall already allows them; only the Network Security Group (NSG) keeps them closed.
  3. Open the management UI at http://<VM-IP>:15672/ and sign in with the generated user (see First login below).
  4. Create your vhosts, users, and queues; point AMQP clients at port 5672 over your VNet. RabbitMQ 4.3 refuses the `x-queue-mode` argument and `x-queue-version: 1`, denies global QoS and transient non-exclusive queues by default, and Node.js clients need amqplib 0.10.7 or later. Check the running RabbitMQ version with `sudo rabbitmq-diagnostics server_version`.

First login / credentials

This image generates its admin credential on the VM at first boot — nothing is pre-set. SSH into the VM with the username + key you chose at deploy, then print the generated credential:

ssh <your-username>@<VM-IP>
sudo cat /opt/rabbitmq/admin-password

Sign in as dcaadmin-<random> (RABBITMQ_ADMIN_USER in the credential file — not `admin` or `guest`).

  1. Print the credential file: RABBITMQ_ADMIN_USER (per-VM administrator name) and RABBITMQ_ADMIN_PASSWORD.
  2. Open http://<VM-IP>:15672/ and sign in with that username and password.
  3. Create vhosts and least-privilege users for applications (Admin → Users), change the admin password, and delete the file.

The management user is per-VM (dcaadmin-xxxxxxxx), not `admin`; both lines are in the file.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.