Search:

It seems that in your client's environment, there is something interfering with the WebSocket upgrade requests.

Hi Ike,

This is strange, from the log you collected so far, it seems that the client send the we upgrade request bur receive a 404 error.
On the server side, it seems that the WebSocket upgrade...

Hi Ike,

In the log, there is no trace of the WebSocket protocol upgrade requests, neither successful nor any errors.
It's possible that there is an intermediary between your client and the server...

Hi Ike,

With the server log settings suggested in a previous post you should find these logs pertaining to a client session successfully bound to a websocket transport

26-Oct-23...

Hi Ike,

Unfortunately, switching to version 5.1.8 and enabling client-side DEBUG logging did not change the situation and did not help us understand the reason for the 404 error on the WS upgrade...