mmistakes / jekyll-theme-skinny-bones

A Jekyll starter with a variety of flexible layouts and components.
https://mmistakes.github.io/jekyll-theme-skinny-bones
MIT License
804 stars 906 forks source link

Could not find a valid gem 'redcarpet' (= 3.2.0) Unable to download data from https://rubygems.org/ error. What is the fix #13

Closed smadakcir closed 9 years ago

smadakcir commented 9 years ago

C:\Users\Design\Dropbox\onderhanden\design user herontwerp_0000b_marketing_Blog> bundle install DL is deprecated, please use Fiddle Fetching gem metadata from https://rubygems.org/........ Using blankslate 2.1.2.4 Using sass 3.4.7 Using thor 0.19.1 Using bourbon 4.0.2 Using hitimes 1.2.2 Using timers 4.0.1 Using celluloid 0.16.0 Using fast-stemmer 1.0.2 Using classifier-reborn 2.0.2 Using coffee-script-source 1.8.0 Using execjs 2.2.2 Using coffee-script 2.3.0 Using colorator 0.1 Using ffi 1.9.6 Using jekyll-coffeescript 1.0.1 Using jekyll-gist 1.1.0 Using jekyll-paginate 1.1.0 Using jekyll-sass-converter 1.2.1 Using rb-fsevent 0.9.4 Using rb-inotify 0.9.5 Using listen 2.7.11 Using jekyll-watch 1.1.2 Using kramdown 1.5.0 Using liquid 2.6.1 Using mercenary 0.3.4 Using posix-spawn 0.3.9 Using yajl-ruby 1.1.0 Using pygments.rb 0.6.0

Gem::RemoteFetcher::FetchError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://rubygems.org/gems/redca rpet-3.2.0.gem) An error occurred while installing redcarpet (3.2.0), and Bundler cannot continue. Make sure that gem install redcarpet -v '3.2.0' succeeds before bundling.

C:\Users\Design\Dropbox\onderhanden\design user herontwerp_0000b_marketing_Blog> gem install redcarpet -v 3.2.0 ERROR: Could not find a valid gem 'redcarpet' (= 3.2.0), here is why: Unable to download data from https://rubygems.org/ - SSL_connect retur ned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed ( https://rubygems.org/specs.4.8.gz)

C:\Users\Design\Dropbox\onderhanden\design user herontwerp_0000b_marketing_Blog>

mmistakes commented 9 years ago

It's a rubygems.org issue with switching their DNS and SSL. According to their status the issue was fixed. I had to use the insecure source to install gems using the following method and then flip back to the secure one.

Replace the ssl gem source with non-ssl as a temp solution:

gem sources -r https://rubygems.org/
gem sources -a http://rubygems.org/

Here's another workaround if you need it.