SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A

ruby ssl certificate openssl imap
Joelio picture Joelio · Aug 17, 2010 · Viewed 20.8k times · Source

I have a ruby client that connects to an exchange server using IMAP & SSL. I use the Ruby Net::IMAP library (which uses openssl under the covers) to connect. Its been working fine for months. The exchange server admin installed new cert from godaddy and now I get this error:

 SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A

Does anyone know what this error means? (I tried googling)

I suspect there is an issue with the new cert causing this, but I dont know how to troubleshoot it.

Also I know you can disable certificate verification when using NET:HTTP by doing:

 http.verify_mode = OpenSSL::SSL::VERIFY_NONE if http.use_ssl?

but I cant figure out how to do this using NET:IMAP. I want to disable this to see if this is the problem.

As for code im using: Im using this(or very close to this) http://github.com/look/fetcher/blob/master/lib/fetcher/imap.rb

I tried changing to : @connection = Net::IMAP.new(@server, @port, @ssl, nil, false)

Here is the stacktrace

 checking emails on: Tue Aug 17 20:48:01 +0000 2010
 rake aborted!
 SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A
 /usr/lib/ruby/1.8/net/imap.rb:904:in `connect'
 /usr/lib/ruby/1.8/net/imap.rb:904:in `initialize' 
 /u/apps/aras/releases/20100728212439/vendor/plugins/fetcher/lib/fetcher/imap.rb:34:in `new'
 /u/apps/aras/releases/20100728212439/vendor/plugins/fetcher/lib/fetcher/imap.rb:34:in `establish_connection'
 /usr/lib/ruby/gems/1.8/gems/system_timer-1.0/lib/system_timer.rb:28:in `timeout_after'
 /u/apps/aras/releases/20100728212439/vendor/plugins/fetcher/lib/fetcher/imap.rb:33:in `establish_connection'
 /u/apps/aras/releases/20100728212439/vendor/plugins/fetcher/lib/fetcher/base.rb:31:in `fetch'

Answer

genkilabs picture genkilabs · Oct 29, 2012

I received this error trying to connect to dynamoDB with rails 3 using the default setup. Solution was to add

config.port = 443

to the

dynamo_db.rb

initializer

As of this writing this fix is in an unmerged branch of the gem.

Related questions

Ruby 1.8.7 and Net::HTTP: Making an SSL GET request with client cert?

I'm trying to fetch a resource via SSL using Net::HTTP. Here is the relevant code fragment: req = Net::HTTP::Get.new(ContentURI.path) https = Net::HTTP.new(ContentURI.host, ContentURI.port) https.use_ssl = true https.cert = OpenSSL::X509::…

Read More
SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

I am using Authlogic-Connect for third party logins. After running appropriate migrations, Twitter/Google/yahoo logins seem to work fine but the facebook login throws exception: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed The …

Read More
bundle install fails with SSL certificate verification error

When I run bundle install for my Rails 3 project on Centos 5.5 it fails with an error: Gem::RemoteFetcher::FetchError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://bb-m.rubygems.org/gems/multi_json-1.3.2.gem) …

Read More