Share via

Package Microsoft.Azure.SignalR.AspNet hu bstate showed consistent connections

Rex Tez 20 Reputation points
2024-10-27T13:57:41.7633333+00:00

From the doc centre for my org website chat  condition using SignalR. My clients have complained there is connect issue every time. It was working fine for 3 months. Any update from Azure? I validated to see if it’s coming from other clients, and found an error

error":"Internal server error."}

 

I use nuget package Install-Package Microsoft.Azure.SignalR.AspNet

 

In Startup.cs, we are using  MapSignalR() for passing in connection. In our local, before migrating to Azure, with Asp.net SignalR the state of connection for hub and clients HubState showed consistent connections and not break. However, moving to Azure we are seeing this issue. I do not have a support plan to receive help, they said it’s only for billing and was redirected here.

var app = builder.Build();

 

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using Microsoft.AspNet.SignalR;

 

namespace ChatRoom

{

    public class ChatHub : Hub

    {

        public void Send(string name, string message)

        {

            // Call the broadcastMessage method to update clients.

            Clients.All.broadcastMessage(name, message);

        }

image.png

 

ASP.NET Core
ASP.NET Core
A set of technologies in the .NET Framework for building web applications and XML web services.
4,707 questions
Azure SignalR Service
Azure SignalR Service
An Azure service that is used for adding real-time communications to web applications.
151 questions
Accepted answer
  1. ajkuma 27,851 Reputation points Microsoft Employee
    2024-10-29T09:24:13.7666667+00:00

    Rex Tez, Following-up from the above, adding some pointers to isolate the issue.

    Based on my understanding, you maybe referring to this doc :Tutorial: Get started with ASP.NET Core SignalR -please do confirm. Which region have you provisioned your Azure resource?

    • Please review the URL of the request when 404 occurs. If the URL is targeting to your web app, and similar to {your_web_app}/hubs/{hubName}, check if the client SkipNegotiation is true. When the client initially negotiates with the app server, it receives a redirect URL. It's essential that the client does not bypass the negotiation process when using Azure SignalR
    • As described in Internals of Azure SignalR Service, Azure SignalR routes incoming client traffics to these server connections. When a server connection is dropped, it closes all the client connections it was serving.

    Also, kindly check Service Health and Resource Health status for more info.

    • Azure Service Health provides you with a customizable dashboard which tracks the health of your Azure services in the regions where you use them.
    • Azure Resource Health helps you diagnose and get support for service problems that affect your Azure resources. It reports on the current and past health of your resources.

    Regarding Azure support plans, please check doc: https://azure.microsoft.com/support/plans

    Kindly let us know, we will follow-up with you further.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.