Hello @Lokesh Royal - Thank you for posting on MS Q&A!
On the Azure Containers Apps side for supporting WebSocket, it sounds like you already have the correct configuration with the
transport type set to either
http, ref: Set up HTTPS or TCP ingress in Azure Container Apps
Assuming that you have it configured so and the fact that the WebSocket connection is being established, I believe the root cause may have to do with the
reason is : 1006 error which is missing the actual reason message. I've come across this post on StackOverflow with many people weighing in on Close Code 1006 caused by Abnormal Closure by the client browser which appears to be common with Chromium-based browsers. In your case though, I'd try increasing the
nginx default timeout per this answer, and if that doesn't resolve the issue, I'd start debugging the client side and the front-end code. Feel free to tag me, and let me know how it goes, and I'd be happy to help!