I don't know, it told me to report to the github repository

[OinkiePie]

FAQ

• Yes, my issue is not about variability or throttling.
• Yes, my issue is not about a specific accessibility audit (file with axe-core instead).
• Yes, my issue is not answered by other FAQs.

URL

http://127.0.0.1:5500/commands

What happened?

error

What did you expect?

I expected this to check my site

What have you tried?

check my site

How were you running Lighthouse?

Chrome DevTools

Lighthouse Version

11.3.0

Chrome Version

121.0.0.0

Node Version

20.10.0

OS

windows 10

Relevant log output

INVALID_URL

Channel: DevTools
Initial URL: 
Chrome Version: 121.0.0.0
Stack Trace: LighthouseError: INVALID_URL
    at UrlUtils.normalizeUrl (devtools://devtools/bundled/third_party/lighthouse/lighthouse-dt-bundle.js:252:39542)
    at devtools://devtools/bundled/third_party/lighthouse/lighthouse-dt-bundle.js:449:12402
    at Runner.gather (devtools://devtools/bundled/third_party/lighthouse/lighthouse-dt-bundle.js:446:3581)
    at navigationGather (devtools://devtools/bundled/third_party/lighthouse/lighthouse-dt-bundle.js:449:12373)
    at async navigation (devtools://devtools/bundled/third_party/lighthouse/lighthouse-dt-bundle.js:449:13723)
    at async a (devtools://devtools/bundled/entrypoints/lighthouse_worker/lighthouse_worker.js?remoteBase=https%3A%2F%2Fchrome-devtools-frontend.appspot.com%2Fserve_file%2F%406f54147f20896c29d462c15c7b62fd0d8510cd41%2F:1:2166)
    at async self.onmessage (devtools://devtools/bundled/entrypoints/lighthouse_worker/lighthouse_worker.js?remoteBase=https%3A%2F%2Fchrome-devtools-frontend.appspot.com%2Fserve_file%2F%406f54147f20896c29d462c15c7b62fd0d8510cd41%2F:1:2520)

[connorjclark]

Thanks for the report.

We have some issues here:

1. should be possible to audit localhost in CDT. dont see how this could have failed if it was http://
2. isProtocolAllowed failing and throwing an error should present better than this in CDT - but I can't think of a way to navigate to a page such that the lighthouse panel doesnt already fade out the option to run an audit ( maybe if the page did location.href = 'about:blank' or to a file url ??)

[adamraine]

The report is using M121 but we fixed a major cause of INVALID_URL errors in M123: https://chromiumdash.appspot.com/commit/f1d39232489aa8260d9cd4ca63d6f305838ff55a

It's possible this isn't happening on the latest version of Chrome.