inkerinmaa opened a new issue, #56186:
URL: https://github.com/apache/airflow/issues/56186

   ### Apache Airflow version
   
   3.1.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Using official docker compose 
tutorial[https://airflow.apache.org/docs/apache-airflow/3.1.0/howto/docker-compose/index.html](url)
 added network settings to each service in compose:
   `
     networks:
       - test`
   And at the end of compose file:
   `networks:
     test:
       name: test
       external: true`
   caused tasks in example dags get stucked in queued state and apiserver log 
says:
   `JWT token is not valid: Signature verification failed` 
   Same happens if I add 
   `AIRFLOW__API__BASE_URL: 'https://tst.mycompany.com/airflow'`
   to use reverse-proxy for accessing UI
   
   ### What you think should happen instead?
   
   Tasks should be running and no errors in logs appear
   
   ### How to reproduce
   
   Use official docker compose 
tutorial[https://airflow.apache.org/docs/apache-airflow/3.1.0/howto/docker-compose/index.html](url)
   and add all services to any external docker network
   docker network create airflow
   and add to each service
   `networks:
       - airflow`
   OR 
   add environment varible
   `AIRFLOW__API__BASE_URL: 'https://tst.mycompany.com/airflow'`
   
   
   ### Operating System
   
   Debian
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Docker-Compose
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] 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]

Reply via email to