Patrick Hulce

Thanks for filing @catdad! Yeah this SGTM 👍

@hekod777 rendertron is using an older version of chrome-launcher (~0.3 instead of latest 0.8) which has a few mitigations that might help (though it looks like you've already tried increasing...

Ah yeah, thanks for the ping here, we'll fix that up 👍

Thanks for filing @Stanzilla! Just to be clear Chrome should *always* open to `about:blank` before navigating anywhere else when run from the CLI or node. Are you saying that Chrome...

Interesting, can you access Chrome ports if Lighthouse isn't involved at all? i.e. start Chrome manually with a remote debugging port and try to hit its URL something like ```...

Hm, seems like there are intermittent WSL issues with localhost binding https://github.com/microsoft/WSL/issues/4636 maybe try some of the remediation techniques there? > Restarting LxssManager from windows services worked for me. I...

@susannakosic are you able to start and run Chrome on that machine without chrome-launcher/loki involved? as @bendytree said in https://github.com/GoogleChrome/chrome-launcher/issues/6#issuecomment-341491690 this is usually because Chrome crashes or is unable to...

You can use the [proxy command-line flags](https://www.chromium.org/developers/design-documents/network-settings#TOC-Command-line-options-for-proxy-settings) ```js const {launch} = require('chrome-launcher') launch({chromeFlags: ['--proxy-server==[:]']}) ```

@jackwicklow1 yes you will need to replace the components of `--proxy-server==[:]` with scheme, uri, and port as necessary according to the linked Chromium documentation. > I also need to authenticate...

You definitely don't want to launch Chrome on the same port as your web server. I'm not sure what nginx and reverse proxy setup has to do with anything. Are...