Showing "lighthouse is warming up" forever
See original GitHub issueMaintainer’s Note:
tl;dr - This happens when Chromium fails to fetch the Lighthouse code from the web. Check your network connectivity, ensure there are no proxies that would prevent you from downloading code from a Google server, and try again.
On Brave, you’ll have to enable the Remote Debugging
option under brave://settings/privacy
(thx @bsclifton!)
Original Issue:
When running lighthouse on Chromium “75.0.3770.90” to audit www.google.com it is showing the message “lightouse is warming up” forever. Since 2019-07-30. It used to worked in the very exact setup before. Probably, infrastructure to run lighthouse is unavailable.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:35
- Comments:105 (5 by maintainers)
Top Results From Across the Web
Showing "lighthouse is warming up" forever - Stack Overflow
When I click on Generate report on Chrome's Audit tab in DevTools, it is showing the message lighthouse is warming up forever.
Read more >Chrome Devtools lighthouse doesn't work : r/brave_browser
The Lighthouse feature of the Audits panel doesn't work. ... click on the button to start an audit, it hangs showing "Lighthouse is...
Read more >845410 - Audit stuck in "Lighthouse is warming up" on Linux ...
3. Select all the audit checkboxes. 4. Click Run audit. 5. The dialog box will stuck and will display a message 'Lighthouse is...
Read more >Showing "lighthouse is warming up" forever - Bountysource
tl;dr - This happens when Chromium fails to fetch the Lighthouse code from the web. Check your network connectivity, ensure there are no ......
Read more >Lighthouse Audit stuck on "Auditing your web page …"
Same on Windows. Opera is stuck on "lighthouse is warming up...". message. Opera Version: 52.0.2871.40; OS: Win 10 64 ...
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
@avimehenwal to get this working on Brave, you’ll have to enable the
Remote Debugging
option under brave://settings/privacyHi folks - Brave developer here 😄
For Brave, this is a known issue that was captured with https://github.com/brave/brave-browser/issues/3199. We had disabled remote debugging because it was making outbound calls
I recently resolved this in Brave by adding a new
Enable Remote Debugging
toggle in brave://settings/privacy. Once you turn this on, it’ll work again 😄The fix is only in version 1.2 and greater (current stable version is 1.1.23; 1.2 is expected to hit Stable on Jan 6).Fix is here for those curious: https://github.com/brave/brave-core/pull/4044