tobiasholzner-whiteduck opened a new issue, #8158:
URL: https://github.com/apache/incubator-devlake/issues/8158

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   We are running DevLake in an Azure Container Apps Environment. We have 
seperate Container Apps for Server, UI and the Dashboard. It worked well until 
the UI started to return 502 bad gateway errors. If I read the Nginx Logs I get 
the following error:
   
   `
   2024/10/23 13:11:30 [error] 18#18: invalid UDP DNS response 22651 fl:85A0
   `
   `
   2024/10/23 13:11:30 [error] 18#18: invalid UDP DNS response 7473 fl:85A0
   `
   `
   2024/10/23 13:11:33 [error] 18#18: *83 
app-apache-devlake-prod-server.asdf.westeurope.azurecontainerapps.io could not 
be resolved (110: Operation timed out), client: 100.100.0.83, server: 
localhost, request: "GET /api/version HTTP/1.1", host: 
"app-apache-devlake-prod-ui.asdf.westeurope.azurecontainerapps.io:443"
   `
   
   - If I lookup the server with nslookup or by using curl with the nginx user 
the name gets resolved.
   - When I restart the container it works for a few times
   - The /etc/resolv.conf show me that I use the nameserver 127.0.0.11
   - I use the v1.0.1 with the Images from Dockerhub
   
   
   ### What do you expect to happen
   
   To work well, like before
   
   ### How to reproduce
   
   - create seperate ACAs and call /api/version on the UI ACA
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v1.0.1
   
   ### 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://www.apache.org/foundation/policies/conduct)
   


-- 
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