Lissy93 / web-check

🕵️‍♂️ All-in-one OSINT tool for analysing any website
https://web-check.xyz
MIT License
22.6k stars 1.74k forks source link

Unable to Locate Chromium #108

Open ricardodomingues10 opened 8 months ago

ricardodomingues10 commented 8 months ago

I tried this command: docker run -p 3000:3000 lissy93/web-check, and encountered this problem.

Error details tech-stack: Could not find Chromium (rev. 1095492). This can occur if either:

  1. you did not perform an installation before running the script (e.g. npm install) or
  2. your cache path is incorrectly configured (which is: /root/.cache/puppeteer). For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.

Can you help me?

m4teh commented 6 months ago

Defining CHROME_PATH=/usr/bin/chromium also doesn't work. Despite this being the location in the published Debian docker image.

Error00101 commented 3 months ago

Had the same issue. @m4teh Defining the 'CHROME_PATH' does not work as it is already defined inside the container (just run env inside the container -> you will see it is defined)

however I dug through some of the sourcecode. ( -> API -> tech-stack -> wappalyzer(v6.10) ->puppeteer) puppeteer has some documentation where I found a few Interesting thing: PUPPETEER_CACHE_DIR -> nope PUPPETEER_EXECUTABLE_PATH -> YES this is it (Somewhere through the chain the CHROME_PATH gets lost and now replaced with nothing - didnt look where but semms to be solvable)

Screenshots of it not working/Working with the coresponding Compose files not working :( ![grafik](https://github.com/user-attachments/assets/95735c24-18d4-444f-a375-a2bfb98c54d0) now working :) ![grafik](https://github.com/user-attachments/assets/a9df5a2f-65d5-456c-b63c-bee433e08fae)

TLDR: Set the env -> PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium

If i get my hands on some time I will debug this.

b1nary-b0b commented 1 month ago

Thx for thw workaround, unfortunately it does not work for me :( I still get the same error