Anton Voylenko
Anton Voylenko
The **RECOVER_SESSIONS** env controls session restart in case of page failures.
@raffus a temporary solution is to set the **RECOVER_SESSIONS** env to false. Need more time to find why the exception is not handled in some cases.
This possibility is missing, but we could implement it in the future service version.
You are right, the mobile app still shows as paired after terminating the session. It seems the issue happens only when the browser runs in headless mode, need to investigate...
See `/client/getClassInfo/{sessionId}` https://github.com/chrishubert/whatsapp-api/blob/1f53776892853f0867c5c392d1614050f032c596/swagger.json#L572
If you still face the issue, feel free to pull the image with updated `whatsapp-web.js` library and other fixes that are missing in this repo: `docker pull avoylenko/wwebjs-api`
Could you pull the latest image and check if this solves your issue.
The maximum allowed body size is controlled by setting the **MAX_ATTACHMENT_SIZE** env. By default the value is set to 10000000 and the value specifies the number of bytes.
Is there anything written to the server log during the crash?
The browser is CPU/memory consuming process and turning off the callback won't change anything. Try to allocate more RAM by cutting the memory allocated to the GPU.