Closed michael-eckhart-woellkart closed 7 months ago
Hi @michael-eckhart-woellkart,
Thanks for reporting this issue. To help protect the management portal, we recently updated the associated configuration (please see issue/53114). You can get access by setting the new RABBITMQ_MANAGEMENT_ALLOW_WEB_ACCESS
environment variable to true
in your docker-compose file (as described in the README.md file).
Hope it helps!
Thank you, that worked. Just the name is maybe a little bit wrong. Because it is not only the web access, also the amap connection works with this setting :).
Name and Version
bitnami/rabbitmq:3.10
What architecture are you using?
amd64
What steps will reproduce the bug?
We can fix it by adding a volumne:
File content:
What is the expected behavior?
Would it be possible to set this setting by a enviroment varibale, if not the enviroment variables "RABBITMQ_USERNAME" and "RABBITMQ_PASSWORD" does not make any sense.
What do you see instead?
Error Log:
Additional information
No response