SignalR failed in production after re-authentication

Question

I use SignalR for online chat on my website. When I start my app in local enviroment everything works, but in production and staging enviroment everything works good before I try to re-authenticate - in this case my chat fails with the next issues in console:

Answer 1

@Anya Mirch , Azure SignalR Service exposes resource logs, you can also enable logs for service side.
To isolate the issue, you may enable server/client side logs to capture failures.
You may take look at the resource logs to fetch more details, aids (in encountering connection unexpected growing or dropping situation).

Typical issues are often about connections, unexpected quantity changes, connections reach connection limits and authorization failure. So, kindly review these settings:

-unexpected-connection-number-changes

• This article outlines connection lifetime and disconnection scenarios
• Timeout limit is reached while SignalR is attempting to re-establish a lost transport connection, please try to change/increase Timeout settings in application start up.

The default ConnectionTimeout(110 secs), DisconnectTimeout (30 secs), and KeepAlive(10 secs) values are appropriate for most scenarios but can be changed if your environment has special needs.
https://github.com/Azure/azure-signalr/blob/dev/docs/run-asp-net-core.md#3-configure-service-options