# Capistrano and Certificates **URL:** \ **Category:** Rails\ **Created:** [April 18, 2006, 1:39pm UTC](https://www.ruby-forum.com/t/capistrano-and-certificates/58097 "2006-04-18T13:39:46Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![davidtl](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/35a633/32.png) [@davidtl](https://www.ruby-forum.com/u/davidtl)\ **Post date:** [April 18, 2006, 1:39pm UTC](https://www.ruby-forum.com/t/capistrano-and-certificates/58097/1 "2006-04-18T13:39:46Z")
All, I’m setting up a deployment script with Capistrano at the moment, and am running into some trouble when it attempts to pull the code down from the SVN server when I run the deploy task. The SVN server runs over https, and the problem seems to be when I get asked whether I want to accept or reject the certificate. I hit ‘p’ to accept the certificate permanently, but then the whole process stalls. Nothing is changed on the server, and it never recovers. I’ve pasted below the stack trace that is printed out when I terminate. Has anyone else run into this before? Are there any workarounds? I’m running on OS X with Ruby 1.8.4. The setup task ran perfectly. Thanks, David /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/command.rb:39:in `sleep' /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/command.rb:39:in`process!’ /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/command.rb:26:in `process!' /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/actor.rb:176:in`run’ /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/actor.rb:425:in `execute_on_servers' /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/actor.rb:173:in`run’ /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/scm/base.rb:41:in `run_checkout' /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/scm/subversion.rb:73:in`checkout’ /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/recipes/standard.rb:70:in `load' /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/actor.rb:125:in`update\_code’ /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/recipes/standard.rb:141:in `load' /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/actor.rb:329:in`transaction’ /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/recipes/standard.rb:140:in `load' /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/actor.rb:125:in`deploy’ /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/cli.rb:246:in `execute_recipes!' /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/cli.rb:246:in`execute\_recipes!’ /usr/local/lib/ruby/gems/1.8/gems/capistrano-1.1.0/lib/capistrano/cli.rb:221:in `execute!' ./lib/tasks/capistrano.rake:15:in`cap’ ./lib/tasks/capistrano.rake:26 /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in`execute’ /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:357:in `invoke' /usr/local/lib/ruby/1.8/thread.rb:135:in`synchronize’ /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in `invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in`run’ /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `run’ /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/bin/rake:7 /usr/local/bin/rake:18 ---
**Author:** ![davidtl](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/35a633/32.png) [@davidtl](https://www.ruby-forum.com/u/davidtl)\ **Post date:** [April 18, 2006, 5:51pm UTC](https://www.ruby-forum.com/t/capistrano-and-certificates/58097/2 "2006-04-18T17:51:50Z")
David, Please submit this as a Capistrano bug at [http://dev.rubyonrails.org](http://dev.rubyonrails.org). Capistrano is, by default, not aware of the certificate prompt. It needs to be made aware of this. (A patch would be wonderful, if anyone has the time.) Thanks, Jamis ---
**Author:** ![davidtl](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/35a633/32.png) [@davidtl](https://www.ruby-forum.com/u/davidtl)\ **Post date:** [April 18, 2006, 6:56pm UTC](https://www.ruby-forum.com/t/capistrano-and-certificates/58097/3 "2006-04-18T18:56:09Z")
David T. wrote: > Has anyone else run into this before? Are there any workarounds? I’m > running on OS X with Ruby 1.8.4. The setup task ran perfectly. I’ve faced this problem in other contexts. A workaround is to save the certificate by manually logging into your server and performing a svn checkout. During this preliminary checkout, you will save your certificate permanently on the server. After having done this you will no longer be asked when you do the checkout remotely through capistrano. – Ray ---
**Author:** ![davidtl](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/35a633/32.png) [@davidtl](https://www.ruby-forum.com/u/davidtl)\ **Post date:** [April 18, 2006, 11:59pm UTC](https://www.ruby-forum.com/t/capistrano-and-certificates/58097/4 "2006-04-18T23:59:24Z")
Jamis: I’ve submitted this as a ticket as requested: [http://dev.rubyonrails.org/ticket/4792](http://dev.rubyonrails.org/ticket/4792) > I’ve faced this problem in other contexts. A workaround is to save the > certificate by manually logging into your server and performing a svn > checkout. During this preliminary checkout, you will save your > certificate permanently on the server. Ray: Thanks - I was focusing so hard on what was going wrong that I couldn’t see the obvious solution! Best, David