Get stuck when sending a message, timeout error despite of a connected session

[AKhateeb]

Hi,

I have a working instance of the recent release of this repo (pulled container from Docker Hub). Yesterday at 2:00 PM GMT, the container started getting issues. When I tried to restart it, and after fully connecting the session (or reloading it from the cache), the following error was noticed (the container seems crashed)

> wwebjs-api@1.0.0 start
> node server.js

{"level":30,"time":1771567413205,"pid":20,"hostname":"cd3038ae44b9","msg":"Server running on port 3000"}
{"level":30,"time":1771567413206,"pid":20,"hostname":"cd3038ae44b9","msg":"Starting all sessions"}
{"level":40,"time":1771567413207,"pid":20,"hostname":"cd3038ae44b9","sessionId":"support2","msg":"Existing session detected"}
{"level":30,"time":1771567413208,"pid":20,"hostname":"cd3038ae44b9","sessionId":"support2","msg":"Session is being initiated"}
{"level":40,"time":1771567413209,"pid":20,"hostname":"cd3038ae44b9","sessionId":"support2","msg":"Browser lock file exists, removing"}
{"level":30,"time":1771567431815,"pid":20,"hostname":"cd3038ae44b9","sessionId":"support2","msg":"Destroying session"}
{"level":30,"time":1771567450347,"pid":20,"hostname":"cd3038ae44b9","sessionId":"support","msg":"Session is being initiated"}
/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:103
    #error = new Errors_js_1.ProtocolError();
             ^

ProtocolError: Protocol error (Network.getResponseBody): No data found for resource with given identifier
    at <instance_members_initializer> (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:103:14)
    at new Callback (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:107:16)
    at CallbackRegistry.create (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/common/CallbackRegistry.js:25:26)
    at Connection._rawSend (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/Connection.js:108:26)
    at CdpCDPSession.send (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/CdpSession.js:74:33)
    at /usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/cdp/HTTPResponse.js:99:65
    at async CdpHTTPResponse.text (/usr/src/app/node_modules/puppeteer-core/lib/cjs/puppeteer/api/HTTPResponse.js:39:25)
    at async /usr/src/app/node_modules/whatsapp-web.js/src/Client.js:868:39

Node.js v22.22.0
npm notice
npm notice New major version of npm available! 10.9.4 -> 11.10.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.10.1
npm notice To update run: npm install -g npm@11.10.1
npm notice

I tried old versions, clean sessions, increased memory, etc., all in vain. The container is still not working (my node version used is v22, I even tried v20, but with no luck)

Can anyone please help me!

[avoylenko]

Run the instance with headless mode disabled and see what happens there.

[AKhateeb]

@avoylenko Thanks for your suggestion. Unfortunately, the same issue still exists

I added these to env (as I'm running this repo by Docker on a remote Linux server)

PUPPETEER_ARGS=--no-sandbox,--disable-setuid-sandbox,--disable-dev-shm-usage,--disable-gpu,--no-zygote,--single-process

I have these variables commented to let it use the defaults: #WEB_VERSION, WEB_VERSION_CACHE_TYPE

I don't know WHY IT SUDDENLY STOPPED yesterday at 2:00 PM (GMT), is there a quick fix I can do to recover it (all restart/reset/re-fetch) attempts ended up with no result

[AKhateeb]

It worked fine on another server. I'm curious to know why this puppeteer issue appears with no reason

[AKhateeb]

After two days, nothing changed on the server; it stopped sending again.

The weird thing is that it returns session CONNECTED and when I send a message through the API and then request a screenshot using {{baseUrl}}/session/getPageScreenshot/:sessionId I can see the message is set on the right person but with "pending" icon as if there is no connection to send it, I'm sure something changed from whatsapp recently.

@avoylenko you may kindly check it in your free time if it matters. I'm not sure if I'm the only one to face this issue