This repository was archived by the owner on May 7, 2024. It is now read-only.
This repository was archived by the owner on May 7, 2024. It is now read-only.
Unable to connect with SignalR with any available transports. Error 404 "No Connection with that ID" #105
Description
Problem
I have a react website in which I am trying to connect to SignalR hub on my .net core server via ocelot gateway.
I am unable to connect to hub and get a 404 error "No Connection with that ID". I have only one server instance running and no load balancer is involved.
Even though the negotiate call is always successful.
WebSocket and Server Sent Events are not working at all and on Long Polling, 404 is returned.
Network call logs are:
I have added all possible routes for ocelot. I am out of ideas on what to do now.
I have observed that the connectionId returned in response to the negotiate call is not used to connect to hub and instead the connectionToken value is used as the value for "id" query string parameter.
Specifications
- Ocelot Version: 15.0.6
- @microsoft/signalr Version: 5.0.1
- .Net Core: 3.1
- Platform: Windows