# Certificate doesn't match any of the subject alternative names **URL:** \ **Category:** Logstash\ **Created:** [February 23, 2022, 10:25pm UTC](https://discuss.elastic.co/t/certificate-doesnt-match-any-of-the-subject-alternative-names/298091 "2022-02-23T22:25:55Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![maof97](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maof97/32/101433_2.png) [@maof97](https://discuss.elastic.co/u/maof97)\ **Post date:** [March 8, 2022, 1:20am UTC](https://discuss.elastic.co/t/certificate-doesnt-match-any-of-the-subject-alternative-names/298091/3 "2022-03-08T01:20:38Z")
I had a similar problem like this ([Unable to create an enrollment token for Kibana. "Elasticsearch node HTTP layer SSL configuration Keystore doesn't contain any PrivateKey entries where the associated certificate is a CA certificate"](https://discuss.elastic.co/t/unable-to-create-an-enrollment-token-for-kibana-elasticsearch-node-http-layer-ssl-configuration-keystore-doesnt-contain-any-privatekey-entries-where-the-associated-certificate-is-a-ca-certificate/297032)) A reply I got there was: > [@Unable to create an enrollment token for Kibana. "Elasticsearch node HTTP layer SSL configuration Keystore doesn't contain any PrivateKey entries where the associated certificate is a CA certificate"](https://discuss.elastic.co/t/unable-to-create-an-enrollment-token-for-kibana-elasticsearch-node-http-layer-ssl-configuration-keystore-doesnt-contain-any-privatekey-entries-where-the-associated-certificate-is-a-ca-certificate/297032/4): > > We do our best to detect all IP addresses of the interfaces that are up when Elasticsearch is installed and then use them as IP Subject Alternative Names in the HTTP TLS certificate. So I guess you made the same mistake as me, by installing ES without the later used interface being already present. --- _[View the full topic](https://discuss.elastic.co/t/certificate-doesnt-match-any-of-the-subject-alternative-names/298091)._