Fleet Server is not Healthy

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?

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

Added fleet

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.

1 Like

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

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

Sigh.

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