whatsapp-http-api
whatsapp-http-api copied to clipboard
Multiple Issues with Whatsapp-http-api-plus version during creating session
- I tried to create a session (multiple time) but it fails, throwing the below error
TimeoutError: Timed out after 30000 ms while trying to connect to the browser! Only Chrome at revision r982053 is guaranteed to work.
-
After this failure i ran
GET /api/sessions
and the status wasfailed
-
Next i tried to stop the session by calling
/api/sessions/stop
and provided the session nameThis resulted in error as shown below
-
Then tried to
GET /api/sessions
However in logs i am continuously getting QR codes
I am using devlikeapro/whatsapp-http-api-plus
container image to deploy this application on Kubernetes .
Also intermittently i am getting issues like NO QR in /api/screenshot
response
@allburov can you help with the above reported issues , are these known issues with the default engine ? should we try changing the engine or something else to get it working.
I am looking to achieve consistency in establishing a session >> getting QR images >> authenticating session.
@allburov appreciate any guidance on this
Hi! Could you try to POST /logout
for that session and start it again?
I can confirm this bug.
Maybe this bug only happen when list of chats are very long. I confirm this bug happened on a session that have 2000+ open chats and 1000+ unread chats.
Here is some logs:
(node:34) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
(node:34) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGINT listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:34) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGTERM listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(node:34) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 SIGHUP listeners added to [process]. Use emitter.setMaxListeners() to increase limit
Hi! Could you try the recent version, 2026.6.4
? We've fixed the chrome version there and added chats limit query for getting long list of chats
https://waha.devlike.pro/docs/how-to/chats/#get-all-chats