question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: 403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/osrm/v5.14.3/Release/node-v51-linux-x64.tar.gz

See original GitHub issue

Hi all,

when I try to install it, gives me this error:

npm WARN deprecated @turf/inside@3.14.0: Module has been renamed to @turf/boolean-point-in-polygon

osrm@5.14.3 install /usr/lib/node_modules/osrm-isochrone/node_modules/osrm node-pre-gyp install --fallback-to-build=false || ./scripts/node_install.sh

node-pre-gyp ERR! install error node-pre-gyp ERR! stack Error: 403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/osrm/v5.14.3/Release/node-v51-linux-x64.tar.gz node-pre-gyp ERR! stack at Request.<anonymous> (/usr/lib/node_modules/osrm-isochrone/node_modules/osrm/node_modules/node-pre-gyp/lib/install.js:118:27) node-pre-gyp ERR! stack at emitOne (events.js:101:20) node-pre-gyp ERR! stack at Request.emit (events.js:191:7) node-pre-gyp ERR! stack at Request.onRequestResponse (/usr/lib/node_modules/osrm-isochrone/node_modules/osrm/node_modules/request/request.js:1074:10) node-pre-gyp ERR! stack at emitOne (events.js:96:13) node-pre-gyp ERR! stack at ClientRequest.emit (events.js:191:7) node-pre-gyp ERR! stack at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:522:21) node-pre-gyp ERR! stack at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23) node-pre-gyp ERR! stack at TLSSocket.socketOnData (_http_client.js:411:20) node-pre-gyp ERR! stack at emitOne (events.js:96:13) node-pre-gyp ERR! System Linux 4.4.0-51-generic node-pre-gyp ERR! command “/usr/bin/nodejs” “/usr/lib/node_modules/osrm-isochrone/node_modules/osrm/node_modules/.bin/node-pre-gyp” “install” “–fallback-to-build=false” node-pre-gyp ERR! cwd /usr/lib/node_modules/osrm-isochrone/node_modules/osrm node-pre-gyp ERR! node -v v7.10.1 node-pre-gyp ERR! node-pre-gyp -v v0.6.39 node-pre-gyp ERR! not ok 403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/osrm/v5.14.3/Release/node-v51-linux-x64.tar.gz /usr/lib/node_modules/osrm-isochrone/node_modules/osrm/build /usr/lib/node_modules/osrm-isochrone/node_modules/osrm CMake Error: The source directory “/usr/lib/node_modules/osrm-isochrone/node_modules/osrm” does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. /usr/lib └── (empty)

npm ERR! Linux 4.4.0-51-generic npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “install” “-g” “osrm-isochrone” npm ERR! node v7.10.1 npm ERR! npm v4.2.0 npm ERR! code ELIFECYCLE npm ERR! errno 1

npm ERR! osrm@5.14.3 install: node-pre-gyp install --fallback-to-build=false || ./scripts/node_install.sh npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the osrm@5.14.3 install script ‘node-pre-gyp install --fallback-to-build=false || ./scripts/node_install.sh’. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the osrm package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-pre-gyp install --fallback-to-build=false || ./scripts/node_install.sh npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs osrm npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls osrm npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /root/.npm/_logs/2018-01-05T11_10_07_423Z-debug.log

Do you have any suggestion?

Issue Analytics

  • State:open
  • Created 6 years ago
  • Comments:7

github_iconTop GitHub Comments

3reactions
mvl22commented, Nov 15, 2018

According to https://github.com/Project-OSRM/osrm-backend/issues/4940#issuecomment-371180588:

“We do not yet support NodeJS 9.x, please downgrade to 8.x LTS.”

So switch to Node.js 8:

nvm install 8 && nvm use 8

then retry.

0reactions
xiaogu-spacecommented, Jun 25, 2018

Hi,I can’t install node v6.10.1 npm v3.10.10

like this:

npm WARN deprecated @turf/inside@3.14.0: Module has been renamed to @turf/boolean-point-in-polygon

> osrm@5.18.0 install /Users/xiaogu/Project/dataService/node_modules/osrm
> node-pre-gyp install --fallback-to-build=false || ./scripts/node_install.sh

node-pre-gyp ERR! install error
node-pre-gyp ERR! stack Error: 403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/osrm/v5.18.0/Release/node-v48-darwin-x64.tar.gz
node-pre-gyp ERR! stack     at Request.<anonymous> (/Users/xiaogu/Project/dataService/node_modules/osrm/node_modules/node-pre-gyp/lib/install.js:118:27)
node-pre-gyp ERR! stack     at emitOne (events.js:101:20)
node-pre-gyp ERR! stack     at Request.emit (events.js:188:7)
node-pre-gyp ERR! stack     at Request.onRequestResponse (/Users/xiaogu/Project/dataService/node_modules/osrm/node_modules/request/request.js:1074:10)
node-pre-gyp ERR! stack     at emitOne (events.js:96:13)
node-pre-gyp ERR! stack     at ClientRequest.emit (events.js:188:7)
node-pre-gyp ERR! stack     at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:473:21)
node-pre-gyp ERR! stack     at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
node-pre-gyp ERR! stack     at TLSSocket.socketOnData (_http_client.js:362:20)
node-pre-gyp ERR! stack     at emitOne (events.js:96:13)
node-pre-gyp ERR! System Darwin 17.5.0
node-pre-gyp ERR! command "/usr/local/bin/node" "/Users/xiaogu/Project/dataService/node_modules/osrm/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build=false"
node-pre-gyp ERR! cwd /Users/xiaogu/Project/dataService/node_modules/osrm
node-pre-gyp ERR! node -v v6.10.1
node-pre-gyp ERR! node-pre-gyp -v v0.6.38
node-pre-gyp ERR! not ok
403 status code downloading tarball https://mapbox-node-binary.s3.amazonaws.com/osrm/v5.18.0/Release/node-v48-darwin-x64.tar.gz
Needs cmake to build from source
server@0.0.0 /Users/xiaogu/Project/dataService
└── (empty)

npm WARN Invalid version: "https://registry.npmjs.org/mime-db/-/mime-db-1.30.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.11.1.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/regenerator-runtime/-/regenerator-runtime-0.11.1.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/core-js/-/core-js-2.5.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/readable-stream/-/readable-stream-2.3.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/string_decoder/-/string_decoder-1.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/mime-db/-/mime-db-1.30.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/mime-types/-/mime-types-2.1.17.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/ms/-/ms-0.7.2.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/ms/-/ms-0.7.2.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/negotiator/-/negotiator-0.4.9.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/mime-db/-/mime-db-1.30.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/string_decoder/-/string_decoder-1.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/string_decoder/-/string_decoder-1.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/string_decoder/-/string_decoder-1.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/string_decoder/-/string_decoder-1.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/bytes/-/bytes-3.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/mime-db/-/mime-db-1.30.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/semver/-/semver-5.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/string_decoder/-/string_decoder-1.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/isarray/-/isarray-1.0.0.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/string_decoder/-/string_decoder-1.0.3.tgz"
npm WARN Invalid version: "https://registry.npmjs.org/mz/-/mz-2.7.0.tgz"
npm ERR! Darwin 17.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v6.10.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE

npm ERR! osrm@5.18.0 install: `node-pre-gyp install --fallback-to-build=false || ./scripts/node_install.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the osrm@5.18.0 install script 'node-pre-gyp install --fallback-to-build=false || ./scripts/node_install.sh'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the osrm package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build=false || ./scripts/node_install.sh
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs osrm
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls osrm
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/xiaogu/Project/dataService/npm-debug.log
npm ERR! code 1
Read more comments on GitHub >

github_iconTop Results From Across the Web

Node.js: Error: 403 status code downloading tarball
Error 403 means access is forbidden. Tarball is the tar.gz package file node is downloading for installation.
Read more >
Resolve HTTP 403 "Access Denied" AmazonS3Exception in ...
AmazonS3Exception: Access Denied (Service: Amazon S3; Status Code: 403; Error Code: AccessDenied; Request ID: 8B28722038047BAA; S3 Extended ...
Read more >
403 Forbidden - HTTP - MDN Web Docs - Mozilla
The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.
Read more >
download ambari tar ball - Cloudera Community - 311543
HTTP request sent, awaiting response... 403 Forbidden 2021-02-16 14:44:09 ERROR 403: Forbidden. any idea why this version cant be download?
Read more >
Troubleshoot the 403 Forbidden error when uploading files ...
I'm trying to upload files to my Amazon Simple Storage Service (Amazon S3) bucket using the Amazon S3 console. However, I'm getting a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found