# Fleet Server is not Healthy

**URL:** <https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801>\
**Category:** Elastic Agent\
**Tags:** fleet\
**Created:** [August 12, 2024, 9:18pm UTC](https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801 "2024-08-12T21:18:48Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![rastro](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@rastro](https://discuss.elastic.co/u/rastro)\
**Post date:** [August 12, 2024, 9:18pm UTC](https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801/1 "2024-08-12T21:18:48Z")

</div>

This just started happening a few days ago. Neither pre-existing ("Cannot checkin in [sic] with fleet-server") nor new hosts ("Error: failed to enroll... 8220: connect: connection refused") can talk to fleet. Cannot curl 8220 on the fleet host using IP or localhost, either.

Restarted elastic and kibana on the fleet host with no change.

/var/log/messges has a Fleet Usage message that shows all enrolled hosts as "offline".

Any ideas?

---

<div class="post-metadata">

**Author:** ![rastro](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@rastro](https://discuss.elastic.co/u/rastro)\
**Post date:** [August 29, 2024, 1:16am UTC](https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801/2 "2024-08-29T01:16:40Z")

</div>

Anybody have any ideas? We're still fighting this issue!

---

<div class="post-metadata">

**Author:** ![rastro](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@rastro](https://discuss.elastic.co/u/rastro)\
**Post date:** [August 29, 2024, 4:10pm UTC](https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801/3 "2024-08-29T16:10:23Z")

</div>

Added #fleet

---

<div class="post-metadata">

**Author:** ![rastro](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@rastro](https://discuss.elastic.co/u/rastro)\
**Post date:** [August 29, 2024, 9:27pm UTC](https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801/4 "2024-08-29T21:27:49Z")

</div>

So, we had to upgrade to 8.15 for the kibana security issue. I created a new fleet server through the kibana UI and everything started working again.

So, who knows what happened, but we kicked it enough to get it working again. Very confidence building.

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [September 3, 2024, 7:04pm UTC](https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801/5 "2024-09-03T19:04:14Z")

</div>

Thanks, @rastro for sharing your solution here. Let us know if you have any further questions here.

---

<div class="post-metadata">

**Author:** ![rastro](https://avatars.discourse-cdn.com/v4/letter/r/b782af/32.png) [@rastro](https://discuss.elastic.co/u/rastro)\
**Post date:** [September 4, 2024, 1:42am UTC](https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801/6 "2024-09-04T01:42:02Z")

</div>

You missed the part where we didnt find a solution. Unless you introduced that kibana security issue to force us to upgrade...

Sigh.

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [September 4, 2024, 3:56am UTC](https://discuss.elastic.co/t/fleet-server-is-not-healthy/364801/7 "2024-09-04T03:56:49Z")

</div>

Thanks for following up, @rastro. Sorry about the confusion here; I misread this. What version did you upgrade from?