Skip to content
This repository has been archived by the owner on Apr 28, 2019. It is now read-only.

Excon gem needs to be updated to prevent OpenSSL::SSL::SSLError #10

Open
xavriley opened this issue Mar 17, 2016 · 0 comments · May be fixed by #11
Open

Excon gem needs to be updated to prevent OpenSSL::SSL::SSLError #10

xavriley opened this issue Mar 17, 2016 · 0 comments · May be fixed by #11

Comments

@xavriley
Copy link

We've had a couple of reports on Heroku support that this gem is now failing because excon v0.23.0 can't handle the connection to api.heroku.com now that it has a new TLS security policy in place.

It now throws this kind of error:

/app/vendor/bundle/ruby/1.9.1/gems/excon-0.23.0/lib/excon/ssl_socket.rb:55:in `connect': SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: tlsv1 alert protocol version (OpenSSL::SSL::SSLError) (Excon::Errors::SocketError)

on startup due to the call to get_domains in the Heroku API gem.

One possible fix would be to bump the version of the Heroku API gem which now includes excon v0.44.0. Let me know if you need any more information.

xavriley added a commit to xavriley/locomotive-heroku that referenced this issue Mar 17, 2016
Warning - untested but fixes locomotivecms#10 in theory
@xavriley xavriley linked a pull request Mar 17, 2016 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant