Reputation: 1628
Disclaimer: I didn't write the Capistrano recipe or set up the (FreeBSD) server, I inherited everything from a developer who now works elsewhere. Learning as I go.
Changes I made to the server since last week Friday, not sure which is causing deployments to fail:
1) Updated Ruby using ports.
2) Recompiled Passenger/Apache.
3) Updated rubygems. (gem update --system
)
If I issue bundle install --without development test
locally on the server, bundle is successful. Capistrano attempts to execute: cd /usr/local/docs/arc/releases/20140411143706 && bundle install --gemfile /usr/local/docs/arc/releases/20140411143706/Gemfile --path /usr/local/docs/arc/shared/bundle --deployment --quiet --without development test
and results in:
Could not verify the SSL certificate for https://rubygems.org/quick/Marshal.4.8/Ascii85-1.0.2.gemspec.rz.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for
verification. For information about OpenSSL certificates, see bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and
change 'https' to 'http'.
This led me to believe I should change the gem sources to only fetch gems using http://rubygems.org
. Verified gem sources by issuing gem sources
, there was only the https://rubygems.org
entry. I replaced it with the http
entry and attempted deploying with Capistrano once more. Same results as noted above.
What should I do to fix this? I feel like I need to re-bundle something. It's as though old changes are sticking around.
Upvotes: 1
Views: 312
Reputation: 363
Check the first few lines of your Gemfile, usually you will find something like
source 'https://rubygems.org'
change this to
source 'http://rubygems.org'
Note: Maybe emptying /usr/local/docs/arc/shared/bundle before will be necessary. Also see this how to clean up your shared bundler directory.
Upvotes: 1