# FLeet-server

**URL:** <https://discuss.elastic.co/t/fleet-server/354475>\
**Category:** Elastic Agent\
**Tags:** fleet, filebeat, metricbeat\
**Created:** [February 29, 2024, 7:53pm UTC](https://discuss.elastic.co/t/fleet-server/354475 "2024-02-29T19:53:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![My\_Bach\_Toan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/my_bach_toan/32/132241_2.png) [@My\_Bach\_Toan](https://discuss.elastic.co/u/My_Bach_Toan)\
**Post date:** [February 29, 2024, 7:53pm UTC](https://discuss.elastic.co/t/fleet-server/354475/1 "2024-02-29T19:53:47Z")

</div>

When i tried to add elastic Agent to Windows host, this error happended

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/d/fd3a5f1636c0107ba3297803e270ec4a1aca06e0.png)

---

<div class="post-metadata">

**Author:** ![RLPowellJr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rlpowelljr/32/97049_2.png) [@RLPowellJr](https://discuss.elastic.co/u/RLPowellJr)\
**Post date:** [March 1, 2024, 2:55am UTC](https://discuss.elastic.co/t/fleet-server/354475/2 "2024-03-01T02:55:46Z")

</div>

Is this a cloud cluster, or self-managed? If self-managed, take a look at [Troubleshoot common problems | Fleet and Elastic Agent Guide [8.12] | Elastic](https://www.elastic.co/guide/en/fleet/current/fleet-troubleshooting.html#agent-enrollment-certs)

---

<div class="post-metadata">

**Author:** ![My\_Bach\_Toan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/my_bach_toan/32/132241_2.png) [@My\_Bach\_Toan](https://discuss.elastic.co/u/My_Bach_Toan)\
**Post date:** [March 1, 2024, 1:58pm UTC](https://discuss.elastic.co/t/fleet-server/354475/3 "2024-03-01T13:58:43Z")

</div>

This is a cluster. I have a Fleet Server on ubuntu and i want to add elastic agent to windows host ?? 🙏

---

<div class="post-metadata">

**Author:** ![RLPowellJr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rlpowelljr/32/97049_2.png) [@RLPowellJr](https://discuss.elastic.co/u/RLPowellJr)\
**Post date:** [March 1, 2024, 6:40pm UTC](https://discuss.elastic.co/t/fleet-server/354475/4 "2024-03-01T18:40:41Z")

</div>

If the cluster is running on your hardware, it's self-managed. What may be happening is the Agent's self-signed certificate, which is automatically generated, can't be verified by Fleet Server. The workaround is to add the `--insecure` option to the Agent installation string, like this Linux-based example:

`sudo ./elastic-agent install --url=https://<fleet-server-ip>:8220 --enrollment-token=<token> --insecure`

---

<div class="post-metadata">

**Author:** ![My\_Bach\_Toan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/my_bach_toan/32/132241_2.png) [@My\_Bach\_Toan](https://discuss.elastic.co/u/My_Bach_Toan)\
**Post date:** [March 1, 2024, 7:08pm UTC](https://discuss.elastic.co/t/fleet-server/354475/5 "2024-03-01T19:08:18Z")

</div>

I add --insecure and it is the result !

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/3/53c15a1f4cbf1f3b6fe10fb4ed475f46d12013c9.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 29, 2024, 7:08pm UTC](https://discuss.elastic.co/t/fleet-server/354475/6 "2024-03-29T19:08:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.