Definitely not a whatticket issue but where to add the --no-sandbox to run all of this

When using: <div class="snippet-clipboard-content notranslate position-relative ov

[Help] Running as root without --no-sandbox is not supported. about whaticket-community HOT 5 CLOSED

canove commented on July 22, 2024

[Help] Running as root without --no-sandbox is not supported.

from whaticket-community.

Comments (5)

canove commented on July 22, 2024 4

The right decision is to run WhaTicket without root. But there is a workaround, by editing a file in WWebJS lib:

Edit node_modules/whatsapp-web.js/src/util/Constants.js , adding this args:

ps.: It's not recommended, since every update you will need to make this changes again.

from whaticket-community.

luizoseas commented on July 22, 2024 2

run the command with another account other than root

from whaticket-community.

deepesh-agarwal commented on July 22, 2024 1

This https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#setting-up-chrome-linux-sandbox fixes the issue.

from whaticket-community.

deepesh-agarwal commented on July 22, 2024

When using:

sudo -u www-data bash
www-data@srv1:/root$ cd /var/www/whaticket/backend
www-data@srv1:~/whaticket/backend$ npm start

The error is now:

[nodemon] starting `node src/app.js`
Server started on port: 8080
(node:10078) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
[0829/030733.634647:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround                             , you can try using --no-sandbox.

from whaticket-community.