Forum Discussion
CirrostratusLTM LogConnection error: ssl_null_parse:3167: record length too large (22)
Has anybody seen this issue?
Running 13.1.0.7 Log Level Warning Connection error: ssl_null_parse:3167: record length too large (22)
I found this article but it doesnt apply to 13.1.0.7 K17088: Increasing the size of the SSL handshake buffer
This is the size of my buffer below: list sys db tmm.ssl.maxhandshakesize sys db tmm.ssl.maxhandshakesize { value "32768"
4 Replies
Vijay_ECirrus
Looks to be a simple change. I have done it without any concerns. I would double check to make sure you aren't using high (more than 50%) of resources (memory mainly) on the F5 before enabling it.
Bill_TurnerNimbostratus
Having same issue, same version. Changing the handshake buffer had no effect. I reverted the change. Still looking for an answer.
Connection error: ssl_null_parse:3167: record length too large (22)
BrandonI opened a ticket with F5 Support. One of our VIPs had a server side ssl profile "serverssl-insecure-compatible".
I remove the profile
We have this virtual server using "serverssl-insecure-compatible"
https://support.f5.com/csp/article/K13214
Support Engineer also added
"The following table lists the ciphers used in the serverssl-insecure-compatible SSL profile in BIG-IP 13.0.0 - 13.1.0"
Adding "!DHE:!ECDHE:" may prevent those messages from happening.
cjuniorNacreous
I'm facing the same issue after upgrade to 13.1.1.5.
What SSL profile and cipher did you associate to the virtual server?
Could you share this information?
Thank you .
