Brennan

Closing as this is the wrong repo.

Looks like you're hitting a redis exception >Exception thrown: 'StackExchange.Redis.RedisTimeoutException' in StackExchange.Redis.StrongName.dll Exception thrown: 'StackExchange.Redis.RedisConnectionException' in StackExchange.Redis.StrongName.dll Is your redis server up and accessible from the app?

> I tested and I can confirm that class which contained the signalHub member was being initialized before SignalR was configured to UseSqlServer. (global.asax Application_Start executes before the Startup.Configuration), therefore...

Reopening to investigate making this work regardless of order (although I don't think we'll be able to do this) or update documenation.

As stated in the [README](https://github.com/SignalR/SignalR#aspnet-signalr) > There will be no new features added to this product. We are in maintenance mode and only fixing critical issues. See [our blog post](https://devblogs.microsoft.com/aspnet/the-future-of-asp-net-signalr/)...

> multiple http post calls to /signalr/poll are very slow and can take upto to 2 minutes to complete This is normal, poll requests wait 110 seconds if the server...

> On the other hand I have completed a .net profiler trace. I see several GET requests for /signal/connect lasting more than 62 seconds. Does this makes sense? The connect...

Without a minimal repro we are going to close this issue. Feel free to reopen if you can provide more details.

It probably isn't possible to use the .NET Framework client in WASM. There was some work that had to be done in the ASP.NET Core .NET client to make it...

> SignalR should use existing auth cookie and don't create a new one. Isn't it your app that's creating the cookie? SignalR doesn't create cookies for you so something in...