Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

RabbitMQ console returned 431

I start rabbitmq on docker with command:

docker run -d --hostname my-rabbit --name rabbit-fox -p 5672:5672 -p 8090:15672 rabbitmq:3-management

it runs fine and i can log into console, but later on Chrome browser i get this:

enter image description here

and can not use then console in the browser.

like image 649
tryingHard Avatar asked Dec 07 '18 10:12

tryingHard


People also ask

How do I use RabbitMQ Management Console?

To be able to use RabbitMQ management console, we first need to enable a management plugin that allows us to use RabbitMQ management console. The plugin name is rabbitmq_management and we'll enable it using the following command:

How to delete a queue in RabbitMQ?

Step 1: Navigate to the RabbitMQ management portal, type your credentials and log in. Step 2: Go to the Queues tab, and click on the name of the Queue you want to delete. Step 3: After you’ve chosen the queue you want to delete, you’ll be taken to its detail page where you’ll find a delete or purge option towards the bottom of the list.

What is management UI in RabbitMQ?

RabbitMQ management console (also called Management UI) is a built-in monitoring option for RabbitMQ. It's very useful during the development since we can easily check what's happening with our messages and where did they end up. 2. Solution

What are normal RabbitMQ permissions and permissions?

Normal RabbitMQ permissions to resources still apply to monitors and administrators; just because a user is a monitor or administrator does not grant them full access to exchanges, queues and bindings through the management plugin or other means. All users can only list objects within the virtual hosts they have any permissions for.


1 Answers

Clearing browser's cache & memory did the work in my case.

After facing the same issue these steps performed: I tried to re-run the docker, even I got to the point I re-installed the RabbitMQ server image without any result.

It simply was solved when I cleared the browser's Cache & Memory

like image 149
Shrembo Avatar answered Sep 29 '22 06:09

Shrembo