Node-sass: Can't download binding.node because of missing proxy

[f1nality]

Cannot npm install since today, worked OK before:

> [email protected] install /application/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.3/linux_musl-x64-48_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.5.3/linux_musl-x64-48_binding.node": 

ESOCKETTIMEDOUT

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g. 

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080

[jastkand]

Same thing for me. I can't download the file wget https://github.com/sass/node-sass/releases/download/v4.7.2/linux-x64-57_binding.node. The download freezed on 0%.

Here is the console output. Not sure if it will be helpful.

--2018-01-26 10:18:52--  https://github.com/sass/node-sass/releases/download/v4.7.2/linux-x64-57_binding.node
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/4128353/7074bec0-ce98-11e7-8d2c-767ad5238cca?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180126%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180126T071853Z&X-Amz-Expires=300&X-Amz-Signature=ea5523cdd8287947dc6ad001b7cff23ef9c0369e2eb481bf6234876eb735177e&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dlinux-x64-57_binding.node&response-content-type=application%2Foctet-stream [following]
--2018-01-26 10:18:53--  https://github-production-release-asset-2e65be.s3.amazonaws.com/4128353/7074bec0-ce98-11e7-8d2c-767ad5238cca?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180126%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180126T071853Z&X-Amz-Expires=300&X-Amz-Signature=ea5523cdd8287947dc6ad001b7cff23ef9c0369e2eb481bf6234876eb735177e&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dlinux-x64-57_binding.node&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... 52.216.64.160
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|52.216.64.160|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3114206 (3.0M) [application/octet-stream]
Saving to: `linux-x64-57_binding.node.1'

Temporary I've fixed the issue by using the taobao mirror:

sass_binary_site=https://npm.taobao.org/mirrors/node-sass

Add this line to .npmrc (either global or local).

[xzyfer]

You need to be able to connect to githib.com. if you need to configure a proxy use npm config. This isn't a node-sass issue.

[jastkand]

@justedd what do you mean? I am using yarn. The problem is not related to npm or yarn. It's related to an inability to download the file from amazon s3 bucket.

[xzyfer]

Yarn doesn't make a difference if you cannot connect to githib.com. It's an
os level network issue.

On 26 Jan. 2018 7:27 pm, "orangesan" [e-mail] wrote:

run yarn instead npm i

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2230#issuecomment-360715150,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWJ-8dqJUL31Hb0MG7C4jGnEt6JkCks5tOYx6gaJpZM4RtBix
.

[f1nality]

github-production-release-asset-2e65be.s3.amazonaws.com is available again, so the problem is gone

[brunolm]

I got this error:

 npm rebuild node-sass

> [email protected] install D:\BrunoLM\Projects\project\node_modules\node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.7.2/win32-x64-64_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.7.2/win32-x64-64_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g.

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080

win32-x64-64_binding.node (64-64) doesn't exist in that version.

Restarting my computer and trying again solved the issue, it somehow was able to install even without being able to download whatever that thing was.

[xzyfer]

Node 10 requires [email protected]

On Mon., 21 May 2018, 10:40 pm BrunoLM, [e-mail] wrote:

I got this error:

npm rebuild node-sass

[email protected] install D:\BrunoLM\Projects\projectnode_modulesnode-sass
node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.7.2/win32-x64-64_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.7.2/win32-x64-64_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

  export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

  npm config set proxy http://example.com:8080

win32-x64-64_binding.node (64-64) doesn't exist in that version.

Restarting my computer and trying again solved the issue, it somehow was
able to install even without being able to download whatever that thing was.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2230#issuecomment-390775864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWKtMAOouf8pWnv4fcmOibGOPGGXXks5t0yZYgaJpZM4RtBix
.

[danielrvt]

I'm having my build failing unexpectedly because of this... is there any workaround?

[nschonni]

The solution is to follow the message that npm is giving and set your proxy variables