unlighthouse: Unlighthouse stuck at "Waiting for routes..." screen
Describe the bug
unlighthouse dashboard does not load any data, and no error message at all is ever displayed, when using on a Linux distribution with Chromium installed. The default browser on this machine is Firefox.
The problem happens regardless of the website scanned.
unlighthouse-puppeteer behaves exactly the same way.
How to reproduce
- Run
unlighthouseas instructed in the documentation:
npx unlighthouse --site https://my-website.com
- Confirm the npx prompt to install required package.
Observed result
- In the command line, messages confirm the successful connection to the website with status
200, the eventual detection of a sitemap, and number of routes initially discovered. - In the command line, a deprecation warning is displayed:
Puppeteer old Headless deprecation warning:
In the near feature `headless: true` will default to the new Headless mode
for Chrome instead of the old Headless implementation. For more
information, please see https://developer.chrome.com/articles/new-headless/.
Consider opting in early by passing `headless: "new"` to `puppeteer.launch()`
If you encounter any bugs, please report them to https://github.com/puppeteer/puppeteer/issues/new/choose.
- A tab open in the default web browser and loads unlighthouse dashboard
- The dashboard stays empty with
Waiting for routes...spinner displayed. Worker progress value remains at 0%, even minutes after the launch.
Expected result
- In the command line, messages confirm the successful connection to the website with status
200, the eventual detection of a sitemap, and number of routes initially discovered. - A tab open in the default web browser and loads unlighthouse dashboard
- The dashboard content gets populated progressively as the crawling progresses.
Reproduction
c.f. bug description
System / Nuxt Info
System:
OS: Linux 4.19 BunsenLabs GNU/Linux 10.5 (Lithium)
CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
Memory: 9.83 GB / 15.35 GB
Container: Yes
Shell: 5.0.3 - /bin/bash
Binaries:
Node: 16.19.1 - ~/.nvm/versions/node/v16.19.1/bin/node
npm: 8.19.3 - ~/.nvm/versions/node/v16.19.1/bin/npm
Browsers:
Chromium: 90.0.4430.212
Firefox: 112.0.2
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 9
- Comments: 23 (6 by maintainers)
Thanks for the follow-up. Here is the debug log output:
Still happens to me with ⛵ Unlighthouse cli @ v0.10.6
nothing else happens.
Time remaining is stuck on 5 secs.
Maybe an option to specify browser to use? Chromium is commonly installed on Ubuntu, but yet it seems that Unlighthouse fails without Chrome installed.