Security Compliance

IE fails to connect to LEM

This article resolves an issue when IE (Microsoft Internet Explorer) version 11 fails to connect to LEM after upgrades to 6.3.x. Message: This Page can't be displayed. Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings.

First published date

10/30/2018 8:57 PM

Last published date

5/31/2019 7:54 PM

Overview

IE (Microsoft Internet Explorer) version 11 may fail to connect to LEM after upgrades to 6.3.x.

Message: This Page can't be displayed.  Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings...

Product section

Log & Event Manager

Cause

As of LEM version 6.2.1, SolarWinds is using SHA512 instead of MD5 for the certificate signature algorithm.

In Microsoft IE version 8, 9 & 10, IE did not default of force TLS 1.2, whereas IE-11 does try to force the use of TLS 1.2.

So LEM versions 6.2.1 and before, we disabled the TLS 1.2 on IE to get IE to communicate with LEM.

On LEM 6.2.1 and later, LEM now uses SHA512 which prefers TLS 1.2.

As of LEM 6.3.x, LEM has a command (confselfsignedcert) to re-generate the certificate and eliminate the error with the certificate.

Resolution

  1. Open a vSphere console connection (or putty session on port 32022) to LEM.
  2. Enter the "manager" menu > enter the "confselfsignedcert" to create a new certificate.
  3. Close the console connection.
  4. IE-11 should be working.


If using the air-based console:

  1. Open vSphere console connection (or putty session on port 32022) to LEM.
  2. Enter the "manager" menu > enter the "confselfsignedcert" to create a new certificate.
  3. Enter the exportcert command to export the new certificate.
  4. Open the Microsoft MMC console, and add the "certificates" menu.
  5. Locate the Trusted Root Certification Authorities under mmc, and delete the existing LEM certificate (starts with TNS...).
  6. Using a right-click to add the new certificate, locate the new certificate and import to Trusted Root Certification Authorities
  7. The certificate should exist only under Trusted Root Certification Authorities, and no other location.
  8. The air-console should not be working.


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.