Updating rubygems nothing to update Chat horney girls online
For information about Open SSL certificates, see bit.ly/ruby-ssl.
To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.
I was going about my usual business, cloning a new project and bundling when I encountered this deliciously vague error: Gem:: Remote Fetcher:: Fetch Error: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://s3.amazonaws.com/production.s3.rubygems.org/gems/builder-3.1.4.gem) An error occurred while installing builder (3.1.4), and Bundler cannot continue.
Make sure that `gem install builder -v '3.1.4'` succeeds before bundling. I hadn’t updated any packages, changed any configurations, or done anything that could be the obvious cause of this issue.
One dirty hack and all was back to normal:rm $(ruby -ropenssl -e 'puts Open SSL:: X509:: DEFAULT_CERT_FILE') && \ brew install curl-ca-bundle && ln -s /usr/local/opt/curl-ca-bundle/share/\ $(ruby -ropenssl -e 'puts Open SSL:: X509:: DEFAULT_CERT_FILE') \ echo 'export SSL_CERT_FILE=/usr/local/opt/curl-ca-bundle/share/ca-bundle.crt' The above command feels more like a band-aid than anything else but it will replace the outdated CA bundle with the latest one available from the c URL maintainers.
My first thought was to blame the repository I had cloned.
Unfortunately, when I switched to another project I was greeted with the same message.
I obviously tried what bundler recommended and ran , fully expecting the same message (as that’s usually how it goes). Being fairly experienced with Linux and OSX, I’m used to dealing with outdated SSL certificate bundles and explicitly specifying the path to Open SSL.
When running the above in a terminal, I was able to see the exact location Ruby was getting its SSL certificate authority bundle.Mine was outdated which was causing the errors (when connecting to Ruby Gems.org, it would fail epicly, not being able to verify the authenticity of its certificate).