Not able to access RabbitMQ node on ports 15762 and 5762 #12861
-
Community Support Policy
RabbitMQ version used4.0.3 Erlang version used26.2.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)See https://www.rabbitmq.com/docs/logging to learn how to collect logs Logs from node 3 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs rabbitmq.confSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location Steps to deploy RabbitMQ clusterStandalone server no cluster Steps to reproduce the behavior in questionI try installing RabbitMQ on ubuntu 24.04 using
whereas when I check the RMQ service it is there
Still I cant access the server at 15672, when I type advanced.configSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location Application code# PASTE CODE HERE, BETWEEN BACKTICKSKubernetes deployment file# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKSWhat problem are you trying to solve?Access RabbitMQ site |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
@eliassal our Community Support policy which you supposedly have read clearly states that we will not troubleshoot networking for you. We have dedicated documentation guides that explain how we would do it, for network connectivity, for TLS, as well as on the ports used by RabbitMQ, HTTP API request logging and even how to set up a reverse proxy for the HTTP API with Apache 2 or Nginx. Please take it from here. |
Beta Was this translation helpful? Give feedback.
-
means that CLI tools failed to authenticate (not connect) to the node in question. See How CLI Tools Authenticate to Nodes. It has nothing to do with the HTTP API because standard (not |
Beta Was this translation helpful? Give feedback.
@eliassal our Community Support policy which you supposedly have read clearly states that we will not troubleshoot networking for you.
We have dedicated documentation guides that explain how we would do it, for network connectivity, for TLS, as well as on the ports used by RabbitMQ, HTTP API request logging and even how to set up a reverse proxy for the HTTP API with Apache 2 or Nginx.
Please take it from here.