Protoo server problem on Debian 11

Hello

A few months ago I posted an issue here: Since updating from Debian 9 to Debian 11 there is a problem that crashes after 10 hours or 20 hours · Issue #28 · versatica/protoo · GitHub and was told to come here

Here are the issues I’ve seen since I upgraded from Debian 9 to Debian 11:

protoo connection request [peerId:, address:/?roomId=5b88wt1cw5l&peerId=marc1&t=1646861451977, room:%s]
existing room stat 5b88wt1cw5l marc1 {
  peer: 1,
  transport: 110,
  transports: [
    { consumer: 0 }, { consumer: 0 }, { consumer: 0 }, { consumer: 0 },
    { consumer: 0 }, { consumer: 0 }, { consumer: 0 }, { consumer: 0 },
    { consumer: 0 }, { consumer: 0 }, { consumer: 0 }, { consumer: 0 },
    { consumer: 0 }, { consumer: 0 }, { consumer: 0 }, { producer: 0 },
    { producer: 0 }, { producer: 0 }, { producer: 1 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 1 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 1 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 1 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 1 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    ... 10 more items
  ]
}
request:getRouterRtpCapabilities
request:getRouterRtpCapabilities
request:createWebRtcTransport
request:createWebRtcTransport
request:join
protoo connection request [peerId:, address:/?roomId=6vk27vce76c&peerId=Taminya_&t=1646868789950, room:%s]
handleProtooConnection() | there is already a protoo Peer with same peerId, closing it [peerId:Taminya_]
protoo Peer "close" event [peerId:Taminya_]
existing room stat 6vk27vce76c Taminya_ {
  peer: 2,
  transport: 110,
  transports: [
    { consumer: 0 }, { consumer: 0 }, { consumer: 0 }, { consumer: 0 },
    { consumer: 0 }, { consumer: 0 }, { consumer: 0 }, { consumer: 0 },
    { consumer: 0 }, { consumer: 0 }, { consumer: 0 }, { consumer: 0 },
    { consumer: 0 }, { consumer: 0 }, { consumer: 0 }, { producer: 0 },
    { producer: 0 }, { producer: 0 }, { producer: 1 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 1 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 1 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 1 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 0 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    { producer: 1 }, { consumer: 0 }, { producer: 0 }, { consumer: 0 },
    ... 10 more items
  ]
}
/home/debian/node/mediasoup/meething-mediasoup/node_modules/protoo-server/lib/Peer.js:161
                                        pReject(new Error('peer closed'));
                                                ^

Error: peer closed
    at Object.close (/home/debian/node/mediasoup/meething-mediasoup/node_modules/protoo-server/lib/Peer.js:161:14)
    at Peer.close (/home/debian/node/mediasoup/meething-mediasoup/node_modules/protoo-server/lib/Peer.js:103:9)
    at ConfRoom.handlePeerConnect (/home/debian/node/mediasoup/meething-mediasoup/lib/Room.js:41:20)
    at WebSocketServer.<anonymous> (/home/debian/node/mediasoup/meething-mediasoup/main.js:90:11)
    at WebSocketServer.emit (node:events:520:28)
    at WebSocketServer._onRequest (/home/debian/node/mediasoup/meething-mediasoup/node_modules/protoo-server/lib/transports/WebSocketServer.js:89:9)
    at WebSocketServer.<anonymous> (/home/debian/node/mediasoup/meething-mediasoup/node_modules/protoo-server/lib/transports/WebSocketServer.js:37:50)
    at WebSocketServer.emit (node:events:520:28)
    at WebSocketServer.handleUpgrade (/home/debian/node/mediasoup/meething-mediasoup/node_modules/websocket/lib/WebSocketServer.js:224:14)
    at Server.emit (node:events:520:28)
[nodemon] app crashed - waiting for file changes before starting...

there are sometimes errors which are always related to the websocket of protoo-server

the errors are always related to the websocket of protoo-server, is protoo-server not suitable for Debian 11?

The problem is not Debian 11.
The problem comes from the fact that the application works well under node 14 but not on node 16 - More info on request timeout · Issue #13 · meething/meething-mediasoup · GitHub