# Elasticsearch binds to all interfaces even with network.host commented out

**URL:** <https://discuss.elastic.co/t/elasticsearch-binds-to-all-interfaces-even-with-network-host-commented-out/331159>\
**Category:** Elasticsearch\
**Created:** [April 29, 2023, 9:00pm UTC](https://discuss.elastic.co/t/elasticsearch-binds-to-all-interfaces-even-with-network-host-commented-out/331159 "2023-04-29T21:00:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexl9](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexl9/32/119194_2.png) [@alexl9](https://discuss.elastic.co/u/alexl9)\
**Post date:** [April 29, 2023, 9:00pm UTC](https://discuss.elastic.co/t/elasticsearch-binds-to-all-interfaces-even-with-network-host-commented-out/331159/1 "2023-04-29T21:00:33Z")

</div>

I installed the latest Elasticsearch but it binds to all interfaces even with network.host commented out, is that expected behavior?

---

<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:** [April 30, 2023, 12:41am UTC](https://discuss.elastic.co/t/elasticsearch-binds-to-all-interfaces-even-with-network-host-commented-out/331159/2 "2023-04-30T00:41:12Z")

</div>

Hi @alexl9 Welcome to the community!

How did you install and exactly what version... did you do the default installation with security?

Can you share your elaticsearch.yml?

I suspect elasticsearch transport is not bound to all interfaces, I suspect if you did the default install with default security the HTTP transport is then bound to all interfaces, that happens with the default install you will find a line like this in the Auto Security Confinguration Settings

```auto
#----------------------- BEGIN SECURITY AUTO CONFIGURATION -----------------------
#
# The following settings, TLS certificates, and keys have been automatically      
# generated to configure Elasticsearch security features on 19-04-2023 22:14:03
#
# --------------------------------------------------------------------------------
....
# Allow HTTP API connections from anywhere
# Connections are encrypted and require user authentication
http.host: 0.0.0.0`

```

You can certainly changes that if you like

---

<div class="post-metadata">

**Author:** ![alexl9](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexl9/32/119194_2.png) [@alexl9](https://discuss.elastic.co/u/alexl9)\
**Post date:** [May 1, 2023, 3:01pm UTC](https://discuss.elastic.co/t/elasticsearch-binds-to-all-interfaces-even-with-network-host-commented-out/331159/3 "2023-05-01T15:01:53Z")

</div>

yup that was it, can the docs be updated though? In this section

> **[Networking | Elasticsearch Guide \[8.7\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.7/modules-network.html)**

it says

> By default Elasticsearch binds only to `localhost` which means it cannot be accessed remotely. This configuration is sufficient for a local development cluster made of one or more nodes all running on the same host

Also in elasticsearch.yml it says

```auto
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
#network.host:

```

---

<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:** [May 1, 2023, 3:54pm UTC](https://discuss.elastic.co/t/elasticsearch-binds-to-all-interfaces-even-with-network-host-commented-out/331159/4 "2023-05-01T15:54:50Z")

</div>

Perhaps open an issue against the elasticsearch repo.

> **[GitHub - elastic/elasticsearch: Free and Open, Distributed, RESTful Search...](https://github.com/elastic/elasticsearch/)**
>
> Free and Open, Distributed, RESTful Search Engine. Contribute to elastic/elasticsearch development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [May 1, 2023, 4:32pm UTC](https://discuss.elastic.co/t/elasticsearch-binds-to-all-interfaces-even-with-network-host-commented-out/331159/5 "2023-05-01T16:32:08Z")

</div>

Thanks both for working out what was happening here. This looks like a docs bug to me too. I was going to reopen [#95646](https://github.com/elastic/elasticsearch/issues/95646) but I see that @alexl9 has opened a new issue at [#95706](https://github.com/elastic/elasticsearch/issues/95706) instead.

---

<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:** [May 29, 2023, 4:32pm UTC](https://discuss.elastic.co/t/elasticsearch-binds-to-all-interfaces-even-with-network-host-commented-out/331159/6 "2023-05-29T16:32:30Z")

</div>

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