RabbitMQ console returned 431

Question

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:

and can not use then console in the browser.

Culmination

Please use the chrome developer tools to investigate the exact API call that failed. – Tav

HTTP status 431 refers to a header size too large problem. I cleaned cookies and it worked, at least for now. It's worth knowing what is causing this. – Manet

Answer 1

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

Quianaquibble

Thanks for this! Another way to get it working is to open an incognito tab. – Kanazawa

Thanks a lot!!! i've been whit this error for 3hrs changing every config in my project, but this simply thing fixed everything! – Almuce

Answer 2

Another solution that worked here with the same issue, was only to change http://localhost:15672 to http://127.0.0.1:15672.

Eurus

Answer 3

I find I get this pretty consistently using edge, but never with chrome.

Edge it can reappear not long after clearing the cache etc.

"chrome-error://chromewebdata/:1"

Scenery

Answer 4

When running RabbitMQ on some host (e.g. localhost), and also debugging ASP.Net on the same host, the best option is to use different browsers (not just a new instance, but for example one on Firefox and the other in Chrome).

The reason is that ASP.net by default will have huge cookies set for localhost. These are also sent to RabbitMq when you try to log in.

Apparently rabbits cannot digest dinosaur cookies.

Using separate browsers will prevent the cookies for the same host (but different ports) to mix.

Weakling

Answer 5

I cleared the browser cache, but it had no effect. I was only able to log in when I cleared my cookies.

Claudie