34e1d79 attach RabbitMQ service to dokploy-network for backend connectivity
📊 Changes
1 file changed (+9 additions, -3 deletions)
View changed files
📝blueprints/rabbitmq/docker-compose.yml (+9 -3)
📄 Description
Description
This update ensures that the RabbitMQ service is accessible to the backend container by attaching it to the existing dokploy-network.
Previously, RabbitMQ was running on a separate network , which prevented the backend from resolving rabbitmq as a hostname and resulted in "unknown host" errors.
Changes
Added explicit networks section for RabbitMQ in docker-compose.yml.
Configured dokploy-network as an external network to reuse the existing Dokploy-managed network.
Mapped ports 5672 (AMQP) and 15672 (management UI) explicitly for consistency.
Impact
Backend services can now connect to RabbitMQ using:
amqp://<user>:<pass>@rabbitmq:5672
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/Dokploy/templates/pull/426
**Author:** [@hussainsabba](https://github.com/hussainsabba)
**Created:** 10/6/2025
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `fix/rabbitmq-backend-connectivity`
---
### 📝 Commits (1)
- [`34e1d79`](https://github.com/Dokploy/templates/commit/34e1d794bea3a9cd8bb107d2f35905e06b8c0514) attach RabbitMQ service to dokploy-network for backend connectivity
### 📊 Changes
**1 file changed** (+9 additions, -3 deletions)
<details>
<summary>View changed files</summary>
📝 `blueprints/rabbitmq/docker-compose.yml` (+9 -3)
</details>
### 📄 Description
## Description
This update ensures that the RabbitMQ service is accessible to the backend container by attaching it to the existing `dokploy-network`.
Previously, RabbitMQ was running on a separate network , which prevented the backend from resolving `rabbitmq` as a hostname and resulted in "unknown host" errors.
## Changes
- Added explicit `networks` section for RabbitMQ in `docker-compose.yml`.
- Configured `dokploy-network` as an external network to reuse the existing Dokploy-managed network.
- Mapped ports `5672` (AMQP) and `15672` (management UI) explicitly for consistency.
## Impact
- Backend services can now connect to RabbitMQ using:
```bash
amqp://<user>:<pass>@rabbitmq:5672
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/Dokploy/templates/pull/426
Author: @hussainsabba
Created: 10/6/2025
Status: ❌ Closed
Base:
main← Head:fix/rabbitmq-backend-connectivity📝 Commits (1)
34e1d79attach RabbitMQ service to dokploy-network for backend connectivity📊 Changes
1 file changed (+9 additions, -3 deletions)
View changed files
📝
blueprints/rabbitmq/docker-compose.yml(+9 -3)📄 Description
Description
This update ensures that the RabbitMQ service is accessible to the backend container by attaching it to the existing
dokploy-network.Previously, RabbitMQ was running on a separate network , which prevented the backend from resolving
rabbitmqas a hostname and resulted in "unknown host" errors.Changes
networkssection for RabbitMQ indocker-compose.yml.dokploy-networkas an external network to reuse the existing Dokploy-managed network.5672(AMQP) and15672(management UI) explicitly for consistency.Impact
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.