# Error with openssl in 1.8.4 on XP?

**URL:** <https://www.ruby-forum.com/t/error-with-openssl-in-1-8-4-on-xp/96486>\
**Category:** Ruby\
**Created:** [June 29, 2006, 12:23am UTC](https://www.ruby-forum.com/t/error-with-openssl-in-1-8-4-on-xp/96486 "2006-06-29T00:23:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [June 29, 2006, 12:23am UTC](https://www.ruby-forum.com/t/error-with-openssl-in-1-8-4-on-xp/96486/1 "2006-06-29T00:23:50Z")

</div>

I’ve been trying to consume a SOAP service using ruby, which should be  
simple enough, but I need to work across Https and there seems to be no  
way to do this currently.

The only message I get is OpenSSL::SSL::SSLError and then a stack trace  
that leads back into http.rb line 588, which is where it asks the socket  
to connect. There is no informative error message and the problem  
appears to be in the binary rather than in the ruby source.

In the last few days of beating my head against the wall over this one  
I’ve found various discussions that suggest there is a problem with  
openSSL on the Windows version of 1.8.4 - I have only managed to get  
anything working when I tried it on my Debian Box, running 1.8.2 - I  
don’t know if it’s the version or the Debian but I can make https  
requests successfully from there. Solutions I’ve seen suggested have  
included rolling back to 1.8.2 and erasing old versions of the libraries  
in the /site\_ruby/ directory. The latter doesn’t work, the former I’d  
prefer to avoid if possible.

I was wondering if anyone has come up with an authoritative solution to  
this, or a handy quick-fix? If not, where should I be going to file a  
bug report?

---

<div class="post-metadata">

**Author:** ![glenatron](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/94ad74/32.png) [@glenatron](https://www.ruby-forum.com/u/glenatron)\
**Post date:** [June 29, 2006, 2:38pm UTC](https://www.ruby-forum.com/t/error-with-openssl-in-1-8-4-on-xp/96486/2 "2006-06-29T14:38:44Z")

</div>

ben moxon wrote:

> I’ve been trying to consume a SOAP service using ruby, which should be  
> simple enough, but I need to work across Https and there seems to be no  
> way to do this currently.
> 
> The only message I get is OpenSSL::SSL::SSLError and then a stack trace  
> that leads back into http.rb line 588, which is where it asks the socket  
> to connect. There is no informative error message and the problem  
> appears to be in the binary rather than in the ruby source.
> 
> In the last few days of beating my head against the wall over this one  
> I’ve found various discussions that suggest there is a problem with  
> openSSL on the Windows version of 1.8.4 - I have only managed to get  
> anything working when I tried it on my Debian Box, running 1.8.2 - I  
> don’t know if it’s the version or the Debian but I can make https  
> requests successfully from there. Solutions I’ve seen suggested have  
> included rolling back to 1.8.2 and erasing old versions of the libraries  
> in the /site\_ruby/ directory. The latter doesn’t work, the former I’d  
> prefer to avoid if possible.
> 
> I was wondering if anyone has come up with an authoritative solution to  
> this, or a handy quick-fix? If not, where should I be going to file a  
> bug report?

I’ve filed a bug report, here is a convenient sample that shows the  
problem:

require ‘http-access2’

def check\_uri\_request(uriText)  
clnt=HTTPAccess2::Client.new  
clnt.ssl\_config.verify\_mode=OpenSSL::SSL::VERIFY\_NONE  
puts clnt.get\_content(uriText)  
end

check\_uri\_request(‘[Google Ads - Get Customers and Sell More with Online Advertising](https://adwords.google.co.uk/select/steps.html)’)

I’m using http-access2 because the net/http and open-uri stuff kept  
dying before it even got to ssl.

Definitely a problem with 1.8.4 on Windows XP - 1.8.2 works fine and  
even open-uri fails nicely pointing out that it doesn’t support https. I  
havent tried it with 1.8.4 on any other platforms yet.