Azure SignalR Service is not connected yet, error many times for blazer app

[swiftinitdotcom]

Azure SignalR Service is not connected yet, error many times for blazer app

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Exceptions (if any)

Further technical details

• Your Azure SignalR SDK version
• Your Server ASPNETCORE version or Assembly version of Microsoft.AspNetCore.SignalR
• Your SignalR Client SDK version

[vicancy]

Is it a persistent error or a transient error? Azure SignalR Service is not connected yet means the blazer app is not connected to the service, here contains detailed info and troubleshooting guidance for such error: https://docs.microsoft.com/en-us/azure/azure-signalr/signalr-howto-troubleshoot-guide#500-error-when-negotiate-azure-signalr-service-is-not-connected-yet-please-try-again-later

[swiftinitdotcom]

Its for few days now, before it was working nicely, now I had to move to onpremise because of this... until this gets resolved

[swiftinitdotcom]

Strange thing is same published app works just fine on on premise and when I publish on azure this signal r error....

[vicancy]

Consistently repro? Any exceptions from the app server side? Can it be reproed from localhost?

[swiftinitdotcom]

yes it posts back and does not behave like blazer app in azure due to signarr error, works just fine on server iis

[vicancy]

If it can be repro-ed consistently from localhost, could you try this: https://docs.microsoft.com/en-us/azure/azure-signalr/signalr-howto-troubleshoot-guide#troubleshooting-guide

[vicancy]

Please feel free to reopen the issue if there are further updates.