ElasticSearch instance not reachable from outside the server - Azure Windows 2012

Question

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

Answer 1

I would suggest to set the network.host to special values

eg.

network.host: [_local_, _site_]

This works for me.

Answer 2

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.

Answer 3

Please note that for me success was achieved only after setting

http.host: 0.0.0.0

instead of

http.host: "localhost"

Answer 4

Starting with ES 2.0, the elasticsearch process only binds to localhost, which explains why you can query ES from inside but not from the outside.

You need to change the following setting in your elasticsearch.yml configuration file:

network.host: 0.0.0.0

Answer 5

Resolved for me on Windows server 2012 with Elasticsearch 7.1.1 adding in C:\ProgramData\Elastic\Elasticsearch\config\elasticsearch.yml the following config:

http.host: 0.0.0.0