[PR #426] [CLOSED] attach RabbitMQ service to dokploy-network for backend connectivity #449

New Issue

GiteaMirror · 2025-11-22T20:38:52-06:00

GiteaMirror commented

2025-11-22 20:38:52 -06:00

📋 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)

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>

GiteaMirror added the pull-request label 2025-11-22 20:38:52 -06:00

GiteaMirror closed this issue

2025-11-22 20:38:53 -06:00

GiteaMirror referenced this issue

2025-11-22 20:39:07 -06:00

[PR #449] [MERGED] feat(blueprints): add Hoppscotch AIO blueprint with migrations #462

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#449