Installing and Configuring RabbitMQ

Software Installation — Step-by-Step

RabbitMQ installation consists of two main steps: first, installing Erlang (on which RabbitMQ is written), and then RabbitMQ itself. We will use official repositories for Ubuntu to ensure up-to-date versions and easy updates.

1. Adding Official Erlang and RabbitMQ Repositories

As of 2026, the most stable and up-to-date versions of Erlang and RabbitMQ for Ubuntu 24.04 LTS (Noble Numbat) can be obtained from official repositories. This ensures you receive the latest security patches and functional updates.

Adding Erlang Solutions Repository

RabbitMQ requires a specific version of Erlang/OTP. It is recommended to use packages from Erlang Solutions, as they are often more up-to-date than those available in standard Ubuntu repositories.

# Install necessary utilities for working with HTTPS repositories
sudo apt install -y curl gnupg apt-transport-https

# Add Erlang Solutions GPG key
curl -fsSL https://packages.erlang-solutions.com/ubuntu/erlang_solutions.asc | sudo gpg --dearmor -o /usr/share/keyrings/erlang-solutions.gpg

# Add Erlang Solutions repository for Ubuntu 24.04
echo "deb [signed-by=/usr/share/keyrings/erlang-solutions.gpg] https://packages.erlang-solutions.com/ubuntu noble contrib" | sudo tee /etc/apt/sources.list.d/erlang-solutions.list > /dev/null

# Update package list
sudo apt update

Adding RabbitMQ Repository

Similarly, let's add the official RabbitMQ repository.

# Add RabbitMQ GPG key
curl -fsSL https://www.rabbitmq.com/rabbitmq-release-signing-key.asc | sudo gpg --dearmor -o /usr/share/keyrings/rabbitmq.gpg

# Add RabbitMQ repository for Ubuntu 24.04
echo "deb [signed-by=/usr/share/keyrings/rabbitmq.gpg] https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu noble main" | sudo tee /etc/apt/sources.list.d/rabbitmq.list > /dev/null

# Update package list again
sudo apt update

2. Installing Erlang/OTP

Now that the repositories are added, you can install Erlang. Erlang/OTP version 26.0 (or newer, current as of 2026) is recommended for RabbitMQ 3.13.0+.

# Install Erlang/OTP
sudo apt install -y erlang-nox

Ensure Erlang is installed correctly and check its version:

erl -version
# The expected output will be similar to: Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version 14.0.5 (or similar for OTP 26.x)

3. Installing RabbitMQ Server

After installing Erlang, you can proceed with installing RabbitMQ.

# Install RabbitMQ Server
sudo apt install -y rabbitmq-server

After installation, the RabbitMQ server should start automatically. You can check its status with the following command:

sudo systemctl status rabbitmq-server

You should see the status

active (running)

4. Enabling RabbitMQ Management Plugin

The management plugin provides a convenient web interface for monitoring and administering RabbitMQ. This is very useful for visualizing queues, exchanges, connections, and users.

# Enable RabbitMQ management plugin
sudo rabbitmq-plugins enable rabbitmq_management

After enabling the plugin, the web interface will be available at

http://YOUR_VPS_IP_ADDRESS:15672/

5. Adding a User and Setting Permissions

By default, RabbitMQ creates a

guest

guest

localhost

# Create a new user (replace myuser and mypassword with your values)
sudo rabbitmqctl add_user myuser mypassword

# Grant administrator rights to the user for Management UI access
sudo rabbitmqctl set_user_tags myuser administrator

# Set permissions for the default virtual host "/"
# This grants the user myuser full access to the default virtual host
sudo rabbitmqctl set_permissions -p / myuser "." "." "."

http://YOUR_VPS_IP_ADDRESS:15672/

myuser

mypassword

netstat

ss

# Install net-tools if not already installed
sudo apt install -y net-tools

# Check RabbitMQ open ports
sudo netstat -tulnp | grep LISTEN | grep -E '5672|15672|25672|4369'

Backups and Maintenance

Regular backups and proper maintenance are critically important for ensuring the reliability and long-term stability of your RabbitMQ installation. Data loss or incorrect broker operation can lead to serious problems in your applications.

What to Back Up for RabbitMQ

In the context of RabbitMQ, "data" does not always mean the messages themselves in queues (many of them are temporary). The most important items for backup are:

1. RabbitMQ Definitions: These are metadata such as virtual hosts, users, their permissions, queues, exchanges, and bindings. This is critically important for restoring the broker's structure.
2. Configuration Files: Any modified files in

   /etc/rabbitmq/

   , such as

   rabbitmq.conf

   ,

   rabbitmq-env.conf

   , as well as certificate files if you are using TLS for AMQP connections.
3. Persistent Message Data: If you use persistent queues and messages, RabbitMQ stores them on disk in

   /var/lib/rabbitmq/mnesia/

   . Backing up this directory can be complex, as RabbitMQ must be stopped to create a consistent snapshot. For active systems, it is often preferable to restore persistent messages from the source systems rather than from a RabbitMQ backup.

For most scenarios, backing up definitions and configuration files is sufficient.

Simple RabbitMQ Definitions Auto-Backup Script

We will create a script that will export RabbitMQ definitions to a JSON file and save it. For storage, you can use S3-compatible storage or another VPS.

#!/bin/bash

# Directory for storing backups on the server
BACKUP_DIR="/var/backups/rabbitmq"
DATE=$(date +%Y%m%d%H%M%S)
BACKUP_FILE="${BACKUP_DIR}/rabbitmq_definitions_${DATE}.json"
CONFIG_FILES="/etc/rabbitmq/rabbitmq.conf /etc/rabbitmq/rabbitmq-env.conf" # Add other important configs here, e.g., certificates

# Create backup directory if it doesn't exist
mkdir -p "${BACKUP_DIR}"

echo "Starting RabbitMQ definitions backup..."

# Export RabbitMQ definitions
sudo rabbitmqctl export_definitions "${BACKUP_FILE}"

# Check if export was successful
if [ $? -eq 0 ]; then
    echo "RabbitMQ definitions exported to ${BACKUP_FILE}"
    
    # Copying configuration files
    for file in ${CONFIG_FILES}; do
        if [ -f "${file}" ]; then
            cp "${file}" "${BACKUP_DIR}/$(basename ${file})_${DATE}"
            echo "Copied ${file} to ${BACKUP_DIR}/$(basename ${file})_${DATE}"
        else
            echo "Warning: Configuration file ${file} not found."
        fi
    done

    # Clean up old backups (keep last 7 days)
    find "${BACKUP_DIR}" -type f -name "rabbitmq_definitions_*.json" -mtime +7 -delete
    find "${BACKUP_DIR}" -type f -name "*_${DATE}" -mtime +7 -delete # For configs, if they have the same date in the name
    echo "Old backups cleaned up."

    # Optional: upload to S3-compatible storage (requires awscli or s3cmd)
    # aws s3 cp "${BACKUP_FILE}" s3://your-s3-bucket/rabbitmq/definitions/
    # aws s3 cp "${BACKUP_DIR}/rabbitmq.conf_${DATE}" s3://your-s3-bucket/rabbitmq/configs/

else
    echo "ERROR: Failed to export RabbitMQ definitions."
    exit 1
fi

echo "RabbitMQ backup script finished."

Save this script, for example, as

/usr/local/bin/backup_rabbitmq.sh

sudo nano /usr/local/bin/backup_rabbitmq.sh
sudo chmod +x /usr/local/bin/backup_rabbitmq.sh

Then add it to

cron

sudo crontab -e

Add the following line to execute the script daily at 03:00 AM:

0 3 * * * /usr/local/bin/backup_rabbitmq.sh >> /var/log/rabbitmq_backup.log 2>&1

Where to Store Backups

Storing backups on the same server as the main service is highly discouraged. In case of server failure, you will lose both data and backups. Options:

• Cloud Storage (S3-compatible): Amazon S3, DigitalOcean Spaces, Backblaze B2. This is an economical and reliable option. Use

  awscli

  or

  s3cmd

  for automatic uploads.
• Separate VPS: A small VPS with a large disk, configured as a backup storage (e.g., using

  rsync

  or

  borgbackup

  over SSH).
• Local NAS/Server: If you have your own infrastructure, you can use it.

Restoring from Backup

To restore RabbitMQ definitions:

1. Install RabbitMQ on a new server.
2. Stop RabbitMQ:

   sudo systemctl stop rabbitmq-server

   .
3. Copy your

   rabbitmq_definitions_*.json

   backup to the server.
4. Restore definitions:

   sudo rabbitmqctl import_definitions /path/to/rabbitmq_definitions.json

   .
5. Copy configuration files from the backup to

   /etc/rabbitmq/

   .
6. Start RabbitMQ:

   sudo systemctl start rabbitmq-server

   .

Updates: rolling vs maintenance window

Updating RabbitMQ and Erlang is an important part of maintenance. The approach depends on whether you are using a cluster or a single node.

• Single Node: A maintenance window will be required, as RabbitMQ will be unavailable during the update. Schedule the update during periods of minimal load.
• Cluster (rolling upgrade): In a clustered configuration, a rolling upgrade can be performed, where each node is updated in turn while other nodes continue to serve requests. This ensures high availability but requires more complex setup and planning.

Always test updates in a staging environment before applying them to production. A full backup is recommended before updating.

# Update packages
sudo apt update
sudo apt upgrade -y

# After updating Erlang or RabbitMQ, always restart the service
sudo systemctl restart rabbitmq-server

Regularly check official RabbitMQ and Erlang announcements for information on new versions and important changes.

Troubleshooting + FAQ

Various issues can arise when working with RabbitMQ. In this section, we will cover typical scenarios and provide answers to frequently asked questions.

Cannot connect to RabbitMQ from a client, or Management UI is unavailable. What to do?

What to check:

1. Firewall (UFW): Ensure that RabbitMQ ports (5672 for AMQP, 15672 for Management UI) are open on your VPS. Use

   sudo ufw status verbose

   .
2. RabbitMQ Service Status: Check if RabbitMQ is running with the command

   sudo systemctl status rabbitmq-server

   . If it's inactive, try starting it:

   sudo systemctl start rabbitmq-server

   .
3. RabbitMQ Logs: Check the logs in

   /var/log/rabbitmq/rabbit@YOUR_HOSTNAME.log

   or

   /var/log/rabbitmq/rabbitmqctl.log

   for startup errors.
4. Is RabbitMQ listening on the correct ports: Use

   sudo netstat -tulnp | grep LISTEN | grep -E '5672|15672'

   . If the ports are not displayed, RabbitMQ might not be running or is configured incorrectly.
5. User Permissions: Ensure that the user you are using to connect has the appropriate permissions on the virtual host. Check in the Management UI or with the command

   sudo rabbitmqctl list_permissions -p / your_user

   .
6. Caddy/Reverse Proxy: If you are using Caddy for HTTPS, ensure that Caddy is running (

   sudo systemctl status caddy

   ) and its configuration (

   /etc/caddy/Caddyfile

   ) is correct.

RabbitMQ is running slowly or consuming too many resources. How to optimize?

What to check:

1. RAM and Disk Usage: In the Management UI, on the "Overview" tab, look at the memory and disk usage graphs. If RAM is consistently near its maximum, RabbitMQ starts flushing messages to disk, which slows down performance.
2. Message Persistence: If you have many persistent messages, they are actively written to disk. Ensure your disk is fast enough (SSD/NVMe).
3. Number of Queues and Messages: Too many queues or very large queues can consume a lot of resources. Consider consolidating queues or implementing a more aggressive message expiration policy (TTL).

4. vm_memory_high_watermark

   and

   disk_free_limit

   settings: Adjust these parameters in

   /etc/rabbitmq/rabbitmq.conf

   according to your resources.
5. Heartbeats: Ensure that clients are using Heartbeats. This helps RabbitMQ detect "dead" connections faster and free up resources.
6. Erlang/RabbitMQ Version: Ensure you are using up-to-date versions, as new versions often contain performance improvements.

How to reset the password for a RabbitMQ user?

If you have forgotten the password for a RabbitMQ user, you can reset (or change) it using

rabbitmqctl

sudo rabbitmqctl change_password myuser new_strong_password

Replace

myuser

new_strong_password

What is the minimum VPS configuration suitable for RabbitMQ?

For small projects or development, handling up to 100-200 messages per second, a VPS with 2 vCPU, 2-4 GB RAM, and 50-80 GB SSD will be minimally suitable. However, for stable operation and a small margin of safety, especially if moderate load or persistent queues are planned, 2 vCPU, 4 GB RAM, and 80-100 GB SSD are recommended. A fast disk (SSD) is crucial for RabbitMQ performance, especially when dealing with persistent messages.

What to choose — VPS or dedicated for this task?

For most beginner and medium-sized projects, a VPS will be the optimal choice. It offers a good price-to-performance ratio, sufficient flexibility, and ease of management. A dedicated server becomes preferable when your project reaches very large scales (thousands of messages per second, multi-node clustering), requires maximum stable and predictable performance without "noisy neighbor" effects, or has strict requirements for physical isolation and security. It's always best to start with a VPS and scale up to a dedicated server as needs grow.

Messages accumulate in queues but are not processed.

What to check:

1. Consumers: Ensure that your consumer applications are running and connected to RabbitMQ. Check their logs for errors.
2. Consumer Throughput: Consumers might not be processing messages as quickly as they arrive. Consider increasing the number of consumer instances or optimizing their code.
3. Prefetch count: The

   prefetch_count

   setting on the consumer side can affect processing speed. If it's too low, consumers might be idle. If it's too high, one consumer might take too many messages, while others wait.
4. Message Errors: Some messages might cause errors in consumers and be constantly returned to the queue (requeue), creating a "poison pill" scenario. Check consumer logs for recurring errors.

How to monitor RabbitMQ?

The Management UI provides excellent graphs and statistics for monitoring. For more advanced monitoring and alerts, you can use:

• Prometheus + Grafana: The RabbitMQ Management Plugin exports metrics that Prometheus can collect, and Grafana can visualize.
• Logs: Regularly review RabbitMQ logs for warnings and errors.
• System Metrics: Monitoring CPU, RAM, disk I/O on the VPS.

Conclusions and Next Steps

We have successfully installed and configured RabbitMQ on a VPS, preparing a reliable foundation for asynchronous task processing and building distributed systems. You have learned how to ensure basic server security, install necessary components, configure the message broker, and plan for backup and maintenance. Now you have a powerful tool that will allow your applications to operate more efficiently, scalably, and resiliently.

Further steps to optimize and expand your infrastructure may include:

1. Integration with Applications: Start connecting your services to RabbitMQ using client libraries for your programming language (e.g., Pika for Python, amqplib for Node.js, RabbitMQ .NET client for C#).
2. Monitoring and Alerts: Set up a comprehensive monitoring system (e.g., Prometheus + Grafana) to track key RabbitMQ metrics and receive notifications about potential issues.
3. Clustering: To enhance fault tolerance and throughput, consider creating a RabbitMQ cluster by deploying multiple nodes on different VPS or dedicated servers.
4. Performance Optimization: As the load grows, delve into fine-tuning RabbitMQ, exploring queue policies, lazy queues, federation, and Shovel for more complex scenarios.