/home/sistahid/wa.sistah.id/controller/waController.js:29 await client.on('qr', (qr) => {\ ^ SyntaxError: Invalid or unexpected token at wrapSafe (internal/modules/cjs/loader.js:1001:16) at Module._compile (internal/modules/cjs/loader.js:1049:27) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:101:18) at Object. (/home/sistahid/wa.sistah.id/router/wa.js:2:48) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) /home/sistahid/wa.sistah.id/controller/waController.js:29 await client.on('qr', (qr) => {\ ^ SyntaxError: Invalid or unexpected token at wrapSafe (internal/modules/cjs/loader.js:1001:16) at Module._compile (internal/modules/cjs/loader.js:1049:27) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:101:18) at Object. (/home/sistahid/wa.sistah.id/router/wa.js:2:48) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) /home/sistahid/wa.sistah.id/controller/waController.js:29 await client.on('qr', (qr) => {\ ^ SyntaxError: Invalid or unexpected token at wrapSafe (internal/modules/cjs/loader.js:1001:16) at Module._compile (internal/modules/cjs/loader.js:1049:27) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:101:18) at Object. (/home/sistahid/wa.sistah.id/router/wa.js:2:48) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) /home/sistahid/wa.sistah.id/controller/waController.js:29 await client.on('qr', (qr) => {\ ^ SyntaxError: Invalid or unexpected token at wrapSafe (internal/modules/cjs/loader.js:1001:16) at Module._compile (internal/modules/cjs/loader.js:1049:27) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:101:18) at Object. (/home/sistahid/wa.sistah.id/router/wa.js:2:48) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) /home/sistahid/wa.sistah.id/controller/waController.js:29 await client.on('qr', (qr) => {\ ^ SyntaxError: Invalid or unexpected token at wrapSafe (internal/modules/cjs/loader.js:1001:16) at Module._compile (internal/modules/cjs/loader.js:1049:27) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:101:18) at Object. (/home/sistahid/wa.sistah.id/router/wa.js:2:48) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) /home/sistahid/wa.sistah.id/controller/waController.js:29 await client.on('qr', (qr) => {\ ^ SyntaxError: Invalid or unexpected token at wrapSafe (internal/modules/cjs/loader.js:1001:16) at Module._compile (internal/modules/cjs/loader.js:1049:27) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) at Module.load (internal/modules/cjs/loader.js:950:32) at Function.Module._load (internal/modules/cjs/loader.js:790:12) at Module.require (internal/modules/cjs/loader.js:974:19) at require (internal/modules/cjs/helpers.js:101:18) at Object. (/home/sistahid/wa.sistah.id/router/wa.js:2:48) at Module._compile (internal/modules/cjs/loader.js:1085:14) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) (node:3338) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! [0714/154117.241322:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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. #0 0x55fa80510b89 base::debug::CollectStackTrace() #1 0x55fa80475433 base::debug::StackTrace::StackTrace() #2 0x55fa80488330 logging::LogMessage::~LogMessage() #3 0x55fa7e46d99b content::ZygoteHostImpl::Init() #4 0x55fa8001e372 content::ContentMainRunnerImpl::Initialize() #5 0x55fa8001c439 content::RunContentProcess() #6 0x55fa8001c58e content::ContentMain() #7 0x55fa80077d7a headless::(anonymous namespace)::RunContentMain() #8 0x55fa80077a85 headless::HeadlessShellMain() #9 0x55fa7cadb3e8 ChromeMain #10 0x7fd3a240c555 __libc_start_main #11 0x55fa7cadb22a _start TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md at onClose (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20) at Interface. (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68) at Interface.emit (events.js:412:35) at Interface.close (readline.js:530:8) at Socket.onend (readline.js:254:10) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `node --trace-warnings ...` to show where the warning was created) (node:3338) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:3338) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:3338) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'evaluate' of null at Client.getNumberId (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/whatsapp-web.js/src/Client.js:1153:35) at Client.isRegisteredUser (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/whatsapp-web.js/src/Client.js:1139:35) at sendMessage (/home/sistahid/wa.sistah.id/controller/waController.js:148:31) at Layer.handle [as handle_request] (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/layer.js:95:5) at next (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/route.js:144:13) at Route.dispatch (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/route.js:114:3) at Layer.handle [as handle_request] (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/layer.js:95:5) at /home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:284:15 at Function.process_params (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:346:12) at next (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:280:10) at Function.handle (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:175:3) at router (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:47:12) at Layer.handle [as handle_request] (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:328:13) at /home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:286:9 at Function.process_params (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:346:12) (node:3338) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) (node:8741) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! [0714/154427.936279:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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. #0 0x5617697afb89 base::debug::CollectStackTrace() #1 0x561769714433 base::debug::StackTrace::StackTrace() #2 0x561769727330 logging::LogMessage::~LogMessage() #3 0x56176770c99b content::ZygoteHostImpl::Init() #4 0x5617692bd372 content::ContentMainRunnerImpl::Initialize() #5 0x5617692bb439 content::RunContentProcess() #6 0x5617692bb58e content::ContentMain() #7 0x561769316d7a headless::(anonymous namespace)::RunContentMain() #8 0x561769316a85 headless::HeadlessShellMain() #9 0x561765d7a3e8 ChromeMain #10 0x7fd75e0e5555 __libc_start_main #11 0x561765d7a22a _start TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md at onClose (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20) at Interface. (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68) at Interface.emit (events.js:412:35) at Interface.close (readline.js:530:8) at Socket.onend (readline.js:254:10) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `node --trace-warnings ...` to show where the warning was created) (node:8741) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:8741) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:8741) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'evaluate' of null at Client.getNumberId (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/whatsapp-web.js/src/Client.js:1153:35) at Client.isRegisteredUser (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/whatsapp-web.js/src/Client.js:1139:35) at sendMessage (/home/sistahid/wa.sistah.id/controller/waController.js:148:31) at Layer.handle [as handle_request] (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/layer.js:95:5) at next (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/route.js:144:13) at Route.dispatch (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/route.js:114:3) at Layer.handle [as handle_request] (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/layer.js:95:5) at /home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:284:15 at Function.process_params (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:346:12) at next (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:280:10) at Function.handle (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:175:3) at router (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:47:12) at Layer.handle [as handle_request] (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:328:13) at /home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:286:9 at Function.process_params (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/express/lib/router/index.js:346:12) (node:8741) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) (node:2220) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! [0714/155654.722341:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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. #0 0x5601beac0b89 base::debug::CollectStackTrace() #1 0x5601bea25433 base::debug::StackTrace::StackTrace() #2 0x5601bea38330 logging::LogMessage::~LogMessage() #3 0x5601bca1d99b content::ZygoteHostImpl::Init() #4 0x5601be5ce372 content::ContentMainRunnerImpl::Initialize() #5 0x5601be5cc439 content::RunContentProcess() #6 0x5601be5cc58e content::ContentMain() #7 0x5601be627d7a headless::(anonymous namespace)::RunContentMain() #8 0x5601be627a85 headless::HeadlessShellMain() #9 0x5601bb08b3e8 ChromeMain #10 0x7f288b8e0555 __libc_start_main #11 0x5601bb08b22a _start TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md at onClose (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20) at Interface. (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68) at Interface.emit (events.js:412:35) at Interface.close (readline.js:530:8) at Socket.onend (readline.js:254:10) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `node --trace-warnings ...` to show where the warning was created) (node:2220) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:2220) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:3014) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! [0714/155709.760002:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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. #0 0x55762c225b89 base::debug::CollectStackTrace() #1 0x55762c18a433 base::debug::StackTrace::StackTrace() #2 0x55762c19d330 logging::LogMessage::~LogMessage() #3 0x55762a18299b content::ZygoteHostImpl::Init() #4 0x55762bd33372 content::ContentMainRunnerImpl::Initialize() #5 0x55762bd31439 content::RunContentProcess() #6 0x55762bd3158e content::ContentMain() #7 0x55762bd8cd7a headless::(anonymous namespace)::RunContentMain() #8 0x55762bd8ca85 headless::HeadlessShellMain() #9 0x5576287f03e8 ChromeMain #10 0x7f42358ac555 __libc_start_main #11 0x5576287f022a _start TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md at onClose (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20) at Interface. (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68) at Interface.emit (events.js:412:35) at Interface.close (readline.js:530:8) at Socket.onend (readline.js:254:10) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `node --trace-warnings ...` to show where the warning was created) (node:3014) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:3014) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:3881) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! [0714/155754.638576:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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. #0 0x561869704b89 base::debug::CollectStackTrace() #1 0x561869669433 base::debug::StackTrace::StackTrace() #2 0x56186967c330 logging::LogMessage::~LogMessage() #3 0x56186766199b content::ZygoteHostImpl::Init() #4 0x561869212372 content::ContentMainRunnerImpl::Initialize() #5 0x561869210439 content::RunContentProcess() #6 0x56186921058e content::ContentMain() #7 0x56186926bd7a headless::(anonymous namespace)::RunContentMain() #8 0x56186926ba85 headless::HeadlessShellMain() #9 0x561865ccf3e8 ChromeMain #10 0x7f871f9a0555 __libc_start_main #11 0x561865ccf22a _start TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md at onClose (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20) at Interface. (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68) at Interface.emit (events.js:412:35) at Interface.close (readline.js:530:8) at Socket.onend (readline.js:254:10) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `node --trace-warnings ...` to show where the warning was created) (node:3881) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:3881) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:3978) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! [0714/155759.123105:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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. #0 0x558d9d430b89 base::debug::CollectStackTrace() #1 0x558d9d395433 base::debug::StackTrace::StackTrace() #2 0x558d9d3a8330 logging::LogMessage::~LogMessage() #3 0x558d9b38d99b content::ZygoteHostImpl::Init() #4 0x558d9cf3e372 content::ContentMainRunnerImpl::Initialize() #5 0x558d9cf3c439 content::RunContentProcess() #6 0x558d9cf3c58e content::ContentMain() #7 0x558d9cf97d7a headless::(anonymous namespace)::RunContentMain() #8 0x558d9cf97a85 headless::HeadlessShellMain() #9 0x558d999fb3e8 ChromeMain #10 0x7fded11fc555 __libc_start_main #11 0x558d999fb22a _start TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md at onClose (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20) at Interface. (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68) at Interface.emit (events.js:412:35) at Interface.close (readline.js:530:8) at Socket.onend (readline.js:254:10) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `node --trace-warnings ...` to show where the warning was created) (node:3978) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:3978) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:4162) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! [0714/155803.755055:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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. #0 0x56344bd3db89 base::debug::CollectStackTrace() #1 0x56344bca2433 base::debug::StackTrace::StackTrace() #2 0x56344bcb5330 logging::LogMessage::~LogMessage() #3 0x563449c9a99b content::ZygoteHostImpl::Init() #4 0x56344b84b372 content::ContentMainRunnerImpl::Initialize() #5 0x56344b849439 content::RunContentProcess() #6 0x56344b84958e content::ContentMain() #7 0x56344b8a4d7a headless::(anonymous namespace)::RunContentMain() #8 0x56344b8a4a85 headless::HeadlessShellMain() #9 0x5634483083e8 ChromeMain #10 0x7ff5be794555 __libc_start_main #11 0x56344830822a _start TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md at onClose (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20) at Interface. (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68) at Interface.emit (events.js:412:35) at Interface.close (readline.js:530:8) at Socket.onend (readline.js:254:10) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `node --trace-warnings ...` to show where the warning was created) (node:4162) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:4162) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:6701) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! [0714/155917.498351:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/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. #0 0x55cd1e854b89 base::debug::CollectStackTrace() #1 0x55cd1e7b9433 base::debug::StackTrace::StackTrace() #2 0x55cd1e7cc330 logging::LogMessage::~LogMessage() #3 0x55cd1c7b199b content::ZygoteHostImpl::Init() #4 0x55cd1e362372 content::ContentMainRunnerImpl::Initialize() #5 0x55cd1e360439 content::RunContentProcess() #6 0x55cd1e36058e content::ContentMain() #7 0x55cd1e3bbd7a headless::(anonymous namespace)::RunContentMain() #8 0x55cd1e3bba85 headless::HeadlessShellMain() #9 0x55cd1ae1f3e8 ChromeMain #10 0x7f6c08cde555 __libc_start_main #11 0x55cd1ae1f22a _start TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md at onClose (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241:20) at Interface. (/home/sistahid/nodevenv/wa.sistah.id/14/lib/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:231:68) at Interface.emit (events.js:412:35) at Interface.close (readline.js:530:8) at Socket.onend (readline.js:254:10) at Socket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `node --trace-warnings ...` to show where the warning was created) (node:6701) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:6701) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.