-
Notifications
You must be signed in to change notification settings - Fork 436
Error: CERT_UNTRUSTED when using node 0.10.34 #262
Comments
The update to the root certs might have something to do with it: nodejs/node-v0.x-archive@f9456a2 |
Facing a similar issue as reported by johnywith1n. |
We are as well. |
is there a bug filed upstream against node? it seems pretty bad if they break https requests to bitbucket |
fwiw, i can confirm that this breaks with the upgrade to v0.10.34 |
i filed this as nodejs/node-v0.x-archive#8894 |
for those not following the node thread, the best workaround is to probably rollback to node v0.10.33. node v0.10.34 contains a change to the root SSL certs that interacts badly with a bug in openssl, and breaks https on some sites. I'm not sure if they're going to rollback the cert change or try to roll forward the openssl fix. |
Thanks for all the communication here. I just got a new computer and was about to run my web application on a fresh system when I had the same error as described here. Downgrading node will save me lots of debugging time. Thanks! :) Got that problem with the Windows version: |
Same here, breaks the build of Bootstrap Material Design. |
In case someone needs a download link for node 0.10.33: http://blog.nodejs.org/2014/10/23/node-v0-10-33-stable/ |
For what its worth I ran into this issue and I got it working by temporarily using |
+1 to this issue for npm install on Web Starter Kit: phantomjs@1.9.12 install \GitHub\web-starter-kit\node_modules\gulp-uncss\nod Downloading https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-1.9.8-wind Error making request. Please report this full log at https://github.com/Medium/phantomjs |
Turn off strictssl on node v0.10.34. Fixes #262
Thanks for taking time to fix this issue. However I don't believe that turning off SSL is a good strategy. As much as I can see all updated machines will pull an uncertified version of phantomjs and execute it. This violates the assumptions of those who once checked that this module can be trusted. I'd rather be told not to update node as long as this issue exists. A better solution could be to allow users to turn off SSL through an option, but keeping the default situation as is. |
When installing using a fresh copy of node 0.10.34 (installed via nvm), I get the following:
The text was updated successfully, but these errors were encountered: