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

This error is throw:ERR_HTTP2_PROTOCOL_ERROR after that execution is stopped. #15701

Closed
2 tasks done
Mohit1011519 opened this issue Dec 18, 2023 · 1 comment
Closed
2 tasks done

Comments

@Mohit1011519
Copy link

FAQ

URL

https://www.directv.com/

What happened?

Uploading Screenshot from 2023-12-18 15-16-25.png…
we are not able to run 1 user 5 sessions every time with this url, also not running a single instance.

What did you expect?

we are runnig lighthouse test on this url.

What have you tried?

No response

How were you running Lighthouse?

node

Lighthouse Version

v11.4.0

Chrome Version

chrome-117

Node Version

v18.16.1

OS

linux

Relevant log output

LH:status Connecting to browser +644ms
  LH:status Navigating to about:blank +5ms
  LH:status Benchmarking machine +8ms
  LH:status Preparing target for navigation mode +1s
  LH:status Navigating to about:blank +15ms
  LH:status Preparing target for navigation +7ms
  LH:status Cleaning origin data +3ms
  LH:status Cleaning browser cache +2ms
  LH:status Preparing network conditions +10ms
  LH:status Navigating to https://www.directv.com/ +36ms
  LH:status Getting artifact: DevtoolsLog +30s
  LH:status Getting artifact: Trace +0ms
  LH:NavigationRunner:error Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Details: net::ERR_HTTP2_PROTOCOL_ERROR) https://www.directv.com/ +0ms
  LH:status Analyzing and running audits... +6ms
  LH:status Auditing: Uses HTTPS +0ms
  LH:Runner:warn devtoolsLogs gatherer, required by audit is-on-https, did not run. +0ms
  LH:status Auditing: Registers a service worker that controls page and `start_url` +1ms
  LH:Runner:warn ServiceWorker gatherer, required by audit service-worker, did not run. +0ms
  LH:status Auditing: Has a `<meta name="viewport">` tag with `width` or `initial-scale` +0ms
  LH:Runner:warn MetaElements gatherer, required by audit viewport, did not run. +0ms
  LH:status Auditing: First Contentful Paint +1ms
  LH:Runner:warn traces gatherer, required by audit first-contentful-paint, did not run. +0ms
  LH:status Auditing: Largest Contentful Paint +0ms
  LH:Runner:warn traces gatherer, required by audit largest-contentful-paint, did not run. +0ms
  LH:status Auditing: First Meaningful Paint +0ms
  LH:Runner:warn traces gatherer, required by audit first-meaningful-paint, did not run. +0ms
  LH:status Auditing: Speed Index +1ms
  LH:Runner:warn traces gatherer, required by audit speed-index, did not run. +0ms
  LH:status Auditing: Screenshot Thumbnails +0ms
  LH:Runner:warn traces gatherer, required by audit screenshot-thumbnails, did not run. +0ms
  LH:status Auditing: Final Screenshot +0ms
  LH:Runner:warn traces gatherer, required by audit final-screenshot, did not run. +0ms
  LH:status Auditing: Total Blocking Time +0ms
  LH:Runner:warn traces gatherer, required by audit total-blocking-time, did not run. +1ms
  LH:status Auditing: Max Potential First Input Delay +0ms
  LH:Runner:warn traces gatherer, required by audit max-potential-fid, did not run. +0ms
  LH:status Auditing: Cumulative Layout Shift +2ms
  LH:Runner:warn traces gatherer, required by audit cumulative-layout-shift, did not run. +0ms
  LH:status Auditing: No browser errors logged to the console +0ms
  LH:Runner:warn ConsoleMessages gatherer, required by audit errors-in-console, did not run. +0ms
  LH:status Auditing: Initial server response time was short +0ms
  LH:Runner:warn devtoolsLogs gatherer, required by audit server-response-time, did not run. +0ms
@adamraine
Copy link
Member

I can't reproduce this, ERR_HTTP2_PROTOCOL_ERROR comes from Chrome and not Lighthouse and can indicate a server side issue.

@adamraine adamraine closed this as not planned Won't fix, can't repro, duplicate, stale Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants