Hacker News Reader

Fixes this issue basically: https://github.com/GoogleChrome/lighthouse/issues/6512#:~:te....

Tried all of the proposed solutions and this error still pops up on certain sites and certain configuration settings. Felt totally random when it started happening.

View on HN

Do you have a good record of these sites/configurations? We suspect it's related to the host environment in some way that we can't reproduce on our machines. It'd be useful information for debugging if you can share it. Thanks!

I’ve experienced the same as you, I’ve lost many hours to fixing different protocol time out errors. We’re running it in ECS now and it’s pretty stable, every now and then one pops up but is fixed by retrying the job.

Reply on news.ycombinator.com