# Can elasticsearch-head be configured to connect to secured ES?

**URL:** <https://discuss.elastic.co/t/can-elasticsearch-head-be-configured-to-connect-to-secured-es/204386>\
**Category:** Elasticsearch\
**Created:** [October 21, 2019, 12:37am UTC](https://discuss.elastic.co/t/can-elasticsearch-head-be-configured-to-connect-to-secured-es/204386 "2019-10-21T00:37:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nee\_Defeng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nee_defeng/32/45771_2.png) [@Nee\_Defeng](https://discuss.elastic.co/u/Nee_Defeng)\
**Post date:** [October 21, 2019, 12:37am UTC](https://discuss.elastic.co/t/can-elasticsearch-head-be-configured-to-connect-to-secured-es/204386/1 "2019-10-21T00:37:06Z")

</div>

I referred the instruction from this link: [https://github.com/mobz/elasticsearch-head](https://github.com/mobz/elasticsearch-head) and tried to use '[http://localhost:9100/?auth\_user=elastic&auth\_password=changeme](http://localhost:9100/?auth_user=elastic&auth_password=changeme)' but failed.

Anyone has done before successfully? Thanks

 ![2019-10-21%2011_31_39-elasticsearch-head](https://us1.discourse-cdn.com/elastic/original/3X/f/7/f73f86b30b7372f0cebdfed395162d14429f8fc2.png)

Chromse shows the error like:

vendor.js:7829 OPTIONS [https://elk:9200/](https://elk:9200/) net::ERR\_CERT\_AUTHORITY\_INVALID

---

<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:** [November 18, 2019, 12:37am UTC](https://discuss.elastic.co/t/can-elasticsearch-head-be-configured-to-connect-to-secured-es/204386/2 "2019-11-18T00:37:07Z")

</div>

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