Error: Failed to start the transport 'LongPolling': Error: No Connection with that ID: Status code '404'

Question

I have created a signalr selfhosted webapp service that connects to on prem signalr service using hybrid connection. This self hosted service then broadcast the changes to front end and back to on prem signalR. The self hosted service is fronted by a front door.

Everything works fine locally with long polling (front door doesn't support websockets), but doesn't work when deployed in Azure. Error: Failed to start the transport 'LongPolling': Error: No Connection with that ID: Status code '404'

Anything i am missing?

Answer 1

Enabled the clientAffinity on the app service and that did the magic. Also on Azure front door removed the host header on the backend