Keycloak Keep crashing Unexpectedly

Getting advice
10

Hey Subodh,

Pls don’t mind and feel offended. There is absolutely no reason to do so.
My intention was to make the code more readable so you have a better reach of people. You can yourself see the difference when you use that code block and when you haven’t.

I have been using various online forums for over fifteen years, I was too helped by senior members to write good questions with relevant logs/code sections so that it is easier for other community members.

This is a bit challenging tone, we are here to help each other :slight_smile: Anyways, let’s start with the basics which you have failed to mention in your question itself.

The issue you are facing is due to SSL Version or could be ciphers, from experience debugging such issues are a bit tricky and could be due to a lot of factors.

handshake: javax.net.ssl.SSLHandshakeException: Client requested protocol SSLv3 not enabled or not supported

I am not an expert on Keycloak or NodeJS or ReactJS but would start a bit like this

  • Try using openssl s_client to connect to the application using SSLv3. Double-check if you see the same error. Then maybe try with SSLv1 or SSLv2.
  • Mention your ReactJS and NodeJS versions too. You mentioned that it was working for a couple of days and then stopped working. Did something changes on the application?
  • What are the hops between keycloak and apps? Where do SSL offloads - on ALB/ELB or the application itself?
  • Keycloak has a variety of uses. What exactly are you using it for?
  • How did you install keycloak on Ubuntu? Can you reproduce the issue with the keycloak docker image jboss/keycloak:9.0.3?
  • Which version of Ubuntu? Maybe try to upgrade the OS which will also update the relevant SSL packages?
  • You have mentioned that it works in local machine. What kind of machine is it? Is it same as the EC2 Instance? If you can use docker then differences in libraries can be ruled out.
  • I am not sure if this could be related but you can also try out JDBC_PARAMS=useSSL=false. This solved my issue here. It is not ideal but at least you will have an interim solution.
  • If possible, try to list out the steps to reproduce the issue.

Cheers,
Vikas