Failed to download Chromium r515411 #1597
Comments
@gp5251 This might just be an intermittent network issue. Does this happen consistently? |
@paambaati I also encountered the same situation. |
使用国内Chromium源 # // > https://npm.taobao.org/mirrors
# // export PUPPETEER_DOWNLOAD_HOST=https://npm.taobao.org/mirrors
# // set PUPPETEER_DOWNLOAD_HOST=https://npm.taobao.org/mirrors
npm config set puppeteer_download_host=https://npm.taobao.org/mirrors
npm i puppeteer 或者用淘宝的cnpm 安装,自动使用国内源 npm install -g cnpm --registry=https://registry.npm.taobao.org
cnpm i puppeteer 还可以手动下载Chromium文件,解压后放在本地
|
@vc1 problem resolved, 3q. |
We're using a private nexus repository. Could I interchange the googleapis.com url, with our own direct route? Are there any other request related attributes we need to take care off? |
@p0psicles there's |
Yes I figured it out eventually. I do think it would help if this would be added to the documentation. Now you need to search through a number of issues or go through the code yourself. |
@p0psicles I'll be happy to review a PR! |
I tried the above method, But it did not work
How can I resolve it?
I do not know if this error was caused by a manual installation。 |
It looks like there's a something that prevents pptr from network access. If there's a proxy, you can set it up with env variables.
@kiki882727 you're trying to run an old chromium. If you're using pptr 1.0.0, try running Chrome Canary instead. |
Any progress? |
It doesn't work with any solutions on my mac.
|
@aslushnikov thanks for your help, I tried anther version of puppeter -- 0.13.0, It worked very well. I will upgrades it in the feature, But not now, thank you again for your help |
Same problem. Solved w/ 0.13.0 build. |
Tried it again with 1.0.0 and it did work. No idea why. |
Error: Download failed: server returned code 407. URL: https://storage.googleapis.com/chromium-browser-snapshots/Win_x64/526987/chrome-win32.zip Downloaded the file from https://storage.googleapis.com/chromium-browser-snapshots/Win_x64/526987/chrome-win32.zip Made sure it is downloadale from below location from a local webserver set this in .npmrc Did the trick for me; a quick workaround if some one needs |
I had an issue installing puppeteer on Mac OS (10.10), and also a permissions issue with mkdir for some reason. This solved it. |
it works @vc1 |
@vc1 Niubi, good job. |
I think this was the case with me. I tried it a second time and it work. Running: node v8.11.2 and npm 5.6.0 at the time, if that matters. |
works fine. |
Thanks, it's work. |
Thank you! Working!! |
I *think* the reason downloading mocha-headless-chrome failed previously was an intermittent network thing? based on puppeteer/puppeteer#1597 (comment) at least. if this still doesn't work there are other workarounds
I had this issue as well when installing puppeteer on Cloud Functions for Firebase. This was the specific error:
I was using I just retried it a couple of times and eventually it would install correctly. Not really a fix but it may indicate it was just trying to install it on a malfunctioning serverless instance or something. |
@JaapWeijland I'm getting the same error you are when installing puppeteer function Firebase Functions (
Sometime it's a other error
I was using |
I came across an problem like below when i tried to run npm i puppeteer, is there any solution?
puppeteer@0.13.0 install /Users/guipeng/Desktop/ldl/puppeteer/node_modules/puppeteer
node install.js
ERROR: Failed to download Chromium r515411! Set "PUPPETEER_SKIP_CHROMIUM_DOWNLOAD" env variable to skip download.
{ Error: read ETIMEDOUT
at _errnoException (util.js:1041:11)
at TLSWrap.onread (net.js:606:25) code: 'ETIMEDOUT', errno: 'ETIMEDOUT', syscall: 'read' }
npm WARN enoent ENOENT: no such file or directory, open '/Users/guipeng/Desktop/ldl/puppeteer/package.json'
The text was updated successfully, but these errors were encountered: