[BUG] Sockt closes after 1-2 hours, requiring Node.js service restart

[mohamed-2010]

Describe the issue: I am using Baileys to connect via WebSocket, but I've noticed that the connection closes after approximately one or two hours of being active. I need to restart my Node.js service to reconnect the socket.

Steps to reproduce:

1. Start the WebSocket connection using Baileys.
2. Leave it running for one to two hours.
3. After some time, the connection is closed without error.
4. Restarting the Node.js service reconnects the socket, but the issue happens again after a similar duration.

Expected behavior: The WebSocket should remain open indefinitely or reconnect automatically without requiring a full service restart.

Additional context:

• Node.js version: 16.9.0
• Baileys version: latest

I would appreciate any insights or suggestions on how to resolve this issue. Are there any built-in reconnection strategies or configurations to prevent frequent disconnections?

Thank you in advance for your help.

[Skidy89]

implement an automatic restart every 30 min

[Skidy89]

or simply use the logger debug to see whats happening