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

SSL cert issues? #60

Closed
fhemberger opened this issue Aug 30, 2015 · 2 comments · May be fixed by Susangriffis/nodejs.org#5 or rexingQ/nodejs.org#5
Closed

SSL cert issues? #60

fhemberger opened this issue Aug 30, 2015 · 2 comments · May be fixed by Susangriffis/nodejs.org#5 or rexingQ/nodejs.org#5

Comments

@fhemberger
Copy link
Contributor

I think I saw a related ticket a few days ago but couldn't find it anymore. When I try to access new.nodejs.org with wget (scanning for 404s), I get the following message:

Resolving new.nodejs.org (new.nodejs.org)... 104.131.173.199
Connecting to new.nodejs.org (new.nodejs.org)|104.131.173.199|:443... connected.
ERROR: cannot verify new.nodejs.org's certificate, issued by 'CN=COMODO RSA Domain Validation Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB':
  Unable to locally verify the issuer's authority.
To connect to new.nodejs.org insecurely, use `--no-check-certificate'.

Browser is working fine, reporting just in case it causes issues for other tools as well.

@rvagg
Copy link
Member

rvagg commented Aug 30, 2015

thanks, I was just tinkering with the certs but I thought I was improving the chain so ...

@rvagg
Copy link
Member

rvagg commented Aug 30, 2015

got it, I added the wrong trust cert to the chain, fixed now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants