For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Qasim's avatar
Qasim
Icon for Cirrostratus rankCirrostratus
Aug 08, 2019

SSL Troubleshoot (fatal Description : handshake failure)

Hi,   I have a service that run in two DCs one primary and another secondary. the service is configured like the following:   Client --> tcp/443 LTM ----->tcp/80 backend.   however, the ...
Qasim's avatar
Qasim
Icon for Cirrostratus rankCirrostratus
Aug 09, 2019

Thanks Dario,

 

 

Aug 8 18:27:10 LLB02-SEC warning tmm[17405]: 01260009:4: Connection error: ssl_hs_ciphprivdec:3622: crypto_req_process (80)

Aug 8 18:27:10 LLB02-SEC crit tmm[17405]: 01010025:2: Device error: crypto codec No codec available to initialize request context.

 

Dario_Garrido's avatar
Dario_Garrido
Icon for Noctilucent rankNoctilucent
Aug 09, 2019

It seems any problem with the codec

"Device error: crypto codec No codec available to initialize request context".

 

I've never seen this kind of issue, so it seems a bug related with the release. I recommend you to open a TS case.

 

BTW, have you disable "generic alert" option in your SSL profile?

 

Also, it would be helpfull to decrypt the traffic to figure out the exact message you are receiving after the "ChangeCipherSpec" message.

REF - https://support.f5.com/csp/article/K16700

REF - https://support.f5.com/csp/article/K19310681

 

KR,

Dario.