# Zen discovery not working **URL:** \ **Category:** Elasticsearch\ **Created:** [June 13, 2017, 7:44am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152 "2017-06-13T07:44:18Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![Tamizh](https://avatars.discourse-cdn.com/v4/letter/t/8c91f0/32.png) [@Tamizh](https://discuss.elastic.co/u/Tamizh)\ **Post date:** [June 13, 2017, 7:44am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/1 "2017-06-13T07:44:18Z")
When I try to add a node to my single node cluster. These are my node configurations ``` Node - 1 cluster.name: node.name: discovery.zen.ping.unicast.hosts: ["127.0.0.1:9300", ":9300"] discovery.zen.minimum_master_nodes: 1 Node - 2 cluster.name: node.name: discovery.zen.ping.unicast.hosts: ["127.0.0.1:9300", ":9300"] discovery.zen.minimum_master_nodes: 1 ``` Both get started but not getting connected. ``` [2017-06-13T06:33:14,232][INFO][o.e.t.TransportService] [Q-ZXfxh] publish_address {127.0.0.1:9300}, bound_addresses {[::1]:9300}, {127.0.0.1:9300} [2017-06-13T06:33:17,398][INFO][o.e.c.s.ClusterService] [Q-ZXfxh] new_master {Q-ZXfxh}{Q- ZXfxhxQaOLkvT5SojlmQ}{mNwfOVNRQaiKCrE-s_5m0g}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined) [2017-06-13T06:33:17,455][INFO][o.e.h.HttpServer] [Q-ZXfxh] publish_address {127.0.0.1:9200}, bound_addresses {[::1]:9200}, {127.0.0.1:9200} [2017-06-13T06:33:17,456][INFO][o.e.n.Node] [Q-ZXfxh] started [2017-06-13T06:33:17,702][INFO][o.e.g.GatewayService] [Q-ZXfxh] recovered [1] indices into cluster_state [2017-06-13T06:33:18,059][INFO][o.e.c.r.a.AllocationService] [Q-ZXfxh] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[.kibana][0]] ...]). ``` ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 13, 2017, 7:47am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/2 "2017-06-13T07:47:47Z")
> [@Tamizh](#): > > [2017-06-13T06:33:14,232][INFO][o.e.t.TransportService] [Q-ZXfxh] publish\_address > {127.0.0.1:9300}, bound\_addresses {[::1]:9300}, {127.0.0.1:9300} Looks like your node binds to localhost, which is not reachable from outside. Change `network.host` to `0.0.0.0` or the external IP of the host. ---
**Author:** ![Tamizh](https://avatars.discourse-cdn.com/v4/letter/t/8c91f0/32.png) [@Tamizh](https://discuss.elastic.co/u/Tamizh)\ **Post date:** [June 13, 2017, 8:01am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/3 "2017-06-13T08:01:03Z")
I changed my configuration as follows ``` Node - 1 cluster.name: node.name: network.host: discovery.zen.ping.unicast.hosts: ["127.0.0.1:9300", ":9300"] discovery.zen.minimum_master_nodes: 1 Node - 2 cluster.name: node.name: network.host: discovery.zen.ping.unicast.hosts: ["127.0.0.1:9300", ":9300"] discovery.zen.minimum_master_nodes: 1 ``` But still, i got the following error. ``` org.elasticsearch.transport.BindTransportException: Failed to bind to [9300-9400] at org.elasticsearch.transport.TcpTransport.bindToPort(TcpTransport.java:626) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.transport.TcpTransport.bindServer(TcpTransport.java:591) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.transport.netty4.Netty4Transport.doStart(Netty4Transport.java:182) ~[?:?] at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:68) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.transport.TransportService.doStart(TransportService.java:182) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:68) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.node.Node.start(Node.java:525) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:211) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:288) [elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:112) [elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:103) [elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.cli.SettingCommand.execute(SettingCommand.java:54) [elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:96) [elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.cli.Command.main(Command.java:62) [elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) [elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:73) [elasticsearch-5.0.0.jar:5.0.0] Caused by: java.net.BindException: Cannot assign requested address at sun.nio.ch.Net.bind0(Native Method) ~[?:?] at sun.nio.ch.Net.bind(Net.java:433) ~[?:?] at sun.nio.ch.Net.bind(Net.java:425) ~[?:?] at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[?:?] at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:127) ~[?:?] at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:554) ~[?:?] at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1258) ~[?:?] at io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:511) ~[?:?] at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:496) ~[?:?] at io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:980) ~[?:?] at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:250) ~[?:?] at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:363) ~[?:?] at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) ~[?:?] at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418) ~[?:?] at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440) ~[?:?] at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) ~[?:?] at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_131] [2017-06-13T07:52:36,144][WARN][o.e.b.ElasticsearchUncaughtExceptionHandler] [] uncaught exception in thread [main] org.elasticsearch.bootstrap.StartupException: BindTransportException[Failed to bind to [9300-9400]]; nested: BindException[Cannot assign requested address]; at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:116) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:103) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.cli.SettingCommand.execute(SettingCommand.java:54) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:96) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.cli.Command.main(Command.java:62) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:80) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:73) ~[elasticsearch-5.0.0.jar:5.0.0] Caused by: org.elasticsearch.transport.BindTransportException: Failed to bind to [9300-9400] at org.elasticsearch.transport.TcpTransport.bindToPort(TcpTransport.java:626) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.transport.TcpTransport.bindServer(TcpTransport.java:591) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.transport.netty4.Netty4Transport.doStart(Netty4Transport.java:182) ~[?:?] at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:68) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.transport.TransportService.doStart(TransportService.java:182) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:68) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.node.Node.start(Node.java:525) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:211) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:288) ~[elasticsearch-5.0.0.jar:5.0.0] at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:112) ~[elasticsearch-5.0.0.jar:5.0.0] ... 6 more ``` ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 13, 2017, 8:05am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/4 "2017-06-13T08:05:22Z")
`network.host` on node 1 should be ``, which should be the same as ``. If both nodes are master eligible, `minimum_master_nodes` should be set to 2 in order to prevent split-brain scenarios. ---
**Author:** ![Tamizh](https://avatars.discourse-cdn.com/v4/letter/t/8c91f0/32.png) [@Tamizh](https://discuss.elastic.co/u/Tamizh)\ **Post date:** [June 13, 2017, 8:24am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/5 "2017-06-13T08:24:49Z")
Thanks for the solution. it worked. Still, i have some question that I want to ask. 1. why I can't access my elasticsearch from my localhost. After change host to my localhost IP address. What is the difference between the empty `network.host` to `node-ip` `network.host`. The following the startup log of elasticsearch ``` [2017-06-13T08:15:07,508][INFO][o.e.c.s.ClusterService] [Q-ZXfxh] detected_master {MhnGR-D}{MhnGR-DSRyi3kfcR8w9KvQ}{8444RarNRSW1rWTsiEi8Mg}{139.162.34.250}{139.162.34.250:9300}, added {{MhnGR-D}{MhnGR-DSRyi3kfcR8w9KvQ}{8444RarNRSW1rWTsiEi8Mg}{139.162.34.250}{139.162.34.250:9300},}, reason: zen-disco-receive(from master [master {MhnGR-D}{MhnGR-DSRyi3kfcR8w9KvQ}{8444RarNRSW1rWTsiEi8Mg}{139.162.34.250}{139.162.34.250:9300} committed version [1]]) [2017-06-13T08:15:07,544][INFO][o.e.h.HttpServer] [Q-ZXfxh] publish_address {172.104.50.221:9200}, bound_addresses {172.104.50.221:9200} [2017-06-13T08:15:07,544][INFO][o.e.n.Node] [Q-ZXfxh] started [2017-06-13T08:15:07,821][WARN][o.e.g.DanglingIndicesState] [Q-ZXfxh] [[.kibana/ph_lW1xWT2CClFUPw-525w]] can not be imported as a dangling index, as index with same name already exists in cluster metadata [2017-06-13T08:15:07,866][WARN][o.e.g.DanglingIndicesState] [Q-ZXfxh] [[.kibana/ph_lW1xWT2CClFUPw-525w]] can not be imported as a dangling index, as index with same name already exists in cluster metadata [2017-06-13T08:15:08,044][WARN][o.e.g.DanglingIndicesState] [Q-ZXfxh] [[.kibana/ph_lW1xWT2CClFUPw-525w]] can not be imported as a dangling index, as index with same name already exists in cluster metadata [2017-06-13T08:15:08,297][WARN][o.e.g.DanglingIndicesState] [Q-ZXfxh] [[.kibana/ph_lW1xWT2CClFUPw-525w]] can not be imported as a dangling index, as index with same name already exists in cluster metadata [2017-06-13T08:15:08,638][WARN][o.e.g.DanglingIndicesState] [Q-ZXfxh] [[.kibana/ph_lW1xWT2CClFUPw-525w]] can not be imported as a dangling index, as index with same name already exists in cluster metadata ``` 1. From this log, i have one more concern. What about the dangling index and what it will cause. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 13, 2017, 8:40am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/6 "2017-06-13T08:40:58Z")
Set `network.host` to `0.0.0.0` to bind to all interfaces. ---
**Author:** ![Tamizh](https://avatars.discourse-cdn.com/v4/letter/t/8c91f0/32.png) [@Tamizh](https://discuss.elastic.co/u/Tamizh)\ **Post date:** [June 13, 2017, 8:48am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/7 "2017-06-13T08:48:35Z")
Really thanks for your help. I was struggling with this last two days. But I don't want to put `network.host` to `0.0.0.0`. If I give like that, anybody can access my IP. So I will add Nginx in my node and port forward to access my elasticsearch. Is this the right way ?? ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 13, 2017, 9:00am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/8 "2017-06-13T09:00:39Z")
Nginx will not work for the transport protocol, which Elasticsearch uses to communicate between nodes. You may however be able to limit access to port 9300 from the outside using e.g .iptables. ---
**Author:** ![Tamizh](https://avatars.discourse-cdn.com/v4/letter/t/8c91f0/32.png) [@Tamizh](https://discuss.elastic.co/u/Tamizh)\ **Post date:** [June 13, 2017, 9:20am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/9 "2017-06-13T09:20:34Z")
currently, i secure my elasticsearch and kibana API with basic authentication using Nginx. Because of I am adding a new node, I can't compromise with security. So is there any way to make both possible. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 13, 2017, 9:26am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/10 "2017-06-13T09:26:43Z")
Securing port 9300 through IP tables so that it is only accessible from the other node does not need to change the rest of your setup as you can [configure HTTP to bind to a different host](https://www.elastic.co/guide/en/elasticsearch/reference/5.4/modules-http.html), e.g. localhost. ---
**Author:** ![Tamizh](https://avatars.discourse-cdn.com/v4/letter/t/8c91f0/32.png) [@Tamizh](https://discuss.elastic.co/u/Tamizh)\ **Post date:** [June 13, 2017, 11:07am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/11 "2017-06-13T11:07:04Z")
`iptables -I INPUT -p tcp ! -s --dport 9300 -j DROP` After I gave the command `iptables -L` ``` Chain INPUT (policy ACCEPT) target prot opt source destination DROP tcp -- !li1447-250.members.linode.com anywhere tcp dpt:9300 Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ``` I gave `network.publish_host: ` and comment the `network.host` so that it can only connect from localhost and I can use Nginx over it. But the `network.publish_host` not working as I expect. so what I am doing wrong here ?? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 11, 2017, 11:07am UTC](https://discuss.elastic.co/t/zen-discovery-not-working/89152/12 "2017-07-11T11:07:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.