I have set up Elastic Search 2.3.0 as a service in an Azure VM with Windows Server 2012 R2. I can access elastic search instance from within the server using
I had the same case. Looking in the log
tail -f /var/log/elasticsearch/NODE.log
I saw this:
[NODE_NAME] publish_address {10.XXX.XXX.XXX:9300}, bound_addresses {10.XXX.XXX.XXX:9300}
[NODE_NAME] bound or publishing to a non-loopback address, enforcing bootstrap checks
[NODE_NAME] 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
[NODE_NAME] stopping ...
[NODE_NAME] stopped
Solution:
Modify the archive /etc/elasticsearch/elasticsearch.yml
in the line discorvery seed with this:
discovery.seed_hosts: ["127.0.0.1", "[::1]"]
Done.