# Fleet Server - Error - x509: certificate signed by unknown authority

**URL:** <https://discuss.elastic.co/t/fleet-server-error-x509-certificate-signed-by-unknown-authority/312923>\
**Category:** Elastic Agent\
**Tags:** elastic-stack-security, fleet\
**Created:** [August 25, 2022, 1:21pm UTC](https://discuss.elastic.co/t/fleet-server-error-x509-certificate-signed-by-unknown-authority/312923 "2022-08-25T13:21:59Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Kevin\_Clukey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_clukey/32/103075_2.png) [@Kevin\_Clukey](https://discuss.elastic.co/u/Kevin_Clukey)\
**Post date:** [August 25, 2022, 4:53pm UTC](https://discuss.elastic.co/t/fleet-server-error-x509-certificate-signed-by-unknown-authority/312923/7 "2022-08-25T16:53:44Z")

</div>

@ethical20

When enrolling an agent to fleet, you need to specify the CA that signed the fleet server certificate. This can be found in the documentation [here](https://www.elastic.co/guide/en/fleet/current/secure-connections.html) a the bottom of the page.

```auto
sudo elastic-agent install -f --url=https://192.0.2.1:8220 \
  --enrollment-token=<string> \
  --certificate-authorities=/path/to/ca.crt

```

---

_[View the full topic](https://discuss.elastic.co/t/fleet-server-error-x509-certificate-signed-by-unknown-authority/312923)._