Development

RabbitMQ

RabbitMQ on a VPS: the AMQP message broker behind your job queues, with its web management console served over HTTPS.

In validation

About RabbitMQ

RabbitMQ is a free, open-source message broker (MPL-2.0 licence) and the most widely deployed AMQP server. Your applications drop messages into it — an invoice to generate, an email to send, an image to resize — and workers consume them at their own pace: a traffic spike no longer takes the site down, and a failed job is retried instead of lost. Laravel, Django with Celery, Spring, Node.js, .NET or Go connect to it with their usual libraries.

A single container is enough, with the web management console to watch queues, rates and consumers. The ServOrbit installation creates the admin account with a generated password, publishes the console over HTTPS and keeps the AMQP port on the VPS loopback, out of reach from the Internet.

What gets installed

Ready when the VPS starts

Compatible OS
Choice of Linux distributions
Application
RabbitMQ
Tech stack
DockerErlang
Minimum RAM
1 GB minimum
Minimum CPU
1 vCPU
Default port
8126
Access
root over SSH

Key features

  • Durable message queues — messages survive a server restart, and an unacknowledged message is redelivered.
  • Web management console — queues, exchanges, connections, rates and pending messages, in real time.
  • Flexible routing — direct, topic, fanout and headers exchanges to send a message to one queue, several or all.
  • Quorum queues and streams — replicated queues for critical data, and replayable logs for high volumes.
  • Multi-protocol — AMQP 0-9-1 and AMQP 1.0, plus MQTT and STOMP through plugins.
  • Isolation by vhost — each application gets its own space, user and permissions.

When to use this solution?

Move slow tasks out of web requests

A Laravel or Django shop sends invoice generation, emails and exports to a queue: the page answers at once, and workers handle the rest in the background.

Let microservices talk to each other

A confirmed order publishes a single event; stock, billing and notifications each receive it in their own queue, without the services knowing each other.

Absorb traffic spikes

During a campaign or a sale, messages pile up in the queue instead of overloading the database: workers catch up as soon as the spike is over.

Guide

Deploy RabbitMQ on your VPS

  1. Create the VPS and choose the address

    Order an Ubuntu 24.04 VPS: 2 GB of RAM suits most projects. RabbitMQ is installed with a domain, so that its management console is served over HTTPS: a subdomain of one of your domains, or the VPS's free subdomain (rabbitmq.{dns_slug}.servorbit-dns.com), HTTPS included. There is no need to buy a domain name.

  2. Install RabbitMQ from the Marketplace

    In your client area, select RabbitMQ, choose the address and click Install. The script deploys the official image with the management console, creates the admin account with a generated password and configures the nginx reverse proxy over HTTPS. RabbitMQ starts in about fifteen seconds.

  3. Sign in for the first time

    Open https://your-domain and sign in with the admin user and the password shown in your client area. The factory guest account does not exist. The password is only set on first start: if you change it in the console, your new password is kept across restarts.

  4. Create one vhost and one user per application

    In the Admin tab, create a virtual host per application (for example shop) and a user with permissions on that vhost only. Never give the admin account to an application: if it leaks, only its vhost is exposed.

  5. Connect your applications

    The AMQP port 5672 stays on the VPS loopback. An application installed directly on the VPS connects to amqp://127.0.0.1:5672; a containerised application joins the RabbitMQ Docker network: `bash docker network connect rabbitmq <application-container>` Address to use: amqp://<user>:<password>@rabbitmq:5672/<vhost>.

Proof

What we promise, and how to check it

  • The recommended size, for every application

    The memory required and the VPS that covers it, on every card.

    Check it: the “Recommended VPS” line of each card

  • Root access, on your server

    You administer the system over SSH; your data stays on your VPS.

    Check it: the “What is installed” section of each page

  • You pay for the VPS, not the software

    The applications are open source: your only cost is the VPS that runs them.

    Check it: in the cart, no line for the application

Frequently asked questions

Questions about RabbitMQ

← Back to DevelopmentAll applications
Redis can act as a simple queue, and many projects start that way. RabbitMQ is built for it: acknowledgements, redelivery of unprocessed messages, durable queues, routing through exchanges and a console that shows what is waiting. As soon as losing a job is costly, or several services consume the same events, RabbitMQ is the safer choice.

Activate RabbitMQ on your infrastructure.

Dedicated Cloud VPS — IPv4 included, server in Europe, support included. Your data never leaves your server.

All applications

RabbitMQ also runs on a dedicated server, when models or data outgrow a VPS. See dedicated servers