SSL problems of rubygems.org
Hi,
what's going on with https://rubygems.org? In Firefox it
shows up as untrusted website. Also when provided as source in
Gemfile, it will fail running bundle.
curl https://rubygems.org --verbose
* About to connect() to rubygems.org port 443 (#0)
* Trying 204.232.149.26... connected
* Connected to rubygems.org (204.232.149.26) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS alert, Server hello (2):
* SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
* Closing connection <a href="/discussions/problems/0" title="Discussion <a href="/discussions/problems/0" title="Discussion #0">#0</a>">#0</a>
curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
Support Staff 2 Posted by Nick Quaranto on 04 Aug, 2012 06:32 PM
Sorry, this comment was buried in our spam inbox.
Is this still happening?