Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Server & Application Monitor (SAM) > HTTPS component monitor error messages occur with TLS disabled on FIPS enabled nodes

HTTPS component monitor error messages occur with TLS disabled on FIPS enabled nodes

Table of contents

Updated 12-13-2016

Overview

If you have TLS disabled on a node with FIPS enabled, you may receive errors for any assigned HTTPS component monitors. The error messages are due to TLS being disabled. When disabled on a node, a TLS/SSL channel cannot be created. With FIPS enabled, it ensures the TLS handshake to ensure only FIPS compliant crypto algorithms are used.

This article details the error messages you may receive in this situation. To resolve, enable TLS on nodes with FIPS enabled.

Environment

  • SAM 6.2.4, 6.3, 6.4
  • SSL
  • TLS
  • FIPS

Detail

The following errors display for HTTPS component monitors if you have TLS disabled on FIPS enabled nodes. To resolve, enable TLS on FIPS enabled nodes.

 

Error: Could not create SSL/TLS secure channel.

Version: SAM 6.2.4

 

Error: The underlying connection was closed: An unexpected error occurred on a receive.

Version: SAM 6.3, 6.4

 

 

 

Last modified
09:58, 15 Feb 2017

Tags

Classifications

Public