# Problems with access to Elasticsearch form outside machine

**URL:** <https://discuss.elastic.co/t/problems-with-access-to-elasticsearch-form-outside-machine/172450>\
**Category:** Elasticsearch\
**Created:** [March 15, 2019, 2:18am UTC](https://discuss.elastic.co/t/problems-with-access-to-elasticsearch-form-outside-machine/172450 "2019-03-15T02:18:59Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![TimV](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timv/32/13162_2.png) [@TimV](https://discuss.elastic.co/u/TimV)\
**Post date:** [March 15, 2019, 2:25am UTC](https://discuss.elastic.co/t/problems-with-access-to-elasticsearch-form-outside-machine/172450/2 "2019-03-15T02:25:48Z")

</div>

You are failing on [bootstrap checks](https://www.elastic.co/guide/en/elasticsearch/reference/7.0/bootstrap-checks.html):

```auto
[2019-03-15T01:56:48,246][ERROR][o.e.b.Bootstrap] [node-1] node validation exception
[1] bootstrap checks failed
[1]: 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

```

The [cluster coordination algorithm has changed in 7.0](https://www.elastic.co/blog/a-new-era-for-cluster-coordination-in-elasticsearch) and in order to be _safe_ it requires some specific configuration. We relax that requirement (that is, we run in a less-safe mode) when you bind to `localhost` only, but if/when you change `network.host` we enforce that your configure the cluster safely.

This is [covered in the breaking changes documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.0/breaking-changes-7.0.html#breaking_70_discovery_changes) for 7.0

---

_[View the full topic](https://discuss.elastic.co/t/problems-with-access-to-elasticsearch-form-outside-machine/172450)._