Getting "SSL_connect returned = 1 errno = 0 state = SSLv3 read server hi A: sslv3 error handshake alerts" with openshift nodejs application

Question

I have a nodejs application in openshift and we use the rhc port-forward command to connect to our database with local development.

We have implemented a passport for user authentication through Google and through facebook. I have authenticated myself and we can still use rhc commands. My partner recently authenticated himself through facebook, and shortly after that (~ 1 week), we got this error thrown in our path. I don’t know if this is really relevant, but it will not hurt to turn it on.

Connection to openshift.redhat.com failed: A secure connection could not be established to the server (SSL_connect returned=1 errno=0 state=SSLv3 read server hello A: sslv3 alert handshake failure). You may disable secure connections to your server with the -k (or --insecure) option 'https://openshift.redhat.com/broker/rest/api'. If your server is using a self-signed certificate, you may disable certificate checks with the -k (or --insecure) option. Using this option means that your data is potentially visible to third parties. 

Any ideas on how to resolve this? I saw this error in other questions of the stack, but every question I saw, the people asking the question, used ruby.

Answer 1

This is most likely the result of the POODLE SSLv3 fiasco. You can fix this by updating the rubclient gem. At the command prompt, type:

 sudo gem update httpclient 

Or you can also fix this by adding the following to your .openshift / express.conf file:

 ssl_version=tlsv1 

Both of these fixes essentially tell your application to use TLSv1 instead of SSLv3.

Answer 2

The rhc color is updated, run the gem update rhc and you will get the latest fixed version.

Answer 3

I had the same problem on windows with ruby ​​1.9.3 and httpclient 2.3.4.1

gem update httpclient updated the same to 2.5.3.3 and thereby gem update httpclient problem.