rv2931 opened a new issue, #59373: URL: https://github.com/apache/airflow/issues/59373
### Apache Airflow version 3.1.4 ### If "Other Airflow 2/3 version" selected, which one? _No response_ ### What happened? I'm trying the docker compose stack from official curl -LfO 'https://airflow.apache.org/docs/apache-airflow/3.1.4/docker-compose.yaml'. The stack is managed via portainer.io tools When I start the stack, the webserver is running but when I trigger a simple task, it fails with no logs When I go to celery worker container, the output says: `Invalid auth token: Signature verification failed` as said in issue #49646 a workaround works consisting in explicitly declaring AIRFLOW__API_AUTH__JWT_SECRET='random value' in the docker compose common environment variables ### What you think should happen instead? The celery work should be able to connect to airlfow API with the correct JWT_SECRET ### How to reproduce - Get the docker compose demo file: https://airflow.apache.org/docs/apache-airflow/3.1.4/docker-compose.yaml - Configure it to obtain the web interface working - Launch any task - It goes in error - check celery worker conteinr output - verify that the error messge is `Invalid auth token: Signature verification failed` ### Operating System debian trixie/sid ### Versions of Apache Airflow Providers _No response_ ### Deployment Docker-Compose ### Deployment details I use portainer.io tool to manage my docker compose stacks and overload environment variables ### Anything else? _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
