# HTTPS config for Elasticsearch

**URL:** <https://discuss.elastic.co/t/https-config-for-elasticsearch/365073>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security, language-clients\
**Created:** [August 17, 2024, 11:09pm UTC](https://discuss.elastic.co/t/https-config-for-elasticsearch/365073 "2024-08-17T23:09:43Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [August 18, 2024, 4:50am UTC](https://discuss.elastic.co/t/https-config-for-elasticsearch/365073/9 "2024-08-18T04:50:32Z")

</div>

Perhaps look at

> [@\[Solved\] Elasticsearch integration metric settings (elastic-agetnt)](https://discuss.elastic.co/t/solved-elasticsearch-integration-metric-settings-elastic-agetnt/364984/3):
>
> hello stephen Thank you for taking the time to answer me as always my apologies I'm quite new to the community, I didn't know the rules sweat_smilesweat_smile I went into one of the nodes and run the command: curl -v --cacert /etc/elasticsearch/certs/elasticsearch-ca.pem -u elastic https://localhost:9200 and here is its output: root@elasticsearch1:/home/elasticsearch1# curl -v --cacert /etc/elasticsearch/certs/elasticsearch-ca.pem -u elastic https://localhost:9200 Enter host password f…

You need to create a cert with the proper SANs and / or IPs

> [@\[Solved\] Elasticsearch integration metric settings (elastic-agetnt)](https://discuss.elastic.co/t/solved-elasticsearch-integration-metric-settings-elastic-agetnt/364984/4):
>
> Yup regenerate the certs with the proper SANs, IPs etc... test with curl and you should be good to go. That is the proper secure approach

---

_[View the full topic](https://discuss.elastic.co/t/https-config-for-elasticsearch/365073)._