# HTTPS not working for subject alternative name (SAN)

**URL:** <https://discuss.elastic.co/t/https-not-working-for-subject-alternative-name-san/163977>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [January 12, 2019, 4:02am UTC](https://discuss.elastic.co/t/https-not-working-for-subject-alternative-name-san/163977 "2019-01-12T04:02:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ran\_Raines\_Moshe](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@Ran\_Raines\_Moshe](https://discuss.elastic.co/u/Ran_Raines_Moshe)\
**Post date:** [January 12, 2019, 4:02am UTC](https://discuss.elastic.co/t/https-not-working-for-subject-alternative-name-san/163977/1 "2019-01-12T04:02:09Z")

</div>

I get this error while you can see the url do exists in the list

Get https://**[asp-xxx-app-671.dev.mydomain.com](http://asp-xxx-app-671.dev.mydomain.com)**:44330/xxx/: x509: certificate is valid for "[xxxxxxx.dev.mydomain.com](http://xxxxxxx.dev.mydomain.com)","_.xxxxxxx.dev.mydomain.com","**[asp-xxx-app-671.dev.mydomain.com](http://asp-xxx-app-671.dev.mydomain.com)**","_.asp-xxx-app-671.dev.mydomain.com","[asp-xxx-app-673.dev.mydomain.com](http://asp-xxx-app-673.dev.mydomain.com)","_.asp-xxx-app-673.dev.mydomain.com","[asp-xxx-app-674.dev.mydomain.com](http://asp-xxx-app-674.dev.mydomain.com)","_.asp-xxx-app-674.dev.mydomain.com", not **[asp-xxx-app-671.dev.mydomain.com](http://asp-xxx-app-671.dev.mydomain.com)**

yes this is all under the SAN and also looks by the error it is recognizing all the list but has bug with the match

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [January 18, 2019, 3:59pm UTC](https://discuss.elastic.co/t/https-not-working-for-subject-alternative-name-san/163977/2 "2019-01-18T15:59:47Z")

</div>

Sorry for the delay, this is a bit weird. Are you sure it's the SAN and not some other aspect of the cert? Heartbeat works correctly against [https://www.elastic.co/products](https://www.elastic.co/products), and that uses a SAN cert.

Can you reach that domain correctly with `curl`?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 15, 2019, 4:14pm UTC](https://discuss.elastic.co/t/https-not-working-for-subject-alternative-name-san/163977/3 "2019-02-15T16:14:57Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.