Apologies you are experiencing this issue. Kindly share more details about your app framework.
- You may leverage Azure SignalR Services diagnostics from Azure Portal> Navigate to your ASignalR app in the Azure Portal. (screenshot below)
- In the left navigation, click on
Diagnose and solve problems
- Review - “Resources Usage" and “Availability and Performance” options.
Typically, on ASP.net core, when using WebSockets and skipNegotiation = true
Please check these to isolate the issue:
- When using multiple servers without sticky sessions, the connection can start on one server and then switch to another server. The other server is not aware of the previous connection.
- Verify the client is connecting to the correct endpoint. For example, the server is hosted at
http://127.0.0.1:5000/hub/myHub
and client is trying to connect tohttp://127.0.0.1:5000/myHub
. - If the connection uses the ID and takes too long to send a request to the server after the negotiate, the server:
- Deletes the ID. - Returns a 404.
- Checkout this doc reference for more info: Troubleshoot connection errors
If the issue still persist, please check the logs to fetch more info
Logging and diagnostics in ASP.NET Core SignalR -- This article provides guidance for gathering diagnostics from your ASP.NET Core SignalR app to help troubleshoot issues.
Kindly let us know, I'll follow-up with you further.