You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 28, 2019. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
xavriley
added a commit
to xavriley/locomotive-heroku
that referenced
this issue
Mar 17, 2016
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 toapi.heroku.com
now that it has a new TLS security policy in place.It now throws this kind of error:
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.The text was updated successfully, but these errors were encountered: