-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TimeoutError: waiting for target failed: timeout 30000ms exceeded #110
Comments
Try giving the headless argument to your chrome/chromium. |
Hi,I use the following parameters:
But it still throws the same error. |
The puppeteer-stream code overrides the headless launch option here I believe the chrome extension needs the browser to launch with a "GUI" it to record the page. await launch({
...
args: [
...
'--headless=new',
...
],
... |
I have the same problem and also receive the error |
Having the same issue. Any updates? |
I am able to run it headless with this configuration: const browser = await launch({
executablePath: '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome',
defaultViewport: {
width: 1920,
height: 1080,
},
args: [
'--no-sandbox',
'--headless=new',
],
}); |
I'm getting the same error. I don't need it to be headless, so I ran it in headful. The page loads successfully, but nothing else happens and the timeout error occurs. |
Hello, I am running the following script on a linux OS:
But it always throws the following exception:
timeout 30000ms exceeded
In order to be able to locate the problem, I added a log to the
waitForTarget
method innode_modules/puppeteer-core/lib/cjs/puppeteer/common/Browser.js
CODE:
The exception information is as follows:
Version:
node:v16.14.0
npm:8.3.1
os:Linux version 3.10.0-1160.66.1.el7.x86_64
puppeteer:19.2.2
puppeteer-stream:3.0.3
chrome:linux-1056772
Hope to get your help,Thanks!
The text was updated successfully, but these errors were encountered: