Your issue might be the same as the one I encountered. The reason is that StatelessConnectHandlerComponent.CachedClientID was not correctly assigned during the handshake, but this problem does not occur with IpNetDriver. Firstly, in the case of WebSocket communication mode, StatelessConnectHandlerComponent is not needed because the WebSocket layer can handle the handshake itself. Therefore, you can disable the initialization of PacketHandler during startup by using the -NoPacketHandler option.