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

CERT_UNTRUSTED error. #14

Open
williamhrs opened this issue Jan 28, 2015 · 6 comments
Open

CERT_UNTRUSTED error. #14

williamhrs opened this issue Jan 28, 2015 · 6 comments

Comments

@williamhrs
Copy link

Hi, when trying to make a simple test using the module I'm getting a CERT_UNTRUSTED error.

@danjenkins
Copy link
Owner

hi @williamhrs you're going to need to give a bit more information here, what version of node are you running? Which OS? What were you trying to do? Which function are you calling? Can you give me a backtrace?

@chriskinsman
Copy link
Contributor

I am seeing the same thing. Simple code:

var gecko = new Geckoboard({api_key: 'asdfasdfasdfasdfasdf'});
gecko.number('asdfasdfasdfasd').send({item:[{value:123, text:'test}]}, false, 'standard', done);

@chriskinsman
Copy link
Contributor

Looks like an issue with https and the ca chain. If you add rejectUnauthorized: false to the options hash things go through but that is a bit sketchy

@danjenkins
Copy link
Owner

hi @chriskinsman / @williamhrs , yes, it looks like geckoboard has done something with their SSL certs, or a version of node has changed something... can you please tell me what version of node you are running?

You could either add rejectUnauthorized or look at using https://github.com/coolaj86/node-ssl-root-cas which would help aleviate the issue, maybe

This isn't an issue with the library so I'm going to close the issue. Please re-open if you feel it is an issue with the library and not geckoboard's SSL or Node.js

@chriskinsman
Copy link
Contributor

There is no way to set rejectUnauthorized without modifying the library. I
will perhaps figure out a pull request for that.

On Fri, Jan 30, 2015 at 12:06 PM, Dan Jenkins [email protected]
wrote:

hi @chriskinsman https://github.com/chriskinsman / @williamhrs
https://github.com/williamhrs , yes, it looks like geckoboard has done
something with their SSL certs, or a version of node has changed
something... can you please tell me what version of node you are running?

You could either add rejectUnauthorized or look at using
https://github.com/coolaj86/node-ssl-root-cas which would help aleviate
the issue, maybe

This isn't an issue with the library so I'm going to close the issue.
Please re-open if you feel it is an issue with the library and not
geckoboard's SSL or Node.js


Reply to this email directly or view it on GitHub
#14 (comment)
.

@danjenkins
Copy link
Owner

Ah ok! that makes sense, I'll re-open the issue then

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

3 participants