Can't open ElasticSearch on browser from outside the server

Hi ,
I'm new with ES I've installed it from the official site on an Azure VM with Centos 7 System, it's successfully installed, when I start the service it started correctly, and when I check the availability of ES, using this command: curl http://localhost:9200 it seems everything is good, the problem is when I open the link in a browser using myAzureVMipAdress:9200, I get nothing! , I've tried to make some changes on elasticsearch. yml, changing the network. host to 127.0.0.1 I get the same problem :slightly_frowning_face: and changing the http. host to 0.0.0.0, nothing happened.
Please if any one can help , and thank you so much :slightly_smiling_face:

bellow my elasticsearsh.yml file :

# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
#       Before you set out to tweak and tune the configuration, make sure you
#       understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: EFK_cluster
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: EFK_node
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
#path.data: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
#------------------------------------------
#network.host: 127.0.0.1
#http.host: 0.0.0.0
#------------------------------------------

#network.bind_host: ["10.2.0.4","13.80.56.156"]
#network.publish_host: 10.2.0.4
#
# Set a custom port for HTTP:
#
#http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
#gateway.recover_after_nodes: 3
#
# For more information, consult the gateway module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true
discovery.type: single-node

Hello,

I invite you to edit the message and use the markdown formatting for code or configuration snippets.

I think there are several problems.

Except if you have a VPN towards your azure VM, you will need a public IP to access it (azure doc).

In addition, you will need to listen on a public IP for HTTP (Transport is not necessary) with http.host.

But before doing this, we strongly encourage to install a basic license and enable Authentication and authorization and TLS, as they're free.
Follow those steps: https://www.elastic.co/guide/en/elasticsearch/reference/current/ssl-tls.html

If you intend using Kibana, it is not necessary to expose Elasticsearch to the public as Kibana will be your entry point to the Elastic stack.

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