# Heartbeat showing Down even the port is working when autodiscovery of Docker Host Port and IP's

**URL:** https://discuss.elastic.co/t/heartbeat-showing-down-even-the-port-is-working-when-autodiscovery-of-docker-host-port-and-ips/307568
**Category:** Beats
**Tags:** docker, heartbeat
**Created:** [June 18, 2022, 3:27pm UTC](https://discuss.elastic.co/t/heartbeat-showing-down-even-the-port-is-working-when-autodiscovery-of-docker-host-port-and-ips/307568 "2022-06-18T15:27:01Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![itssenthil](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@itssenthil](https://discuss.elastic.co/u/itssenthil)
#### Post date: [June 18, 2022, 3:27pm UTC](https://discuss.elastic.co/t/heartbeat-showing-down-even-the-port-is-working-when-autodiscovery-of-docker-host-port-and-ips/307568/1 "2022-06-18T15:27:01Z")

</div>

Hey Elastic Team, Good Day, I'm done the configurations to autodiscovery of Heartbeat, and also it discovers the port, but the some of the up status ports in realtime in docker showing down from the beginning in the Heartbeat, Can you please help me figure out what could be issue, Attaching Screenshot FYI.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/6/46ba4cd0c25b7cda84f61077f03b096037f441e7.png)

---

<div class="post-metadata">

### Author: ![itssenthil](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@itssenthil](https://discuss.elastic.co/u/itssenthil)
#### Post date: [June 18, 2022, 5:53pm UTC](https://discuss.elastic.co/t/heartbeat-showing-down-even-the-port-is-working-when-autodiscovery-of-docker-host-port-and-ips/307568/2 "2022-06-18T17:53:48Z")

</div>

Anybody here?

---

<div class="post-metadata">

### Author: ![kyungeunni](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kyungeunni/32/125539_2.png) [@kyungeunni](https://discuss.elastic.co/u/kyungeunni)
#### Post date: [June 20, 2022, 9:42am UTC](https://discuss.elastic.co/t/heartbeat-showing-down-even-the-port-is-working-when-autodiscovery-of-docker-host-port-and-ips/307568/3 "2022-06-20T09:42:30Z")

</div>

Hi @itssenthil,

I can see the error message from your screenshot:

> dial TCP 172.18.0.15:6650: connect: connection refused

Could you check if your heartbeat container has network access to the target service?

---

<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: [July 18, 2022, 11:42am UTC](https://discuss.elastic.co/t/heartbeat-showing-down-even-the-port-is-working-when-autodiscovery-of-docker-host-port-and-ips/307568/4 "2022-07-18T11:42:52Z")

</div>

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