-
-
Notifications
You must be signed in to change notification settings - Fork 671
Open
Description
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?
Legacy (Normal)
What type of host account are you experiencing this issue on?
Business account
Mode
My own code
Current Behavior
I have implemented my code and recently I have seen when I start server many time open-wa is not able to start it stuck or fails at Authenticating. And this had happened past 2 months.
error
- Authenticate to continue
0|nest-app | ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
0|nest-app | at Callback.<instance_members_initializer> (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/common/CallbackRegistry.ts:125:12)
0|nest-app | at new Callback (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/common/CallbackRegistry.ts:130:3)
0|nest-app | at CallbackRegistry.create (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/common/CallbackRegistry.ts:28:22)
0|nest-app | at Connection._rawSend (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/Connection.ts:129:22)
0|nest-app | at CdpCDPSession.send (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/CDPSession.ts:98:29)
0|nest-app | at ExecutionContext.#evaluate (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/ExecutionContext.ts:417:44)
0|nest-app | at ExecutionContext.evaluateHandle (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/ExecutionContext.ts:351:32)
0|nest-app | at IsolatedWorld.evaluateHandle (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/IsolatedWorld.ts:175:26)
0|nest-app | at CdpJSHandle.evaluateHandle (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/api/JSHandle.ts:94:29)
0|nest-app | at WaitTask.rerun (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/common/WaitTask.ts:153:41)
0|nest-app | Error while terminating browser PID. You can just ignore this, as the process has most likely been terminated successfully already: kill ESRCH
0|nest-app | Error creating WhatsApp client: ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
0|nest-app | at Callback.<instance_members_initializer> (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/common/CallbackRegistry.ts:125:12)
0|nest-app | at new Callback (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/common/CallbackRegistry.ts:130:3)
0|nest-app | at CallbackRegistry.create (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/common/CallbackRegistry.ts:28:22)
0|nest-app | at Connection._rawSend (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/Connection.ts:129:22)
0|nest-app | at CdpCDPSession.send (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/CDPSession.ts:98:29)
0|nest-app | at ExecutionContext.#evaluate (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/ExecutionContext.ts:417:44)
0|nest-app | at ExecutionContext.evaluateHandle (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/ExecutionContext.ts:351:32)
0|nest-app | at IsolatedWorld.evaluateHandle (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/cdp/IsolatedWorld.ts:175:26)
0|nest-app | at CdpJSHandle.evaluateHandle (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/api/JSHandle.ts:94:29)
0|nest-app | at WaitTask.rerun (/home/ec2-user/whatsapp-message-analyser/node_modules/puppeteer-core/src/common/WaitTask.ts:153:41)
Expected Behavior
Earlier when we start suddenly it start the server.
Steps To Reproduce
Run on ec2
Config
{
sessionId: 'whatsapp-session',
authTimeout: 0,
blockCrashLogs: false,
disableSpins: true,
headless: true,
logConsole: false,
logFile: false,
deleteSessionDataOnLogout: true,
qrTimeout: 0,
popup: true,
useChrome: true,
sessionDataPath: './whatsapp-session',
restartOnCrash: this.setClient.bind(this),
}
const client = await wa.create(this.config);
create() code OR full CLI command + CONFIG
DEBUG INFO
{
"WA_VERSION": "2.3000.1032410020",
"WA_AUTOMATE_VERSION": "4.76.0",
"BROWSER_VERSION": "Chrome/144.0.7559.96",
"START_TS": 1769231860373,
"RAM_INFO": "Total: 2.01 GB | Free: 1.49 GB",
"PPTR_VERSION": "23.11.1",
"LATEST_VERSION": true,
"CLI": false
}Environment
- OS: Linux 6.1
- Node: 24.13.0
- npm: 11.6.2Screenshots/Logs
No response
Anything else?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels