# Elastic Search 7 unable to bootstrap the cluster due to master not discovered yet

**URL:** <https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073>\
**Category:** Elasticsearch\
**Created:** [May 21, 2019, 5:36pm UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073 "2019-05-21T17:36:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [May 21, 2019, 8:11pm UTC](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073/2 "2019-05-21T20:11:26Z")

</div>

Remove the port from the `cluster.initial_master_nodes` setting, and it will work 🙂 We have updated the docs recently to make it clearer that either node name, or ip/port is to be used. Node name/port is not a valid combination.

---

_[View the full topic](https://discuss.elastic.co/t/elastic-search-7-unable-to-bootstrap-the-cluster-due-to-master-not-discovered-yet/182073)._