whatsapp-api icon indicating copy to clipboard operation
whatsapp-api copied to clipboard

Session dissonects after docker restart

Open t0mer opened this issue 1 year ago • 6 comments

Hi, I'm using the docker version of your amazing work. It's been a while since i used it and now, after the first run everything works but when I restart the container is stops working and the following error appears in the logs:

Server running on port 3000
existing session detected tklein
/usr/src/app/node_modules/whatsapp-web.js/src/webCache/LocalWebCache.js:34
        const version = indexHtml.match(/manifest-([\d\\.]+)\.json/)[1];
                                                                    ^

TypeError: Cannot read properties of null (reading '1')
    at LocalWebCache.persist (/usr/src/app/node_modules/whatsapp-web.js/src/webCache/LocalWebCache.js:34:69)
    at /usr/src/app/node_modules/whatsapp-web.js/src/Client.js:771:36
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v20.11.1

I have permissions to the sessions folder and it seems that all files are there and have write permissions.

Thanks

t0mer avatar Mar 10 '24 14:03 t0mer

Ya same issues here ! @t0mer did you find any sol?

This is the same issue without docker, if i restart the server

Initialize error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'push')
    at fillModuleArray (eval at <anonymous> (:2:5), <anonymous>:6:74)
    at moduleRaid (eval at <anonymous> (:2:5), <anonymous>:15:3)
    at __puppeteer_evaluation_script__:4:17

gamingflexer avatar Mar 14 '24 11:03 gamingflexer

Ya same issues here ! @t0mer did you find any sol?

This is the same issue without docker, if i restart the server

Initialize error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'push')
    at fillModuleArray (eval at <anonymous> (:2:5), <anonymous>:6:74)
    at moduleRaid (eval at <anonymous> (:2:5), <anonymous>:15:3)
    at __puppeteer_evaluation_script__:4:17

Not yet. What I did find, and it's strange, is that it happens for specific accounts. I have 3 different WhatsApp accounts; two are working without any issues, and one is not (with the same deployment of the container).

t0mer avatar Mar 14 '24 16:03 t0mer

Yeah, i will ping back if i get any updates.

gamingflexer avatar Mar 15 '24 05:03 gamingflexer

This is related to this issue whatsapp-web.js #2789

arktnld avatar Mar 29 '24 15:03 arktnld

facing the same issue.. any solution?

roo12312 avatar Apr 02 '24 17:04 roo12312

facing the same issue.. any solution?

Try this #190

arktnld avatar Apr 04 '24 12:04 arktnld