Skip to main content
NetApp Knowledge Base

LDAP over TLS error: hostname does not match CN in peer certificate

Last Updated:

Applies to

  • ONTAP 9.x
  • LDAP over TLS
  • DNS


  • LDAP over TLS connection error: hostname does not match CN in peer certificate
    • Example:
12/31/2023 12:00:00 cluster1-01     ERROR         secd.unexpectedFailure: Unexpected SecD failure in Vserver "svm1". Details: Error: Validate the Ldap configuration procedure failed
  [  0 ms] Hostname found in Name Service Cache
  [     1] IP Address found in Name Service Cache
  [     1] Resolved LDAP servers: Vserver: 5
  [     1] Successfully connected to ip, port 389 using TCP
  [    18] Unable to start TLS: Connect error
  [    18]   Additional info: TLS: hostname ( does not match CN ( in peer certificate
[ 18] Unable to connect to LDAP (NIS & Name Mapping) service on
[ 18] No servers available for LDAP_NIS_AND_NAME_MAPPING, vserver: 5, domain: .
**[ 18] FAILURE: Unable to make a connection (LDAP (NIS & Name Mapping):), Result: RESULT_ERROR_SECD_NO_SERVER_AVAILABLE

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.