What's installed on your RabbitMQ server?
- RabbitMQ 4 from the official Docker image's Alpine build with the management UI, on the latest 4.x at install time
- Management UI over HTTPS through Caddy on an sslip.io address, so a domain is optional
- Port 5672 open for AMQP connections
- An admin account called yonetici instead of guest, with a generated password
- Queue data kept in the rabbit_veri Docker volume
- Compose file at /opt/seturack/rabbitmq/compose.yaml
- Firewall with only ports 22, 80, 443 and 5672 open
What size do you need for RabbitMQ?
RabbitMQ's production checklist asks for at least 4 GiB of RAM and 4 cores per node, and says RabbitMQ wasn't designed for single-core environments. Treat the smallest size, 2 GB, as a development and test size, and for production choose 4 GB and add CPU. Publishers are held back once memory use passes 60 percent of RAM, and persistent messages fill the disk too. You can grow RAM, CPU and disk separately from your panel, and your data and IP address stay the same.
| Use | Size | Price | Choose |
|---|---|---|---|
| Starter | 4 GB RAM · 2 vCore · 60 GB NVMe | $6.89/mo | |
| Medium | 8 GB RAM · 4 vCore · 120 GB NVMe | $13.62/mo | |
| Powerful | 16 GB RAM · 8 vCore · 200 GB NVMe | $25.15/mo |
Who is it for?
- Teams moving background jobs away from their web app
- Developers wiring up messaging between services
- Projects using Celery, Spring AMQP or amqplib
- Anyone who wants a real queue in development and testing
What happens after you order?
- Set the size and complete your payment.
- Your server starts and RabbitMQ installs itself. This took about 8 minutes in our real-server tests.
- On the Overview tab, the link in the Panel address row opens the management UI. Enter the details from the Login and Password rows.
- Connect your app: amqp://yonetici:PASSWORD@IP:5672/%2f
- On the Admin tab, create a separate user and virtual host (vhost) for your app.
With every server
- Daily backups included in the price
- Unlimited traffic
- Full root access
- Scale RAM and CPU up or down later, and grow the disk
- Location: Istanbul · IST-1.
Good to know
- Port 5672 has no TLS and is open to the internet, and ufw can't close it because Docker publishes it. To limit it, change the port line in compose.yaml to 127.0.0.1:5672:5672, run docker compose up -d and connect through an SSH tunnel.
- The free disk limit defaults to 50 MB, which the official docs consider suitable only for development. Raise disk_free_limit for production.
- Passing the memory or disk limit blocks publishing connections. As consumers take messages, the alarm clears and traffic flows again.
- The image follows the 4-management-alpine tag but doesn't update itself. For a newer 4.x, run docker compose pull and docker compose up -d in the folder.
RabbitMQ questions and answers
How do I connect to my RabbitMQ server?
Your connection string is amqp://yonetici:PASSWORD@IP:5672/%2f. The %2f at the end stands for the default virtual host, /. RabbitMQ's URI spec says a plain trailing / means an empty name. The IP and password are in your panel, and you give this string to your client library.
How much RAM does RabbitMQ need?
RabbitMQ's official production checklist asks for at least 4 GiB of RAM and 4 cores per node. For development and testing, you can start with 2 GB.
How do I open the RabbitMQ management UI?
The Panel address link in your panel opens it over HTTPS. The login is yonetici and the password is in your panel. From the UI you can create queues, exchanges, users and virtual hosts, and send and receive test messages. Port 15672 isn't open to the outside.
Is the RabbitMQ AMQP connection encrypted?
RabbitMQ's port 5672 has no TLS in this install, so the password and messages travel unencrypted. For sensitive data over the internet, use an SSH tunnel, or set up a TLS listener on port 5671 with your own certificate and publish that port.
Why are my RabbitMQ publishers being blocked?
RabbitMQ blocks publishing connections when memory use passes 60 percent of RAM or free disk drops below the limit. The alarm clears as consumers take messages. You can see the state on the Overview page of the management UI, and if it keeps happening, scale the server up.
Can I create a separate RabbitMQ user for my app?
Yes. On the Admin tab of the UI, add a virtual host and a user and grant permissions. From the command line, in /opt/seturack/rabbitmq, run docker compose exec rabbitmq rabbitmqctl add_user NAME PASSWORD. A new user can't connect until it has permissions.