Title: MQTTX Unable to Connect to RabbitMQ Cluster Behind Ingress-NGINX, But RabbitMQ UI is Accessible

[surendar-argtech]

Community Support Policy

• I have read RabbitMQ's Community Support Policy
• I run RabbitMQ 4.x, the only series currently covered by community support
• I promise to provide all relevant information (versions, logs from all nodes, rabbitmq-diagnostics output, detailed reproduction steps)

RabbitMQ version used

4.0.5

Erlang version used

27.2.x

Operating system (distribution) used

linux

How is RabbitMQ deployed?

Kubernetes Operator(s) from Team RabbitMQ

rabbitmq-diagnostics status output

See https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics

# PASTE OUTPUT HERE, BETWEEN BACKTICKS

Logs from node 1 (with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 2 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

Logs from node 3 (if applicable, with sensitive values edited out)

See https://www.rabbitmq.com/docs/logging to learn how to collect logs

# PASTE LOG HERE, BETWEEN BACKTICKS

rabbitmq.conf

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location

# PASTE rabbitmq.conf HERE, BETWEEN BACKTICKS

Steps to deploy RabbitMQ cluster

RabbitMQ is deployed on Kubernetes.
Ingress is managed by ingress-nginx.
RabbitMQ management UI works fine via the ingress.
MQTTX is configured to use the same broker URL as exposed by the ingress.

Steps to reproduce the behavior in question

I’m running a RabbitMQ cluster behind an ingress-nginx load balancer in Kubernetes. While I’m able to successfully access the RabbitMQ management UI via the ingress, I’m facing an issue with the MQTTX desktop client. It is unable to connect to the RabbitMQ broker URL.

advanced.config

See https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location

# PASTE advanced.config HERE, BETWEEN BACKTICKS

Application code

# PASTE CODE HERE, BETWEEN BACKTICKS

Kubernetes deployment file

# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKS

What problem are you trying to solve?

RabbitMQ is deployed on Kubernetes.
Ingress is managed by ingress-nginx.
RabbitMQ management UI works fine via the ingress.
MQTTX is configured to use the same broker URL as exposed by the ingress.

[michaelklishin]

@surendar-argtech we will not troubleshoot MQTTX or Ingress-Nginx for you.

Enable HTTP API logging and use tcpdump to take a traffic capture, then inspect what every part involved sends and receives with Wireshark.

How to troubleshoot MQTTX or Ingress-Nginx is not something our team will help with in any way.