Error starting

[dgomp]

Are you using the latest version of the library?

• I have checked and am using the latest version of the library.

What type of session are you experiencing this issue on?

Multi-device and I have set multiDevice to true in my config OR am using the --multi-device flag

What type of host account are you experiencing this issue on?

Personal account (normal)

Mode

EASY API/CLI

Current Behavior

Hi,
I'm having the error below:

ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting
in launch/connect calls for a higher timeout if needed.
    at new Callback (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:61:35)
    at CallbackRegistry.create (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:106:26)
    at Connection._rawSend (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:216:26)
    at CDPSessionImpl.send (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:425:78)
    at ExecutionContext._ExecutionContext_evaluate (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\ExecutionContext.js:240:46)
    at async ExecutionContext.evaluate (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\ExecutionContext.js:146:16)
Browser page has closed. Killing client
Killing client. Shutting Down: PAGE_CLOSED
ERRO: o processo "6776" n�o foi encontrado.
Error while terminating browser PID. You can just ignore this, as the process has most likely been terminated successfully already: kill ESRCH
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting
in launch/connect calls for a higher timeout if needed.
    at new Callback (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-co

Therefore, I updated headless: true, to headless: 'new'.
Now it loads up to "Finalizing client..." and then ...

ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting
in launch/connect calls for a higher timeout if needed.
    at new Callback (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:61:35)
    at CallbackRegistry.create (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:106:26)
    at Connection._rawSend (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:216:26)
    at CDPSessionImpl.send (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\Connection.js:425:78)
    at ExecutionContext._ExecutionContext_evaluate (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\ExecutionContext.js:240:46)
    at async ExecutionContext.evaluate (C:\Users\Administrador\Documents\VS\Whats\node_modules\puppeteer-core\lib\cjs\puppeteer\common\ExecutionContext.js:146:16)

Does anyone know how to resolve?
Tks!

Expected Behavior

I expected it to connect.

Steps To Reproduce

Just node .

create() code OR full CLI command + CONFIG

No response

DEBUG INFO

{
  "WA_VERSION": "2.2331.7",
  "WA_AUTOMATE_VERSION": "4.66.3",
  "BROWSER_VERSION": "HeadlessChrome/112.0.5614.0",
  "START_TS": 1690464042562,
  "RAM_INFO": "Total: 8.56 GB | Free: 3.59 GB",
  "PPTR_VERSION": "19.11.1",
  "LATEST_VERSION": true,
  "CLI": false
}

Environment

- OS: Windows Server 2016
- Node: 18.15.0
- npm: 9.5.0

Screenshots/Logs

.

Anything else?

No response