puppeteer: Failed to download Chromium r536395! Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download.

sudo npm install -g puppeteer --unsafe-perm=true --allow-root

Solves the issue to me.

Same issue on Ubuntu

Getting the same issue on MacOS

Please try (on windows 10) on powershell $env:PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=0 then run npm install -g puppeteer --unsafe-perm=true --allow-root

Your problem should get solved.

For windows 10 export NODE_TLS_REJECT_UNAUTHORIZED=0 && npm install it works for me

The best way is to export default env var PUPPETEER_SKIP_CHROMIUM_DOWNLOAD

PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true yarn add puppeteer or PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true npm install puppeteer

Same issue on Windows. Would be nice if Puppeteer respected strict-ssl options. Can’t get out from behind our firewall. I’ve tried using a local install of chromium but then ran into issues with runaway processes.

edit: I can get everything to work locally if I use the release which Puppeteer tries to download. Go to https://storage.googleapis.com/chromium-browser-snapshots/Win_x64/YOUR_RELEASE_HERE/chrome-win32.zip, replace your operating system with the correct one found on line 31 of https://github.com/GoogleChrome/puppeteer/blob/master/lib/BrowserFetcher.js and put it in your project root. Use the executablePath option in the API to point Puppeteer to the chrome executable in the files you just downloaded like so: const browser = await puppeteer.launch({executablePath: './chrome-win32/chrome.exe'});

This gets around my problems with the UNABLE_TO_GET_ISSUER_CERT_LOCALLY flag being set by npm. I really think Puppeteer should respect the strict-ssl flag in .npmrc though.

I’m on Ubuntu bash on windows and try to install glyphhanger

root@PC-006:~# sudo npm install -g glyphhanger
/usr/bin/glyphhanger -> /usr/lib/node_modules/glyphhanger/cmd.js

> puppeteer@1.5.0 install /usr/lib/node_modules/glyphhanger/node_modules/puppeteer
> node install.js

ERROR: Failed to download Chromium r564778! Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download.
{ Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/glyphhanger/node_modules/puppeteer/.local-chromium'
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/usr/lib/node_modules/glyphhanger/node_modules/puppeteer/.local-chromium' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! puppeteer@1.5.0 install: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the puppeteer@1.5.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-06-12T21_08_14_997Z-debug.log

Best Simplest Solution set the variable as true in local and proceed. PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true yarn it works

@xamgore solution worked for me

same questions, i use sudo cnpm install -g puppeteer --unsafe-perm=true --allow-root

same Problem as @bardware here:

/usr/bin/npm install --g penthouse

> puppeteer@1.5.0 install /usr/lib/node_modules/penthouse/node_modules/puppeteer
> node install.js

ERROR: Failed to download Chromium r564778! Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download.
{ Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/penthouse/node_modules/puppeteer/.local-chromium'
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: '/usr/lib/node_modules/penthouse/node_modules/puppeteer/.local-chromium' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! puppeteer@1.5.0 install: `node install.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the puppeteer@1.5.0 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-06-18T08_58_27_069Z-debug.log

Same here. Unless I set the NODE_TLS_REJECT_UNAUTHORIZED variable as zero separately before running npm install, it won’t work. Puppeteer’s download system does not seem to honor strict-ssl or NODE_TLS_REJECT_UNAUTHORIZED in the .npmrc file, so my build system is stuck on this because there’s no way for Node to set environment variables in a pre-install step for Puppeteer. Sucks big time.

Possibly “off topic” but worthy of a note: It seems, for me, that using “-unsafe-perm=true --allow-root” works for a number of otherwise “broken” NPM packages. I have likely lost count of the number of packages that show “Error: EACCES: permission denied”. Anyway: Very true for Fedora 30 in this case attempting to install “puppeteer” = “chromium” with NPM 6.5.0

@aslushnikov this is closed but I am still encountering this 5 years later with latest versions of puppeteer (that are transitive dependencies, not even direct dependencies of my project).

It seems wrong to set puppeteer-specific environment vars in my project when I am not even using it (like PUPPETEER_SKIP_DOWNLOAD).

Seems to me this should be reopened?

And what’s the autorative solution to this issue? - no workarround.

你可能使用了VPN，退出就好了。

sudo npm install -g puppeteer --unsafe-perm=true --allow-root

Solves the issue to me. @xamgore Absolute genius! Thanks man you were a life saver