# Unhelathy host **URL:** \ **Category:** Elastic Agent\ **Created:** [March 17, 2026, 1:26pm UTC](https://discuss.elastic.co/t/unhelathy-host/385494 "2026-03-17T13:26:01Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![a.thiome](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@a.thiome](https://discuss.elastic.co/u/a.thiome)\ **Post date:** [March 17, 2026, 1:26pm UTC](https://discuss.elastic.co/t/unhelathy-host/385494/1 "2026-03-17T13:26:01Z")
I recently installed the Elastic Stack and used Fleet to add hosts, but all Windows and Linux hosts appear as unhealthy. Has anyone else encountered this issue? ---
**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\ **Post date:** [March 17, 2026, 3:15pm UTC](https://discuss.elastic.co/t/unhelathy-host/385494/2 "2026-03-17T15:15:16Z")
Welcome @a.thiome! Do you have any errors or warnings in the logs? ---
**Author:** ![Rafa\_Silva](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rafa_silva/32/147814_2.png) [@Rafa\_Silva](https://discuss.elastic.co/u/Rafa_Silva)\ **Post date:** [March 18, 2026, 1:58am UTC](https://discuss.elastic.co/t/unhelathy-host/385494/3 "2026-03-18T01:58:58Z")
Welcome to the community It’s hard to be precise without logs, but when all hosts show as unhealthy, it’s usually something systemic. A few things worth checking: Elastic Agent service is running properly on the hosts connectivity to Fleet Server (network, DNS, URL) Fleet Server itself is healthy TLS/certificate issues (very common in fresh setups) agent successfully enrolled and assigned to a policy firewall/proxy blocking traffic (especially 8220 / 9200) version compatibility between Agent, Fleet Server, and Elasticsearch If you can share the Elastic Agent or Fleet Server logs, that will help pinpoint the exact issue quickly.