Deploy with Capistrano. Bundle install freezes indefinetly

I am fighting with this for 5 days… i’m getting crazy!
Here is my deploy.rb:

require “bundler/capistrano”
require “rvm/capistrano” # Load RVM’s capistrano plugin.
set :rvm_ruby_string, :local # Or whatever env you want it to
in. ‘1.9.3’

set :domain, ‘
set :application, “myapp”
set :repository, “[email protected]:myrepo/myapp.git”
set :branch, “bkpantesbootstrap” # “master”

set :scm, “git” # :git
set :user, “myuser”
set :deploy_to, “/home/myuser/apps/#{application}”
set :deploy_via, :copy # :remote_cache
set :copy_strategy, :export

set :use_sudo, false
set :keep_releases, 3

role :web, ‘xxx.xx.xx.xx’ # # Your HTTP server, Apache/etc
role :app, ‘xxx.xx.xx.xx’ # This may be the
as your Web server
role :db, ‘xxx.xx.xx.xx’, :primary => true # This is where Rails
migrations will run

set :port, 22

after ‘deploy:update_code’ do
run “cd #{release_path}; RAILS_ENV=production rake assets:precompile”

If you are using Passenger mod_rails uncomment this:

namespace :deploy do
task :start do ; end
task :stop do ; end
task :restart, :roles => :app, :except => { :no_release => true } do
run “#{try_sudo} touch #{File.join(current_path,‘tmp’,‘restart.txt’)}”

Then, after cap deploy:setup and cap deploy:cold, Capistrano makes
install” and this command never ends!
My server is a fresh Ubuntu 12.10, ruby 1.9.3-p362, rails 3.1.11 and
In previous releases everything worked fine… now it is a nightmare!

Perhaps my problems began with the rvm installation. The command “curl
-L | bash -s stable” always finished with the message:
curl: (35) Unknown SSL protocol error in connection to

I only got rvm installed using: “sudo \curl -L | bash
gem install bundler rake
ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)
too many connection resets
I had to download bundler and rake manually and install with: gem
–force --local *.gem
But at last I have ruby and rails installed.
What am I doing wrong? Any help will be very appreciated.
Thank you very much!

Maybe the firewall on the server blocks the git protocol. I have had

Den sndagen den 3:e mars 2013 kl. 21:24:55 UTC+1 skrev LuisRuby: