Z
Z2w ago

puppeteer is failed to start

I had a working browser automation script and from last week it's not working so I created a new script using this guide https://www.windmill.dev/docs/advanced/browser_automation (bun puppteer version) and still it's not working Auto scroll took 30929ms mem peak: 79.43MB job=01936cc7-1afe-a29e-9f85-4833187ffc6d tag=chromium worker=wk-reports-gtcmt-PBOSW hostname=windmill-workers-reports-55475b9c7c-gtcmt --- BUN INSTALL --- bun install v1.1.34 (5e5e7c60) Resolving dependencies Resolved, downloaded and extracted [0] Saved lockfile + puppeteer-core@23.9.0 90 packages installed [57.00ms] --- BUN CODE EXECUTION --- 11 | export class PuppeteerError extends Error { 12 | /** 13 | * @internal 14 | */ 15 | constructor(message, options) { 16 | super(message, options); ^ TimeoutError: Timed out after waiting 30000ms at new PuppeteerError (/tmp/bun/node_modules/puppeteer-core/lib/esm/puppeteer/common/Errors.js:16:9) at new TimeoutError (1:23) at /tmp/bun/node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:237:19 at /tmp/bun/node_modules/puppeteer-core/lib/esm/third_party/rxjs/rxjs.js:1936:31 at /tmp/bun/node_modules/puppeteer-core/lib/esm/third_party/rxjs/rxjs.js:993:9 at /tmp/bun/node_modules/puppeteer-core/lib/esm/third_party/rxjs/rxjs.js:696:12 at /tmp/bun/node_modules/puppeteer-core/lib/esm/third_party/rxjs/rxjs.js:2280:20 at /tmp/bun/node_modules/puppeteer-core/lib/esm/third_party/rxjs/rxjs.js:1360:12 at /tmp/bun/node_modules/puppeteer-core/lib/esm/third_party/rxjs/rxjs.js:1349:22
this is the failing line const browser = await puppeteer.launch({ headless: "new", executablePath: "/usr/bin/chromium", args: ["--no-sandbox"], });
Browser automation | Windmill
Windmill makes it easy to perform browser automation tasks, such as testing or web scraping.
2 Replies
Hugo
Hugo2w ago
Hi, please use these args instead: args: ['--single-process', '--no-zygote', '--no-sandbox'], we will update the docs
Z
ZOP2w ago
thank you so much for your help 🙏 it worked