Distributions: Problems with certificates and wheezy

Created on 21 Nov 2014  Â·  4Comments  Â·  Source: nodesource/distributions

Hi,

I stumbled into what seems to be an issue with wheezy:

    cat /etc/apt/sources.list.d/nodesource.list 
    deb https://deb.nodesource.com/node wheezy main
    deb-src https://deb.nodesource.com/node wheezy main
    curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -

and when I apt-get update, I get:

Ign https://deb.nodesource.com wheezy Release.gpg                                                             
Ign https://deb.nodesource.com wheezy Release                                                      
Err https://deb.nodesource.com wheezy/main Sources                       
  Problem with the SSL CA cert (path? access rights?)
Err https://deb.nodesource.com wheezy/main amd64 Packages
  Problem with the SSL CA cert (path? access rights?)
Atteint http://security.debian.org wheezy/updates Release.gpg
Atteint http://security.debian.org wheezy/updates Release
Réception de : 3 http://security.debian.org wheezy/updates/main amd64 Packages [276 kB]
3 o réceptionnés en 5s (0 o/s)      
W: Impossible de récupérer https://deb.nodesource.com/node/dists/wheezy/main/source/Sources  Problem with the SSL CA cert (path? access rights?)

W: Impossible de récupérer https://deb.nodesource.com/node/dists/wheezy/main/binary-amd64/Packages  Problem with the SSL CA cert (path? access rights?)

Most helpful comment

Ok, an

apt-get install ca-certificates

fixed the problem, sorry

All 4 comments

That's pretty odd, this is potentially an issue on our end with the tls setup but we've not seen this reported elsewhere, perhaps you have a corrupt local certificate chain or something like that. Maybe do a reinstall of the apt-transport-https package as a start?

I'm working from inside a docker container, you're right maybe the local
certificate is corrupted, i'll try fixing it with
http://derekmolloy.ie/fixing-git-and-curl-certificates-problem-on-beaglebone-blac/
and I'll let you know

Le Sat Nov 22 2014 at 7:54:48 PM, Rod Vagg [email protected] a
écrit :

That's pretty odd, this is potentially an issue on our end with the tls
setup but we've not seen this reported elsewhere, perhaps you have a
corrupt local certificate chain or something like that. Maybe do a
reinstall of the apt-transport-https package as a start?

—
Reply to this email directly or view it on GitHub
https://github.com/nodesource/distributions/issues/42#issuecomment-64091035
.

Ok, an

apt-get install ca-certificates

fixed the problem, sorry

bravo you saved my server

Was this page helpful?
0 / 5 - 0 ratings