Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > WPM error on Playback: SSL Failure. URL contained 127 Byte DH Type Key

WPM error on Playback: SSL Failure. URL contained 127 Byte DH Type Key

Updated April 4, 2017


The following error occurs when monitoring a website using the WPM Playback:

SSL Failure. URL contained 127 Byte DH Type Key.



  • All WPM versions
  • Internet Explorer version 10 and 11
  • F5 Load Balancer



There is a  bug within Internet Explorer which causes issues when negotiating SSL with the F5 Load Balancer through which the website is accessed.


See the following articles for more information on the bug:


You can do any of the following workaround options:

Workaround 1:

Re-record the transaction by using one of the direct IP Addresses instead of the VIP of the F5 Load Balancer.


Workaround 2:

Disable the "Diffie-Hellman" Key Exchange.


Workaround 3:

Upgrade F5 software as per the previously linked document.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.



Last modified