SignalR is not delivering message

Question

SignalR is not delivering message

zigzagcloud 0

SignalR is not delivering message. The service seems stop working from yesterday.

I setup System Error Alert on SignalR and it emails me the system error alert when I sent a message to the signalR service and not delivering to the expected clients

This is the alert rule id

[https://portal.azure.com/#resource/subscriptions/9d952a63-5dd8-4c4f-85e1-1023a5590d9a/resourceGroups/POC/providers/microsoft.insights/metricAlerts/SignalR System Error](https://portal.azure.com/#resource/subscriptions/9d952a63-5dd8-4c4f-85e1-1023a5590d9a/resourceGroups/POC/providers/microsoft.insights/metricAlerts/SignalR%20System%20Error"https://portal.azure.com/#resource/subscriptions/9d952a63-5dd8-4c4f-85e1-1023a5590d9a/resourceGroups/POC/providers/microsoft.insights/metricAlerts/SignalR System Error")

Shree Hima Bindu Maganti 3,825 Reputation points Microsoft External Staff

2025-02-14T11:17:57.5533333+00:00

Hi @zigzagcloud
To address the issue of SignalR not delivering messages,

Access the Azure Portal.->Navigate to your SignalR Service instance.

Select Diagnose and solve problems.

Investigate any reported outages, throttling incidents, or system errors.

In the Azure Monitor, go to Alerts.

Your alert rule indicates that System Errors are occurring.

Review the detailed error messages to identify the root cause.

Within your SignalR Service instance, select Metrics.

Monitor key metrics such as Server Connections, Message Count, and Errors.

If Application Insights is configured, examine the logs for any anomalies.

Confirm that the server maintains a stable connection to the SignalR service.

Ensure clients are successfully connecting and receiving messages.

For setups utilizing Serverless mode, verify that the associated functions or services are operational.

If employing Azure Active Directory (AD) or JSON Web Tokens (JWT) for authentication, check for expired tokens or altered permissions.

Dispatch a basic test message,

await hubContext.Clients.All.SendAsync("ReceiveMessage", "Test Message");

If this message is received, potential issues may include client-side filtering or message serialization problems.

Restart both the SignalR Service and your associated web application or backend services.

If recent updates were applied, consider reverting to a prior stable version to determine if the update introduced the issue.

troubleshooting Azure SignalR Service issues.
https://learn.microsoft.com/en-us/answers/questions/1691669/azure-signalr-service-(serverless)-stopped-working

If further assistance is required, please provide additional details about the errors encountered or any recent changes to your system configuration.
Shree Hima Bindu Maganti 3,825 Reputation points Microsoft External Staff

2025-02-17T14:53:23.86+00:00

Hi @zigzagcloud

Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.
Shree Hima Bindu Maganti 3,825 Reputation points Microsoft External Staff

2025-02-20T06:53:36.9466667+00:00

Hi @zigzagcloud

Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.

1 answer

Your answer

Shree Hima Bindu Maganti 3,825 Reputation points Microsoft External Staff

2025-02-14T11:17:57.5533333+00:00

Hi @zigzagcloud
To address the issue of SignalR not delivering messages,

Access the Azure Portal.->Navigate to your SignalR Service instance.

Select Diagnose and solve problems.

Investigate any reported outages, throttling incidents, or system errors.

In the Azure Monitor, go to Alerts.

Your alert rule indicates that System Errors are occurring.

Review the detailed error messages to identify the root cause.

Within your SignalR Service instance, select Metrics.

Monitor key metrics such as Server Connections, Message Count, and Errors.

If Application Insights is configured, examine the logs for any anomalies.

Confirm that the server maintains a stable connection to the SignalR service.

Ensure clients are successfully connecting and receiving messages.

For setups utilizing Serverless mode, verify that the associated functions or services are operational.

If employing Azure Active Directory (AD) or JSON Web Tokens (JWT) for authentication, check for expired tokens or altered permissions.

Dispatch a basic test message,

await hubContext.Clients.All.SendAsync("ReceiveMessage", "Test Message");

If this message is received, potential issues may include client-side filtering or message serialization problems.

Restart both the SignalR Service and your associated web application or backend services.

If recent updates were applied, consider reverting to a prior stable version to determine if the update introduced the issue.

troubleshooting Azure SignalR Service issues.
https://learn.microsoft.com/en-us/answers/questions/1691669/azure-signalr-service-(serverless)-stopped-working

If further assistance is required, please provide additional details about the errors encountered or any recent changes to your system configuration.
Shree Hima Bindu Maganti 3,825 Reputation points Microsoft External Staff

2025-02-17T14:53:23.86+00:00

Hi @zigzagcloud

Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.
Shree Hima Bindu Maganti 3,825 Reputation points Microsoft External Staff

2025-02-20T06:53:36.9466667+00:00

Hi @zigzagcloud

Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.

Answer 1

Hi @zigzagcloud
Resolving Issues Relating to Message Delivery with Azure SignalR Service

Inspect SignalR Logs Through Azure Monitor

Navigate to Azure Monitor and then go to Logs and search SignalRServiceDiagnosticLogs.

Look for failed connections and authentication logs alongside dropped messages.

Keep track of the Azure SignalR logs

SignalR has limits for connection per account, messages sent, and requests made at the same time.

Check the SignalR service and go to Scale to check the usage.

Make sure that the connection string of the application is in alignment with the Azure SignalR instance.

When using Managed Identity, permissions in Azure Role Based Access Control (RBAC) should be validated.

Azure SignalR Explorer can now be acquired in Visual Studio code.

Inspect clients that are connected, hubs that are active, and messages that are sent.

Confirm if tokens are valid and check if they are expired when you are relying on Azure AD / JWT authentication.

Make sure that CORS policies permit SignalR connections from different origins.

Authenticate SignalR Azure with safeguards in place

Use JavaScript to carry out a simple initial test:Resolving Issues Relating to Message Delivery with Azure SignalR Service

connection = new signalR.HubConnectionBuilder()
    .withUrl("https://<your-signalr-endpoint>/chatHub")
    .build();
connection.start().then(() => console.log("Connected!"));
connection.on("ReceiveMessage", (message) => console.log(message));

troubleshooting Azure SignalR Service issues. https://learn.microsoft.com/en-us/answers/questions/1691669/azure-signalr-service-(serverless)-stopped-working
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Share via

SignalR is not delivering message

1 answer

Your answer