# Elastic Agent Unhealthy - No valid comms client available **URL:** \ **Category:** Kibana\ **Created:** [March 26, 2024, 1:40am UTC](https://discuss.elastic.co/t/elastic-agent-unhealthy-no-valid-comms-client-available/356133 "2024-03-26T01:40:36Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Kreb](https://avatars.discourse-cdn.com/v4/letter/k/b5e925/32.png) [@Kreb](https://discuss.elastic.co/u/Kreb)\ **Post date:** [March 26, 2024, 1:40am UTC](https://discuss.elastic.co/t/elastic-agent-unhealthy-no-valid-comms-client-available/356133/1 "2024-03-26T01:40:36Z")
When I install the elastic agent onto a Ubuntu machine through Security Onion the device will check in as healthy for about 30 seconds and then it will go to an Unhealthy state. I have installed the agent on another Ubuntu machine and it never switches to this Unhealthy state. For some context this is for a school project and then way I've installed these agents is by connecting up to the Security Onion Console then downloading the Elastic agent that way. I make the installer executable then install it. This is what it is displaying in the logs over and over after initial setup and check-in: ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/b/1bad053b98a72b7787ff0fe5e773dcb925d87be3.jpeg) I have run the elastic-agent status command and it shows that it is Healthy and connected but that it is degraded. Not really sure where to go from here, I have found people with similar issues but not this exact one. Any help is appreciated. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 23, 2024, 1:41am UTC](https://discuss.elastic.co/t/elastic-agent-unhealthy-no-valid-comms-client-available/356133/2 "2024-04-23T01:41:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.