# Beats in elastic-agent reporting "failed to connect to backoff"

**URL:** <https://discuss.elastic.co/t/beats-in-elastic-agent-reporting-failed-to-connect-to-backoff/299506>\
**Category:** Beats\
**Tags:** fleet, filebeat\
**Created:** [March 11, 2022, 11:42pm UTC](https://discuss.elastic.co/t/beats-in-elastic-agent-reporting-failed-to-connect-to-backoff/299506 "2022-03-11T23:42:34Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![trudyc](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@trudyc](https://discuss.elastic.co/u/trudyc)\
**Post date:** [March 18, 2022, 7:55pm UTC](https://discuss.elastic.co/t/beats-in-elastic-agent-reporting-failed-to-connect-to-backoff/299506/5 "2022-03-18T19:55:39Z")

</div>

There was a typo in my post concerning the work around:

> [@trudyc](#):
>
> In my Fleet Settings I had specified that the Elasticsearch hosts URL was https://:9200 but in these message it shows that it is trying to connect to [http://localhost:9200](http://localhost:9200)

That should say that in the Fleet Settings I had specified that the Elasticsearch hosts URL was [https://nlb-dns-name-from-aws:9200](https://nlb-dns-name-from-aws:9200)

---

_[View the full topic](https://discuss.elastic.co/t/beats-in-elastic-agent-reporting-failed-to-connect-to-backoff/299506)._