RabbitMQ on message trigger node issue

Hi!
I am trying to implement a workflow that listens to some events queued into a RabbitMQ queue. The producer of the message is a SpringBoot microservice that works correctly (so I have no problem connecting to one of the Railway projects I have).
In my case, I have a “n8n w/workers” template with its corresponding workflow and a rabbitmq template. I am facing an issue with how the trigger node handles those events. Couriously if I activate the workflow, events from the queue are consumed (even thought I am not able to track / visualize that data in the workflow). Credentials seem to work correctly. Everytime I set them up I get the same green checkmark. Any idea of what could be happening?

Useful information of how I have RabbitMQ infrastructure setted up.
EXCHANGES:
domain_events
QUEUES
courses.course.notify_users_on_course_created
BIND
agi.courses.*.event.course.created

The exchange is of type topic. The queue is durable. They are both bind with that routing key. This is the config for the trigger node:


Credentials:

The data needed for this part is the one found in the Railway’s RabbitMQ template with ots corresponding values.

EXTRA BACKGROUND
After login into the RabbitMQ UI the user connection gets closed

2024-07-22 07:55:39.203486+00:00 [info] <0.2060.0> closing AMQP connection <0.2060.0>

Logs in primary and worker container:

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hey @AnderGI,

What is the actual issue you are seeing? Can you also confirm the version of n8n you are using?

1 Like

Oh thanks, but I have already solved it. Everything works correctly if I do not keep the RabbitrMQ UI opened. However, the version of n8n is the 1.50.1 if I am not wrong.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.