Keep having connection refused or connection timeout to https://signalr-weu-exp-drax-dev-pldnsazr.service.signalr.net

Kim Hwa Khoo (DHL IT Services) 0 Reputation points
2025-12-09T10:20:44.2266667+00:00

Hi,

Our Project keep having connection refused or connection timeout to https://signalr-weu-exp-drax-dev-pldnsazr.service.signalr.net. Could you please help to advise us?

Fore example:

2025-12-09 08:26:06.805 [http-nio-8080-exec-8] INFO c.d.d.w.f.RequestResponseLoggingFilter RT=,T=b8801b5d556b45efb955eefc79e29da6,S=325ea4a122da8749 - Response:{"exception":"org.springframework.web.client.ResourceAccessException: I/O error on PUT request for "https://signalr-weu-exp-drax-dev-pldnsazr.service.signalr.net/api/v1/hubs/drax.KUL/groups/3P1/connections/AiDTQ8S0xvBqNdS1e6qqnQec4YpQd02": Connection refused"}

2025-12-09 09:28:17.794 [http-nio-8080-exec-9] INFO c.d.d.w.f.RequestResponseLoggingFilter RT=,T=7a5c30dd95c74266bb01091a636d6fb9,S=c17f120d268aae4b - Response:{"exception":"org.springframework.web.client.ResourceAccessException: I/O error on PUT request for "https://signalr-weu-exp-drax-dev-pldnsazr.service.signalr.net/api/v1/hubs/drax.NSW/groups/DGE/connections/y37hacROcz3dD50Qi1dfyAQXcJcQd02": Connection timed out"}

Thanks

Kim Hwa

Azure SignalR Service
Azure SignalR Service
An Azure service that is used for adding real-time communications to web applications.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Vimal Lalani 2,560 Reputation points Microsoft External Staff Moderator
    2025-12-12T18:13:58.2133333+00:00

    Hey Kim Hwa Khoo (DHL IT Services),

    I see you're facing connection issues with your Azure SignalR service, specifically "connection refused" and "connection timeout" errors to the specified endpoint. That sounds frustrating! Here are a few steps and suggestions you can try to troubleshoot the problem:

    1. Check for Multiple Device Clients: Make sure that each device has its own identity. If multiple devices are sharing connection strings, they can compete for connections, which might lead to timeouts or dropped connections.
    2. Validate Network Connectivity: Ensure there are no network connectivity issues between your application server and the Azure SignalR service. You might want to check for firewalls or security groups that could be blocking incoming/outgoing connections.
    3. Look at Server Logs: Check your app server logs for any abnormal events or errors that could indicate why the connections are being refused or timing out. Event logs can reveal if there were any recent restarts or failures.
    4. Connection Restart Logic: Implement a reconnect strategy on the client-side. Azure SignalR has a built-in "Always Reconnect" strategy, and you can also add custom reconnection logic to handle dropped connections effectively.
    5. Transport Protocols: SignalR uses various transport protocols (like WebSockets, Server-Sent Events, etc.). Ensure that your server supports WebSocket, and that it is enabled in IIS if you’re using it.
    6. SDK Version: Make sure you are using the latest version of the Azure SignalR SDK. Some issues can be fixed in newer releases.
    7. Diagnostics Tools: Use tools like Fiddler or the browser's developer console to inspect outgoing requests and see if the client is communicating correctly with the service.
    8. SkipNegotiation Flag: If you are using SkipNegotiation, ensure it's set correctly as skipping negotiation might prevent the connection from being established properly.

    Here are some relevant documentation links that can help you further:

    Hope this helps! If the problem persists, feel free to share more details, and we can dig deeper into the issue!

    0 comments No comments

Your answer

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