# Not starting Elasticsearch for some reason I can't undestand

**URL:** <https://discuss.elastic.co/t/not-starting-elasticsearch-for-some-reason-i-cant-undestand/177092>\
**Category:** Elasticsearch\
**Created:** [April 16, 2019, 12:58pm UTC](https://discuss.elastic.co/t/not-starting-elasticsearch-for-some-reason-i-cant-undestand/177092 "2019-04-16T12:58:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [April 16, 2019, 1:24pm UTC](https://discuss.elastic.co/t/not-starting-elasticsearch-for-some-reason-i-cant-undestand/177092/2 "2019-04-16T13:24:47Z")

</div>

You are binding to `10.254.214.145` which is not localhost, so you are in production mode:

> [@HikariNTB](#):
>
> ```plaintext
> bound or publishing to a non-loopback address, enforcing bootstrap checks
> 
> ```

However, your node configuration is not suitable for production use:

> [@HikariNTB](#):
>
> ```plaintext
> the default discovery settings are unsuitable for production use;
> at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured
> 
> ```

If this is a production deployment, you should set one of these settings. If this is a test deployment only then you can either bind to localhost or else use [single-node discovery](https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html#single-node-discovery) to avoid the bootstrap checks.

---

_[View the full topic](https://discuss.elastic.co/t/not-starting-elasticsearch-for-some-reason-i-cant-undestand/177092)._