Skip to content
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

Puppeteer getting protocolTimeout #202

Open
AshSimmonds opened this issue Apr 8, 2024 · 4 comments
Open

Puppeteer getting protocolTimeout #202

AshSimmonds opened this issue Apr 8, 2024 · 4 comments

Comments

@AshSimmonds
Copy link

AshSimmonds commented Apr 8, 2024

Describe the bug

file:///usr/local/lib/node_modules/@unlighthouse/cli/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89
    #error = new ProtocolError();
             ^

ProtocolError: Page.enable timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.

I don't know whether it's tripping up on a certain page, the debug log only tells you what page it was working on after success of runLighthouseTask. Not sure if the page itself matters, it keeps getting to about 62% then crapping out.

Reproduction

unlighthouse-ci --site ashsimmonds.com --build-static

System / Nuxt Info

No response

@harlan-zw
Copy link
Owner

Hi, can you please try v0.12.0. It might resolve this issue.

@thidayatullah
Copy link

thidayatullah commented May 7, 2024

@harlan-zw
I'm using v0.12.0 and still have the same problem when running

unlighthouse-ci --site <mysite> --reporter csvExpanded

@robpetrin
Copy link

robpetrin commented May 10, 2024

Can confirm this issue persists in v0.12.1 when using

npx unlighthouse --site [url] --desktop --reporter csvExpanded

harlan-zw added a commit that referenced this issue May 22, 2024
@harlan-zw
Copy link
Owner

You can try v0.12.2 but not sure if it will help exactly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants