SignalR Upgrade to Redis Backplane fails with Send Loop Error

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Describe the bug

.net 8.0 SignalR application hosted on IIS, behind HAProxy with the JS client set to websockets.

Without `AddStackExchangeRedis(`, connection succeeds and client is able to post a quick message through SignalR to the server.

Adding `AddStackExchangeRedis(`, with a connection string and detailed logging.
Logs show "Redis Connected"

Below are the errors from clients attempting to connect.

Chrome returns a 1011 Error from the socket.

Tests I've tried to isolate this more.

Removed Redis Sentinel and set to a single Redis Server. Same Error as above.
Removed Redis and restarted the iis app and pool, connection succeeds.
Granted Redis user full Redis access. `ACL SETUSER ********* +@all`

This could 100% be a me issue, I'm just struggling to find out where the error is after spending a day on this and stuck in the overall try/catch loop in the redis code not knowing what could cause this. Any help would be appreciated in tracking down this error.

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version

8.0.0

### Anything else?

_No response_