.local-chromium: No such file or directory

[Jam0r85]

I've provisioned a new server on Hetzner (Ubuntu 22.04) through Forge and when trying to install using the guide I get the following error -

chmod: cannot access '/usr/lib/node_modules/puppeteer/.local-chromium': No such file or directory

I've looked in this folder and the only files/folders present are

I can't find any reference to this error elsewhere. Even tried creating a new server with different hardware and I have the same issue.

Installed chromium directly and it's located at '/snap/bin/chromium' but even when setting the path to this I still get corrupted files.

Everything works fine locally so it must be a server issue.

Any ideas?

[aleksandertabor]

Install Puppeteer v17:
sudo npm install -g puppeteer@17 --unsafe-perm=true

Higher versions don't work.

[Yiddishe-Kop]

This fixed it for me.

But v17 isn't supported anymore. From looking in to this - the issue seems to be a misconfigured cache path, which since puppeteer v19 was changed to ~/.cache/puppeteer (source).

Maybe this package should be updated to support this 🤷‍♂️.

[sammyaxe]

did you manage to solve this?

[hyphen81]

also wondering if you were able to get this working without reverting to v17?

[richpeers]

bump

[AndresReyesDev]

To anyone having this problem, fix it in forge by upgrading puppeteer from version 17 to the latest version (21 at the time), then use this command to get the chrome version specific to this version of puppeteer

npx @puppeteer/browsers install chrome@121.0.6167.85

When it finishes installing chrome it will give the path that you can use in your Laravel project using the parameter:

Browsershot::html('Foo')
  ->setChromePath("/path/to/my/chrome")

Note, you need NodeJS 20 to use the latest version of Puppeteer.

Important info:
Puppeteer Chromium Support
Google: How can I get Chrome for Testing binaries?
Browsershot Requirements
If you use Forge and want to upgrade NodeJS:
Forge Cookbook