Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download fails with HTTP=403 (Yarn, Node-Gyp, Mac, Node 7.10) #87

Open
swernerx opened this issue May 23, 2017 · 28 comments
Open

Download fails with HTTP=403 (Yarn, Node-Gyp, Mac, Node 7.10) #87

swernerx opened this issue May 23, 2017 · 28 comments

Comments

@swernerx
Copy link

It seems that right now there is some issues downloading binaries for this package. This is the error I got over the last 30 minutes (retried a few times):

node-pre-gyp info using node-pre-gyp@0.6.34
node-pre-gyp info using node@7.10.0 | darwin | x64
node-pre-gyp info check checked for "/Users/Sebastian/Workspace/sebastian-software/edgestack/node_modules/node-zopfli/lib/binding/node-v51-darwin-x64/zopfli.node" (not found)
node-pre-gyp http GET https://node-zopfli.s3.amazonaws.com/Release/zopfli-v1.4.0-node-v51-darwin-x64.tar.gz
node-pre-gyp http 403 https://node-zopfli.s3.amazonaws.com/Release/zopfli-v1.4.0-node-v51-darwin-x64.tar.gz
node-pre-gyp ERR! Tried to download(403): https://node-zopfli.s3.amazonaws.com/Release/zopfli-v1.4.0-node-v51-darwin-x64.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for node-zopfli@1.4.0 and node@7.10.0 (node-v51 ABI) (falling back to source compile with node-gyp) 
node-pre-gyp http 403 status code downloading tarball https://node-zopfli.s3.amazonaws.com/Release/zopfli-v1.4.0-node-v51-darwin-x64.tar.gz 
  • node --version: v7.10.0
  • yarn --version: 0.24.5
  • npm --version: 4.6.1

Hopefully someone has an idea where this is coming from. Thanks a lot!

@swernerx swernerx changed the title Download fails with HTTP=403 (Yarn, Node-Gyp, Mac, Node ) Download fails with HTTP=403 (Yarn, Node-Gyp, Mac, Node 7.10) May 23, 2017
@mtmr0x
Copy link

mtmr0x commented May 24, 2017

Same here, the URL is responding access denied. Check: https://node-zopfli.s3.amazonaws.com/Release/zopfli-v2.0.2-node-v51-linux-x64.tar.gz

@umens
Copy link

umens commented Jun 19, 2017

same here for https://node-zopfli.s3.amazonaws.com/Release/zopfli-v2.0.2-node-v57-darwin-x64.tar.gz
node 8.1.2
npm 5.0.3

@iamstarkov
Copy link

hi, @pierreinglebert, can you publish a package with included binaries? like node-zopfli-prebuilt

@thasmo
Copy link

thasmo commented Jun 25, 2017

😢

@CalvinLeeC7E
Copy link

node-pre-gyp http 403 status code downloading tarball https://node-zopfli.s3.amazonaws.com/Release/zopfli-v2.0.2-node-v57-linux-x64.tar.gz

@ghost
Copy link

ghost commented Aug 5, 2017

The same today, please fix this.

@carlosjgp
Copy link

@leosuncin
Copy link

You can compile from source instead of downlad prebuild binary

npm install --build-from-source node-zopfli

I tested on:
Arch Linux 4.11.12-1-MANJARO
node 8.2.1
npm 5.3.0

@Kamill90
Copy link

nope, still the same.
How may i solve it?

@chrisLovesCode
Copy link

chrisLovesCode commented Jan 25, 2018

Same here - 403 when downloading the Widnows File

$ npm install

node-zopfli@2.0.2 install c:\ReactQL-MongoDB\node_modules\node-zopfli
node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(403): https://node-zopfli.s3.amazonaws.com/R
elease/zopfli-v2.0.2-node-v57-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for node-zopfli@2.0.2 and node@8.
9.2 (node-v57 ABI) (falling back to source compile with node-gyp)

@chrisLovesCode
Copy link

@leosuncin

same problem on windows

npm install --build-from-source node-zopfli
results in a 403 folr the windows file like i have descripted

@leosuncin
Copy link

I don't know what to say. It works on my machine, maybe a missing build dependency is the problem.
asciicast

@thasmo
Copy link

thasmo commented Feb 16, 2018

@leosuncin The issue is about the linked binary not being accessible. The fallback is building the binary locally, which fails for some - but I guess that's not what this issue is about.

@thasmo
Copy link

thasmo commented Feb 16, 2018

@pierreinglebert Is this repo still maintained?

@corydeppen
Copy link

Seems like another case of "tough luck Windows users, works on my Mac". Amazing how many repos reference this or similar issues and there doesn't seem to be any true answer after a year or so. It's really unfortunate that developing modern web apps on Windows is such a disaster most of the time.

@insistandinsist
Copy link

@corydeppen I had the same issue on Mac.This issue may be because of python.If your python version is below 2.7.13,try to update it,it works to me.

@lishichao1002
Copy link

lishichao1002 commented Jun 11, 2018

same question

image

@wuwb
Copy link

wuwb commented Jun 19, 2018

solved by npm i --no-optional

@slimlime
Copy link

Still getting these issues

@DominicBoettger
Copy link

DominicBoettger commented Aug 21, 2018

Works with npm install --build-from-source node-zopfli

But this project does not seem to be maintained anymore and is just barely tested on windows.

@studentIvan
Copy link

Seems bruce-one/node-zopfli works well, try it

@matthiasg
Copy link

When using npm i --build-from-source it works for me. I wonder why this is, since not having binaries should automatically trigger a build from source anyway,

@zgramana
Copy link

zgramana commented Feb 11, 2019

I can't speak for everyone, but on my macOS 14 machine, the npm i auto-build fails when the compiler cannot find the source for lodepng:

../src/png/zopflipng.cc:5:10: fatal error: 'lodepng/lodepng.h' file not foundled to exec install script

Running npm i --build-from-source, however, does not have this problem and succeeds.

NOTE: The fix for #88 definitely looks promising, but in my case node-zopfli was coming in as a transitive dep (via shrink-ray) and so I couldn't fix via that workaround. The final resolution for me was to switch to shrink-ray-current which uses node-zopfli-es instead (which itself does not use node-pre-gyp).

@matthiasg
Copy link

Btw I switched to @gfx/zopfli for now which is not quite as fast but does not have these issues with compilation.

@sanchapereira
Copy link

How come this still happens once in a while?

@pierreinglebert
Copy link
Owner

I published a new version that uses the awesome tool prebuild to serve precompiled binaries to all node version (8-12) and on all OS (win32/win64,linux,osx).

@IvannKurchenko
Copy link

Any updates on this, please? I very appreciate all the answers, but non of them unfortunately does not work for me. npm version 6.7.0, Windows 10.

@pierreinglebert
Copy link
Owner

Which version are you using ?
2.1.3 should work fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests