WebSocket connection to fail #5252
Unanswered
raghu-gade
asked this question in
Q&A
Replies: 1 comment 1 reply
-
That's weird, according to your screenshot the client actually reaches the Socket.IO server, since we see the handshake packets. If I understand correctly, it works well without ingress path? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Here is my socket connection code. It's working fine with socket URL 'wss://my-application.eastus.cloudapp.azure.com' in application we need to add ingress path 'nodeserver'. it is taken and connected initially and disconnected immediately next subsequent connections fail error showing.
WebSocket connection to 'wss://my-application.eastus.cloudapp.azure.com/nodeserver/socket.io/?EIO=4&transport=websocket' failed:
While disconnect the socket showing message Disconnected: transport close


Any alternate solution with ingress path socket connection
Beta Was this translation helpful? Give feedback.
All reactions