[BUG] message.upsert events stop about baileys HOT 6 CLOSED

same issue

from baileys.

I'm facing the same problem. I also use a custom authentication method (fork of useMultiFileAuthState | redis db).

I'm considering this to be the problem and also the use of poll messages, I use it as a substitute for interactive messages, decrypting each poll message update.

Did you find a solution for this problem?

from baileys.

Did you find the reason? I have the same problem

from baileys.

No success with it yet.

Right now I'm restarting all the sockets every 30 minutes, and restarting the node process every 4 hours. Would be really cool if this wasn't needed, but for now it's working.

Also tested on my local machine for a day with one phone number connected, and without restarting anything, and it worked fine. After that day tried this again, and the connections were gone after about 45 minutes... I don't what is causing this, our devops engineer guessed it could be something with the IP address, maybe with fix IP it would be ok (we're using Baileys with multiple socket connections on an express.js server with Kubernetes).

We haven't got time to investigate it further yet, but if I have something useful I will report back.

from baileys.

Add this option in makeWASocket:

makeWASocket({
   ...,
   defaultQueryTimeoutMs: undefined // add this
})

from baileys.

Tracking issue in #34

from baileys.