4

I am using Azure SignalR on Asp.Net Core 3.1, I receive SignalR message from azure service bus on API side (Back-End) and want to send the message to Angular client side (Front-End) as notification using azure SignalR. But getting this error

Md. Najrul Islam
  • 77
  • 3
  • 6

3 Answers3

2

I got this error when using aad connection with a service principal. I forgot to grant SignalR Service Owner role to the service principal which caused this error.

After providing the correct role and waiting a bit, it started working.

Ilya Chernomordik
  • 27,817
  • 27
  • 121
  • 207
1

Your server do not connect with SignalR service, please check following:

  • the connection string is correct.
  • the service mode, if you are using Azure SignalR service SDK, servive mode cannot be Serverless
  • for free instance, check the resouce usage in Diagnose and solve problems, make sure your message count do not hit the limit.
vwxyzh
  • 17
  • 2
0

This happened to me, getting 503 errors (disguised as CORS errors). The SignalR service was stuck in a 503 state for a half hour.

The fix for me was to create a new Azure SignalR service with a new name, otherwise I could have waited until my original SignalR service came back but I was impatient.

More context here: https://github.com/hashicorp/terraform-provider-azurerm/issues/11353#issuecomment-933959052

Josh Johanning
  • 840
  • 9
  • 16