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

irbk's avatar
irbk
Icon for Cirrus rankCirrus
Oct 04, 2023
Solved

SSL protocol mismatch

Ok, I ended up way down a rabbit hole earlier this week.  That whole line of thought seemed to be a red herring.  BigIP LTM trying to load balance to MS Navision servers which don't use standard 80 o...
application delivery
LTM
ssl
  • Paulius's avatar
    Paulius
    Oct 05, 2023

    irbk That is correct. Unless you have some way of the F5 being able to look for a value in the client request that would define if it was intended to be SSL or not you would have to split SSL and non-SSL into two different VS listening on different ports on the F5 side that is client facing.

Marrie_Jenner's avatar
Marrie_Jenner
Icon for Nimbostratus rankNimbostratus
May 09, 2024

An SSL protocol mismatch error typically occurs when there's an inconsistency between the SSL/TLS protocols supported by the client and the server. This can happen for various reasons:

  1. Outdated SSL/TLS versions: The client or server might be using outdated versions of SSL/TLS that are not compatible with each other. For example, if the server only supports TLS 1.2 and the client is trying to connect using SSL 3.0, a protocol mismatch error will occur.
  2. Configuration issues: Sometimes, the SSL/TLS configuration on either the client or the server side is incorrect, leading to a mismatch in supported protocols.
  3. Firewall or proxy interference: Firewalls or proxies can sometimes interfere with SSL/TLS connections, causing protocol mismatches if they don't handle the protocols properly.

Solution for this : 

Still if you are facing any error kindly take help from technical support team.