Never AUTHENTICATED after Loading your chats went 100% | WWebJS Community | Page 1

onyx orchid Jan 26, 2024, 8:32 PM

#

I'm currently grappling with an issue in a headless Chromium instance running within a Docker container. Upon invoking the initialize() function, the QR event triggers successfully. However, after scanning the QR code, the subsequent MESSAGE events are received:

{"level":"DEBUG","message":"Loading your chats", "timestamp":"2024-01-26T20:22:54.756Z","percentage":0}
{"level":"DEBUG","message":"Loading your chats","timestamp":"2024-01-26T20:22:56.766Z","percentage":100}

Following this, the process goes silent, and no further actions are observed. No authenticated message, nor ready. Has anyone encountered a similar scenario and found a resolution? Your insights and suggestions would be greatly appreciated!

I'm running the latest stable version and running with NoAuth to make sure it's not the auth strategy that is causing this.

sturdy summit Jan 26, 2024, 9:22 PM

#

check to see if you have a folder .wwebjs_cache and clean it, and try to connect again

onyx orchid Jan 26, 2024, 11:11 PM

#

Thanks for the tip @sturdy summit , but it starts a fresh new container every time, so no .wwebjs_cache is present at the time of initialization.

flat laurel Jan 27, 2024, 1:28 AM

#

onyx orchid Thanks for the tip <@493628059715371010> , but it starts a fresh new container e...

Is your code working perfect locally?

onyx orchid Jan 27, 2024, 7:31 AM

#

Yes, correct

onyx orchid Jan 27, 2024, 8:09 PM

#

Digging a bit more into this issue by running Chromium in headful mode in the docker container with a virtual display buffer. The browser gets stuck in this view:

#Never AUTHENTICATED after Loading your chats went 100%