I remember having had some trouble as well. Make sure that you use the following in your gem files:
devise: ~=1.4.2 ominauth: =0.2.5 (not 0.2.6 for some reason because that has a dependency conflict with another lib) In your production.rb do something like this at the top: require 'pg' require 'net/http' require 'openssl' OpenSSL::SSL:VERIFY_PEER = OpenSSL::SLL:VERIFY_NONE This is a bit of a hack but was the only way for me to get this to work in my configuration (after spending half a day investigating) On Fri, Sep 23, 2011 at 2:51 AM, Leonardo Mateo <leonardoma...@gmail.com>wrote: > On Thu, Sep 22, 2011 at 8:57 PM, Everaldo Gomes > <everaldo.go...@gmail.com> wrote: > > Hi! > > Take a look in the omni populus gem: > > https://github.com/icelab/omnipopulus > Hey! > I've just tried it and had the same result. > I wonder if twitter might have changed something on their side for > authenticating apps or if is omniauth on it's transition to 1.0. > > > > -- > Leonardo Mateo. > There's no place like ~ > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-talk@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > - -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.