Status 403 from https://github.com/lovell/sharp-libvips/releases/download/...
See original GitHub issueI’m pretty new to Heroku, but I have managed to get the npm install
command to work on my Linux server, Windows machine and my Mac. On Heroku, I get this error when deploying my app:
-----> VIPS app detected
-----> Installing libvips
Downloading libvips and unpacking
libvips installed
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NODE_VERBOSE=false
NODE_ENV=production
NODE_MODULES_CACHE=false
-----> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
Resolving node version 10.x...
Downloading and installing node 10.15.3...
Using default npm version: 6.4.1
-----> Restoring cache
Caching has been disabled because NODE_MODULES_CACHE=false
-----> Installing dependencies
Installing node modules (package.json + package-lock)
> sharp@0.21.0 install /tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.7.0/libvips-8.7.0-linux-x64.tar.gz
/tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/node_modules/sharp/install/libvips.js:80
throw new Error(`Status ${response.statusCode}`);
^
Error: Status 403
at /tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/node_modules/sharp/install/libvips.js:80:17
at f (/tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/node_modules/once/once.js:25:25)
at ClientRequest.protocol.request.res (/tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/node_modules/simple-get/index.js:63:5)
at Object.onceWrapper (events.js:277:13)
at ClientRequest.emit (events.js:189:13)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:556:21)
at HTTPParser.parserOnHeadersComplete (_http_common.js:109:17)
at TLSSocket.socketOnData (_http_client.js:442:20)
at TLSSocket.emit (events.js:189:13)
at addChunk (_stream_readable.js:284:12)
make: Entering directory '/tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/node_modules/sharp/build'
TOUCH Release/obj.target/libvips-cpp.stamp
CXX(target) Release/obj.target/sharp/src/common.o
../src/common.cc:25:22: fatal error: vips/vips8: No such file or directory
compilation terminated.
sharp.target.mk:126: recipe for target 'Release/obj.target/sharp/src/common.o' failed
make: *** [Release/obj.target/sharp/src/common.o] Error 1
make: Leaving directory '/tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/node_modules/sharp/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:189:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.4.0-1038-aws
gyp ERR! command "/tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/.heroku/node/bin/node" "/tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/.heroku/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /tmp/build_de25ad290908a11f95fbe6f4c89bd6e4/node_modules/sharp
gyp ERR! node -v v10.15.3
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sharp@0.21.0 install: `(node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sharp@0.21.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! /tmp/npmcache.Fqauu/_logs/2019-03-28T16_16_10_448Z-debug.log
-----> Change to Node.js build process
Heroku has begun executing the "build" script defined in package.json
during Node.js builds.
Read more: https://devcenter.heroku.com/changelog-items/1573
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:
- Node version not specified in package.json
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
Love,
Heroku
! Push rejected, failed to compile Node.js app.
! Push failed
And as suggested in other issues, I have this buildpack added: https://github.com/alex88/heroku-buildpack-vips.git
. Any suggestions on what the issue might be?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:14
- Comments:40 (6 by maintainers)
Top Results From Across the Web
403 Error while downloading dependency | Bitbucket Cloud
When I try to download that file https://github.com/lovell/sharp-libvips/releases/download/v8.7.4/libvips-8.7.4-linux-x64.tar.gz it works without problem.
Read more >Developers - Status 403 from https://github.com/lovell/sharp-libvips ...
I'm pretty new to Heroku, but I have managed to get the npm install command to work on my Linux server, Windows machine...
Read more >Python version incompatibility in sharp package - GitLab.org
I have sharp package in my package.json, seems like it is python ... https://github.com/lovell/sharp-libvips/releases/download/v8.8.1/ ...
Read more >Gatsby new fails to install the sharp package and breaks
I have it installed, running sudo apt-get install -y libvips-tools confirms it. The problem persists. ` – aviya.developer. Nov 28, 2019 at 11:04....
Read more >Strapi installation fails due to blocked npm/github repo, is ...
info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.10.0/libvips-8.10.0-linux-x64.tar.br
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve contacted GitHub support about this.
A reply from GitHub: