[Questions] help with amqps connection issue #13830
-
Community Support Policy
RabbitMQ version used4.1.0 Erlang version used27.3.x Operating system (distribution) usedUbuntu 24.04 How is RabbitMQ deployed?Debian package rabbitmq-diagnostics status outputSee https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics Logs from node 1 (with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs Logs from node 2 (if applicable, with sensitive values edited out)n/a Logs from node 3 (if applicable, with sensitive values edited out)n/a rabbitmq.confSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location Steps to deploy RabbitMQ clusterinstalled rabbitmq according to instructions on rabbitmq.com, following tutorials to incorporate TLS verification and relying on debian packages whenever possible. Steps to reproduce the behavior in questioncall advanced.confign/a Application coden/a Kubernetes deployment filen/a What problem are you trying to solve?after logging in to update my ubuntu 24.04 server today, the message queue is no longer working. inspection of logs revealed the error trace being report from a Node.js application using AMQP that has been working as expected since deployment in January. TLS credentials are valid, and i've verified connection between relevant machines using s_server/s_client as well as locally using s_client to connect to the AMQP instance (which appears as the final entries in the log included above). this error occurred when the application called |
Beta Was this translation helpful? Give feedback.
Answered by
michaelklishin
Apr 30, 2025
Replies: 1 comment 1 reply
-
|
As our Community Support Policy explicitly states, we won't troubleshoot TLS, OAuth 2 and LDAP for non-paying users. There is a dedicated TLS troubleshooting guide that explains the methodology to use. Node.js amqplib and RabbitMQ 4.1.0 CompatibilityIn the Initial AMQP 0-9-1 Maximum Frame SizeBefore a client connection can negotiate a maximum frame size (frame_max), it must authenticate With this release, the value was increased from the original 4096 bytes to 8192 Clients that do override frame_max now must use values of 8192 bytes or greater. amqplib is a popular client library that has been using |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
thank you. i had read through all of these documents before posting, but i missed the one line about upgrading amqplib to 0.10.7. that solved the problem. |
Beta Was this translation helpful? Give feedback.
Answer selected by
michaelklishin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As our Community Support Policy explicitly states, we won't troubleshoot TLS, OAuth 2 and LDAP for non-paying users.
There is a dedicated TLS troubleshooting guide that explains the methodology to use.
Node.js amqplib and RabbitMQ 4.1.0 Compatibility
In the
4.1.0release notes under Breaking Changes and Compatibility Notes there is an explicit mention of a certain Node.js client that you must upgrade to the latest version or your application will not be able to connect to RabbitMQ 4.1.0 plus:Initial AMQP 0-9-1 Maximum Frame Size
Before a client connection can negotiate a maximum frame size (frame_max), it must authenticate
successfully. Before the authenticated phase, a special lower fra…