# Health and connection issues even though ES up and running

**URL:** <https://discuss.elastic.co/t/health-and-connection-issues-even-though-es-up-and-running/380781>\
**Category:** Elastic Search\
**Created:** [August 6, 2025, 5:50am UTC](https://discuss.elastic.co/t/health-and-connection-issues-even-though-es-up-and-running/380781 "2025-08-06T05:50:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![venkat\_tammi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkat_tammi/32/143884_2.png) [@venkat\_tammi](https://discuss.elastic.co/u/venkat_tammi)\
**Post date:** [August 6, 2025, 5:50am UTC](https://discuss.elastic.co/t/health-and-connection-issues-even-though-es-up-and-running/380781/1 "2025-08-06T05:50:04Z")

</div>

I am testing for health and connections for my elasticsearch cluster, even though, this service is up and running. Unfortunately, I am getting error message as **curl: (52) Empty reply from server**

* * *

# curl -u elasticsearch:elasticsearch -X GET "[http://localhost:9200/\_cat/nodes?pretty](http://localhost:9200/%5C_cat/nodes?pretty)"

## curl: (52) Empty reply from server

curl -v GET "[http://localhost:9200/\_cluster/health](http://localhost:9200/_cluster/health)"

- Rebuilt URL to: GET/
- Could not resolve host: GET
- Closing connection 0  
curl: (6) Could not resolve host: GET
- Trying xx.xx.xx.xxx...
- TCP\_NODELAY set
- Connected to xx.xx.xx.xxx (xx.xx.xx.xxx) port 9200 (#1)

> GET /\_cluster/health HTTP/1.1  
> Host: xx.xx.xx.xxx:9200  
> User-Agent: curl/7.61.1  
> Accept: _/_

- Empty reply from server
- Connection #1 to host xx.xx.xx.xxx left intact  
curl: (52) Empty reply from server

* * *

---

<div class="post-metadata">

**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:** [August 6, 2025, 6:00am UTC](https://discuss.elastic.co/t/health-and-connection-issues-even-though-es-up-and-running/380781/2 "2025-08-06T06:00:10Z")

</div>

Have you tried connecting over HTTPS?

---

<div class="post-metadata">

**Author:** ![venkat\_tammi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkat_tammi/32/143884_2.png) [@venkat\_tammi](https://discuss.elastic.co/u/venkat_tammi)\
**Post date:** [August 6, 2025, 10:03am UTC](https://discuss.elastic.co/t/health-and-connection-issues-even-though-es-up-and-running/380781/3 "2025-08-06T10:03:45Z")

</div>

Hello Christian\_Dahlqvist

Yes, I tried.

Unfortunately, I realized that I was passing wrong password. However, now everything is working as expected.

Thank you for your quick response.