locked
Signalr Issue on Azure RRS feed

  • Question

  • User-1311232049 posted

    Hi,

    We are using service fabric for hosting our messaging service (developed using signalr) and react web application as a client.  Everything works exactly as expected on local machines but not on azure.  We have configured CORS policies for cross origin handling since service and react web app hosted on different servers.  Configured sticky sessions in load balancer. This CORS Policy works in local machine with service and client hosted on different ports.

    Post hosting application on azure , we get following Error in browser console.

    WebSocketTransport.js:85 WebSocket connection to 'wss://xxx.azure.com:19081/ServiceFabricApp/MessagingMicroservice/notificationHub?id=7lqxt17yE5QTq5_sRHnWeQ' failed: Error during WebSocket handshake: Unexpected response code: 500

    Error: Failed to start the transport 'WebSockets': null

    Do share views.

    Thanks

    Tushar

    Thursday, January 3, 2019 2:03 PM

All replies

  • User61956409 posted

    Hi Tushar,

    Everything works exactly as expected on local machines but not on azure.  We have configured CORS policies for cross origin handling since service and react web app hosted on different servers.  Configured sticky sessions in load balancer.

    As you mentioned, your SignalR application works well on local, perhaps any additional configuration of Service Fabric or load balancer should be set to make it work. I recommend that you could post the question with the Service Fabric tag on StackOverflow.

    https://stackoverflow.com/questions/tagged/azure-service-fabric 

    With Regards,

    Fei Han

    Friday, January 4, 2019 1:57 AM