lighthouse Https problem
See original GitHub issueHello to everyone!
Lighthouse version: 4.0.0 Google Chrome version: 71 Node.js version: 8.9.0
I’m running lighthouse in CMD. I did “npm install lighthouse” and then “lighthouse “url””. When I run lighthouse on http sites, everything is ok, but as soon as I try to run it on https lighthouse starts running and then I’m getting this:
events.js:183
throw er; // Unhandled 'error' event
Error: read ECONNRESET
at _errnoException <util.js:1024:11>
at TCP.onread <net.js:615:25>
I installed ionic and ws as well, but nothing helped. I’ll be happy, if someone can help with it. thanks in advance.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Test lighthouse on website with invalid certificate fails #7292
The following possibilities instruct Chrome to ignore certificate errors and resolve www.lemonde.fr to IP 62.210.77.17. Note that the server ...
Read more >HTTPS Mixed Content Lighthouse Error - WordPress.org
I am getting an insecure request when I run my page through Lighthouse. The link is for an image http://www.clarkmortgages.ca/wp-content/uploads/image.jpg, ...
Read more >Why is the Lighthouse API sometimes unable to successfully ...
This indicates that there was a problem when the Lighthouse API tried to render the page. This can be due to a number...
Read more >Does not use HTTPS - Chrome Developers
Lighthouse waits for an event from the Chrome Remote Debugging Protocol indicating that the page is running on a secure connection. If the...
Read more >Google lighthouse audit report throws error ... - Stack Overflow
Google lighthouse audit report throws error: Lighthouse was unable to reliably load the page that you requested. (Status code: 404).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Huh, well that was almost too easy 😎
Adding this to my
.travis.yml
fixed it:I didn’t know something changed with the protocol method. Thanks @patrickhulce! 🎉
I’m having a very similar problem for my lighthouse-badges project. It occurred for the first time once I upgraded to lighthouse version
4.0.0
.Basically I test via TravisCI that
lighthouse-badges
produces an.svg
-image and anhtml
-report based on thelighthouse
CLI output.TravisCI runs this command:
/home/travis/build/emazzotta/lighthouse-badges/node_modules/.bin/lighthouse --chrome-flags='--headless --no-sandbox --no-default-browser-check --no-first-run --disable-default-apps' --output=json --output-path=stdout --quiet http://127.0.0.1:8080
and fails with this error:
http://127.0.0.1:8080 is a node server which I start ad-hoc before running the test. Previously I was running the test on https://google.com but I changed to aforementioned local server hoping it would fix the issue, however both fail.
This is actually the commit which broke the build: https://github.com/emazzotta/lighthouse-badges/commit/1d1a7a9148459807142597e55c72192b4deff2dd As you can see, I just upgraded from
4.0.0-alpha.2-3.2.1
to4.0.0
Note that running the same command which Travis runs in CI (
yarn system-test:full-run
) works fine locally. I’m not sure what could be the problem in CI. (Yay, “works on my machine”-issue we meet again)Here’s a link to the latest failing build, in this case I’m trying again to hit https://gooogle.com: https://travis-ci.org/emazzotta/lighthouse-badges/builds/485939498
Any hints are greatly appreciated. 👍