# Enrollment Issue of fleet agent **URL:** \ **Category:** Endpoint Security\ **Tags:** fleet\ **Created:** [December 22, 2021, 8:57am UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655 "2021-12-22T08:57:11Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![MuhammadBilal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muhammadbilal/32/99742_2.png) [@MuhammadBilal](https://discuss.elastic.co/u/MuhammadBilal)\ **Post date:** [December 22, 2021, 8:57am UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655/1 "2021-12-22T08:57:12Z")
Hello, I m trying to integrate elastic endpoint security into my ELK stack, i have successfully install fleet and elastic agent to my endpoint but the issue is endpoint is not appearing in endpoint management in kibana. ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/8/d85dfe2544feb57280e01935581b8be9bac8a961.png) But endpoint is working fine it blocking threats showing alerts etc but not appearing in management so i can't isolate host through elastic endpoint . When i restart fleet agent the host appear in management but after 3 min they disappeared and show an error " [elastic\_agent][error] Could not communicate with fleet-server Checking API will retry, error: fail to checkin to fleet-server: Post "[https://x.x.x.x:8220/api/fleet/agents/4a94fbb2-5074-448d-9fc4-0da3154e8863/checkin?":](https://x.x.x.x:8220/api/fleet/agents/4a94fbb2-5074-448d-9fc4-0da3154e8863/checkin?%22:) dial tcp x.x.x.x:8220: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond." . There is no communication restriction between them. ---
**Author:** ![hendry.lim](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hendry.lim/32/71328_2.png) [@hendry.lim](https://discuss.elastic.co/u/hendry.lim)\ **Post date:** [December 29, 2021, 6:29am UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655/2 "2021-12-29T06:29:18Z")
Verify the host where you have the endpoint installed can connect to your Fleet server, e.g. `curl -k -v https://fleet-host:8220`. ---
**Author:** ![MuhammadBilal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muhammadbilal/32/99742_2.png) [@MuhammadBilal](https://discuss.elastic.co/u/MuhammadBilal)\ **Post date:** [January 3, 2022, 6:29am UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655/3 "2022-01-03T06:29:12Z")
Endpoint hosts are connected to fleet server. ---
**Author:** ![MuhammadBilal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muhammadbilal/32/99742_2.png) [@MuhammadBilal](https://discuss.elastic.co/u/MuhammadBilal)\ **Post date:** [January 3, 2022, 6:30am UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655/4 "2022-01-03T06:30:09Z")
I enrolled Windows OS as a fleet and it works fine but when I enrolled CentOS as a fleet with the same configuration it shows error. ---
**Author:** ![ferullo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ferullo/32/74240_2.png) [@ferullo](https://discuss.elastic.co/u/ferullo)\ **Post date:** [January 3, 2022, 2:00pm UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655/5 "2022-01-03T14:00:40Z")
Since Windows works by CentOS does not it sounds like this could be an SSL certificate issue. Are you using a self signed certificate for your Elastic stack? Can you reach Fleet using `curl -v https://fleet-host:8820`? ---
**Author:** ![MuhammadBilal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muhammadbilal/32/99742_2.png) [@MuhammadBilal](https://discuss.elastic.co/u/MuhammadBilal)\ **Post date:** [January 6, 2022, 12:06pm UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655/6 "2022-01-06T12:06:57Z")
Yes, I m using Self-signed certificate and able to reached curl -v [https://fleet-host:8220](https://fleet-host:8220) ---
**Author:** ![ferullo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ferullo/32/74240_2.png) [@ferullo](https://discuss.elastic.co/u/ferullo)\ **Post date:** [January 10, 2022, 3:40pm UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655/7 "2022-01-10T15:40:02Z")
Did you do anything so the Windows machines can reach Fleet? Either the self signed certificates certificate authority needs to be added to the host machines or your Fleet configuration needs to be modified to share the certificate or alter the SSL verification options. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 7, 2022, 3:40pm UTC](https://discuss.elastic.co/t/enrollment-issue-of-fleet-agent/292655/8 "2022-02-07T15:40:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.