Tomasz Kluczkowski

I think because that is the celeryconfig.py inside flower/examples

I am changing the celeryconfig.py to use rabbitmq as the broker_url and test again.

Ok , run with those env vars on both my linux machine and macbook pro with rabbitmq in docker and starting flower first and broker after creates the connection issue....

I attach the logs ``` [I 210627 18:50:56 web:2239] 200 GET /dashboard?json=1&_=1624816256363 (::1) 1.16ms [E 210627 18:50:57 broker:79] RabbitMQ management API call failed: [Errno 111] Connection refused [I 210627 18:50:57...

You can see before I start rabbitmq in docker, it says: ``` [E 210627 18:51:00 broker:79] RabbitMQ management API call failed: [Errno 111] Connection refused ``` Then I start rabbitmq...

The difference I see is that in your logs above after it connected it did all those inspect calls again: ``` [D 210623 21:22:50 connection:726] heartbeat_tick : for connection fa534377364f4406a3347da30bb814dc...

are you running latest rabbitmq docker image @mher? my command for local testing (I use `--network host` to have access to the api in the browser) ``` docker run --name...

I think this is the reason why it may be working for you. If you start via docker compose then both rabbitmq and flower start at more or less same...

Ok but it runs incorrect flower version with old celery. I guess we need to be strict here and use actual newest versions. I will create a new publicly available...

Hi @xneg, This is on my list as I have similar issue in our k8s deployment. I am aiming at re-using the `purge-offline-workers` CLI arg for this or some smarter...