signalR websockets transport failed to connect

Death Head 26 Reputation points
2022-05-16T15:25:47.11+00:00

Hi, I am trying to figure out why websockets is not connecting using signalR on my webserver.

The setup is Windows Server 2019 with IIS 10.

There is another site on the same webserver using signalR that does not have the same issue. What I am looking for is like a punch list of configurations to look at as to why the two sites are working differently. Any insight would be appreciated.

Here is what I am getting when logging is turned on for signalR.

[14:58:07 GMT+0000 (Coordinated Universal Time)] SignalR: webSockets transport starting.
jquery.signalR-2.4.3.min.js:9 [14:58:07 GMT+0000 (Coordinated Universal Time)] SignalR: Connecting to websocket endpoint 'wss://server/website/signalr/connect?transport=webSockets&clientProtocol=2.1&connectionToken=xl%2FXdj3qzjtBUFE87dS2PHU0210aznNUcB90UBxV2eOZSoZG1KCtPNPYVIeMz4nd49BfdOsxzqBT7enZWRJGbwiXHMhef%2BUL7JCADGHyroZNEtpscGZhqSgVqyhLWXKw&connectionData=%5B%7B%22name%22%3A%22messagehub%22%7D%5D&tid=3'.
jquery.signalR-2.4.3.min.js:9 [14:58:07 GMT+0000 (Coordinated Universal Time)] SignalR: Websocket opened.
jquery.signalR-2.4.3.min.js:9 [14:58:12 GMT+0000 (Coordinated Universal Time)] SignalR: webSockets transport timed out when trying to connect.
jquery.signalR-2.4.3.min.js:9 [14:58:12 GMT+0000 (Coordinated Universal Time)] SignalR: Closing the Websocket.
jquery.signalR-2.4.3.min.js:9 [14:58:12 GMT+0000 (Coordinated Universal Time)] SignalR: webSockets transport failed to connect. Attempting to fall back.
jquery.signalR-2.4.3.min.js:9 [14:58:12 GMT+0000 (Coordinated Universal Time)] SignalR: longPolling transport starting.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,178 questions
0 comments No comments
{count} vote