# Elasticsearch is running but not showing in ElasticHead

**URL:** <https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377>\
**Category:** Elasticsearch\
**Created:** [November 28, 2021, 9:49pm UTC](https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377 "2021-11-28T21:49:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![userR](https://avatars.discourse-cdn.com/v4/letter/u/22d042/32.png) [@userR](https://discuss.elastic.co/u/userR)\
**Post date:** [November 28, 2021, 9:49pm UTC](https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377/1 "2021-11-28T21:49:26Z")

</div>

Hi, I checked the status of Elasticsearch and everything indicates that it is running. However, when I try to connect to elastichead or even look up the ip:port, it does not connect. Is this some sort of port issue? My Elasticsearch.yml is posted below:

```auto
# Use a descriptive name for your cluster:
#
cluster.name: test-application
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: node-1
#
# 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: /var/lib/elasticsearch
#
# Path to log files:
#
path.logs: /var/log/elasticsearch
#
# ----------------------------------- 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 -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
network.host: xx.yyy.zz.aaa
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
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: ["xx.yyy.zz.aaa"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
cluster.initial_master_nodes: ["node-1"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true

```

xx.yyy.zz.aaa - substitute for real ip

---

<div class="post-metadata">

**Author:** ![DineshNaik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dineshnaik/32/89308_2.png) [@DineshNaik](https://discuss.elastic.co/u/DineshNaik)\
**Post date:** [November 29, 2021, 6:04am UTC](https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377/2 "2021-11-29T06:04:47Z")

</div>

@userR

How did you verify the status of Elasticsearch if you are not able to open  
`http://<ip>:<port>`

i will suggest you check the es logs once and see if any error. Share the logs here so that we can check if something is wrong.

---

<div class="post-metadata">

**Author:** ![userR](https://avatars.discourse-cdn.com/v4/letter/u/22d042/32.png) [@userR](https://discuss.elastic.co/u/userR)\
**Post date:** [November 29, 2021, 2:50pm UTC](https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377/3 "2021-11-29T14:50:24Z")

</div>

I ran systemctl status Elasticsearch and it shows as running.

There are no error logs since it started up with no issues

---

<div class="post-metadata">

**Author:** ![DineshNaik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dineshnaik/32/89308_2.png) [@DineshNaik](https://discuss.elastic.co/u/DineshNaik)\
**Post date:** [November 29, 2021, 4:40pm UTC](https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377/4 "2021-11-29T16:40:38Z")

</div>

check the output of these commands from your terminal and of possible share the details:

curl -XGET "http://:9200/\_cluster/health"

curl -XGET "http://:9200/\_cluster/stats"

replace the ip accordingly or use localhost if you are running it on the es server.

---

<div class="post-metadata">

**Author:** ![userR](https://avatars.discourse-cdn.com/v4/letter/u/22d042/32.png) [@userR](https://discuss.elastic.co/u/userR)\
**Post date:** [November 29, 2021, 5:31pm UTC](https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377/5 "2021-11-29T17:31:01Z")

</div>

I receive this error when I run the first command:

```auto
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Network Error (tcp_error)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
A communication error occurred: "Operation timed out"
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>

```

And this for the second command:

```auto
<HTML><HEAD>
<TITLE>Network Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Network Error (tcp_error)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
A communication error occurred: "Operation timed out"
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>

```

---

<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 29, 2021, 5:46pm UTC](https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377/6 "2021-11-29T17:46:40Z")

</div>

This does not seem to come from Elasticsearch but from a proxy.  
Check if you have a proxy.

---

<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 27, 2021, 5:47pm UTC](https://discuss.elastic.co/t/elasticsearch-is-running-but-not-showing-in-elastichead/290377/7 "2021-12-27T17:47:30Z")

</div>

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