# Heartbeat-elastic site monitoring error (Web down)

**URL:** <https://discuss.elastic.co/t/heartbeat-elastic-site-monitoring-error-web-down/184112>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [June 4, 2019, 8:23am UTC](https://discuss.elastic.co/t/heartbeat-elastic-site-monitoring-error-web-down/184112 "2019-06-04T08:23:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![skyluke.1987](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@skyluke.1987](https://discuss.elastic.co/u/skyluke.1987)\
**Post date:** [June 4, 2019, 8:23am UTC](https://discuss.elastic.co/t/heartbeat-elastic-site-monitoring-error-web-down/184112/1 "2019-06-04T08:23:43Z")

</div>

Error Msg:  
Head [https://xx.org/:](https://xx.org/:) dial tcp 202.xx.xx.xx:443: i/o timeout (Client.Timeout exceeded while awaiting headers)

May I know does anyone faced this before? Which part has caused this issue? Is it Uptime service / configuration itself or is it on the application we are monitoring?

Thanks ~

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [June 4, 2019, 5:47pm UTC](https://discuss.elastic.co/t/heartbeat-elastic-site-monitoring-error-web-down/184112/2 "2019-06-04T17:47:50Z")

</div>

This error means that the endpoint you're trying to reach did not respond. That could be due to any number of issues. Either network related, permissions related, or software related.

---

<div class="post-metadata">

**Author:** ![skyluke.1987](https://avatars.discourse-cdn.com/v4/letter/s/48db29/32.png) [@skyluke.1987](https://discuss.elastic.co/u/skyluke.1987)\
**Post date:** [June 6, 2019, 3:07am UTC](https://discuss.elastic.co/t/heartbeat-elastic-site-monitoring-error-web-down/184112/3 "2019-06-06T03:07:18Z")

</div>

Hi so far we have found that there is some connection issue that causes this due to hopping from servers to server. Currently the default heartbeat is listening to a server.

Internal server (Public IP) connecting to GoDaddy server and this does not capture even the site is online.

---

<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 4, 2019, 3:07am UTC](https://discuss.elastic.co/t/heartbeat-elastic-site-monitoring-error-web-down/184112/4 "2019-07-04T03:07:20Z")

</div>

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