# SOLVED: LDAPS Intermittent Issue - No subject alternative DNS name matching dns\_url\_server found

**URL:** https://community.sonatype.com/t/solved-ldaps-intermittent-issue-no-subject-alternative-dns-name-matching-dns-url-server-found/2278
**Category:** Sonatype Nexus Repository
**Tags:** nexus-repository, help
**Created:** [August 6, 2019, 9:28am UTC](https://community.sonatype.com/t/solved-ldaps-intermittent-issue-no-subject-alternative-dns-name-matching-dns-url-server-found/2278 "2019-08-06T09:28:22Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![parryk](https://avatars.discourse-cdn.com/v4/letter/p/dec6dc/32.png) [@parryk](https://community.sonatype.com/u/parryk)
#### Post date: [August 12, 2019, 12:39pm UTC](https://community.sonatype.com/t/solved-ldaps-intermittent-issue-no-subject-alternative-dns-name-matching-dns-url-server-found/2278/5 "2019-08-12T12:39:02Z")

</div>

The issue was not that the cert was not accepted but the fact the certs DNS/SAN was not set to the URL I was using. One out of 8 thus the intermittent issue.

What I did was get the IP list of the ldap\_url then ran this command on every LDAP IP

`echo -n | openssl s_client -connect 10.56.100.47:636 | openssl x509 -noout -text | grep DNS:`

The output then showed one was missing the ldap\_url. All certs were valid and signed, just not for the ldap\_url being used.

---

_[View the full topic](https://community.sonatype.com/t/solved-ldaps-intermittent-issue-no-subject-alternative-dns-name-matching-dns-url-server-found/2278)._