# Cluster node discovery failed

**URL:** https://discuss.elastic.co/t/cluster-node-discovery-failed/155653
**Category:** Elasticsearch
**Tags:** docker
**Created:** [November 7, 2018, 3:50am UTC](https://discuss.elastic.co/t/cluster-node-discovery-failed/155653 "2018-11-07T03:50:21Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![wujiaxin159](https://avatars.discourse-cdn.com/v4/letter/w/e68b1a/32.png) [@wujiaxin159](https://discuss.elastic.co/u/wujiaxin159)
#### Post date: [November 7, 2018, 3:50am UTC](https://discuss.elastic.co/t/cluster-node-discovery-failed/155653/1 "2018-11-07T03:50:21Z")

</div>

elk version: 6.3.0  
Using docker container  
Server IP: 9.77.10.27 --\> Docker IP: 172.17.0.2  
Server IP: 9.77.10.28 --\> Docker IP: 172.17.0.3

9.77.10.27 config

```
cluster.name: elk
node.name: node-1
network.host: 0.0.0.0
discovery.zen.ping.unicast.hosts: ["9.77.10.27:9300","9.77.10.28:9300"]
discovery.zen.minimum_master_nodes: 1
node.master: true
node.data: true
transport.tcp.port: 9300

```

9.77.10.27 config

```
cluster.name: elk
node.name: node-2
network.host: 0.0.0.0
discovery.zen.ping.unicast.hosts: ["9.77.10.27:9300","9.77.10.28:9300"]
discovery.zen.minimum_master_nodes: 1
node.master: true
node.data: true
transport.tcp.port: 9300

```

After starting, there is only one node in the clusters of monitoring.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [November 7, 2018, 6:27am UTC](https://discuss.elastic.co/t/cluster-node-discovery-failed/155653/2 "2018-11-07T06:27:53Z")

</div>

What are the logs saying? Any kind of firewall that would not expose port 9300?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [November 7, 2018, 6:36am UTC](https://discuss.elastic.co/t/cluster-node-discovery-failed/155653/3 "2018-11-07T06:36:12Z")

</div>

Also what does your docker config file/command look like?

---

<div class="post-metadata">

### Author: ![wujiaxin159](https://avatars.discourse-cdn.com/v4/letter/w/e68b1a/32.png) [@wujiaxin159](https://discuss.elastic.co/u/wujiaxin159)
#### Post date: [November 7, 2018, 6:59am UTC](https://discuss.elastic.co/t/cluster-node-discovery-failed/155653/4 "2018-11-07T06:59:02Z")

</div>

Yes, the port is open and can be requested in docker.

---

<div class="post-metadata">

### Author: ![wujiaxin159](https://avatars.discourse-cdn.com/v4/letter/w/e68b1a/32.png) [@wujiaxin159](https://discuss.elastic.co/u/wujiaxin159)
#### Post date: [November 9, 2018, 2:05am UTC](https://discuss.elastic.co/t/cluster-node-discovery-failed/155653/6 "2018-11-09T02:05:27Z")

</div>

Docker Bridged mode binding host host IP failed, binding container IP causes cluster discovery failure.Just switch to host mode.

---

<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: [December 7, 2018, 2:05am UTC](https://discuss.elastic.co/t/cluster-node-discovery-failed/155653/7 "2018-12-07T02:05:31Z")

</div>

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