Increase rabbitmq frame_max to 8192

Feature Requests
1

feature request based of a question:

Describe the problem/error/question

I installed a RabbitMQ version 4.1.0 and was not able to establish a successful connection with n8n.

What is the error message (if any)?

When saving the connection settings and testing the connection, n8n responds with:
Couldn’t connect with these settings
read ECONNRESET

The RabbitMQ log gives more insight:
error: FORMATTER CRASH: {“closing AMQP connection ~tp (~ts):~nfailed to negotiate connection parameters: ~ts”,[<0.634.0>,<<“10.0.1.34:37498 → 10.0.1.46:5672”>>,“3s”,“negotiated frame_max = 4096 is lower than the minimum allowed value (8192)”]}

According to ChatGPT, here is the problem:
In RabbitMQ 4.1.0, the minimum acceptable frame_max value during the connection negotiation phase was increased from 4096 bytes to 8192 bytes. This change was implemented to accommodate larger JWT tokens during authentication. As a result, clients that attempt to negotiate a frame_max value lower than 8192 bytes will have their connections rejected .

So unless you have covered this problem in a newer version (which I did not find in the changelog), you need to updated the related libraries, so that n8n is able to connect to RabbitMQ version 4.1.0. Until you resolve that, I will downgrade RabbitMQ to an older version.

2

Hello,

Same issue here, I wasz abble to downgrade to
rabbitmq:4.0.6-management
And it worked again, but then I tried to go with:
rabbitmq:4.0.9-management
It kept working but the executions in n8n are starting, but disapers at the end of exectution ! (and the message is delivered to the next queue.
I guess the update in n8n should solve it all.

3

A fix would be important. My hoster does not allow downgrades of RabbitMQ. Thus important workflows are not working at the moment.

4

Same issue here, it’s kind of a big deal for us at the moment so it’d be cool if this could be fixed. Doesn’t look like a hard one to handle either!