# Unable to install Fleet Server

**URL:** <https://discuss.elastic.co/t/unable-to-install-fleet-server/318255>\
**Category:** Elastic Agent\
**Tags:** fleet\
**Created:** [November 6, 2022, 9:36am UTC](https://discuss.elastic.co/t/unable-to-install-fleet-server/318255 "2022-11-06T09:36:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![themetman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/themetman/32/112991_2.png) [@themetman](https://discuss.elastic.co/u/themetman)\
**Post date:** [November 6, 2022, 9:36am UTC](https://discuss.elastic.co/t/unable-to-install-fleet-server/318255/1 "2022-11-06T09:36:24Z")

</div>

I am new to Elastic Stack, but well over 20 years as a Linux (Gentoo) User. I have set up Elasticsearch, Kibana and Logstash using https on a Virtualbox system with 2 Linux Servers. I now have Elasticsearch and Kibana on one machine and Logstash on another on my home network using Self Signed Certs. This is working.  
I am trying to install Fleet Server onto the Logstash Server running RHEL8 from the Kibana/Elasticsearch Interface on an aarm64 device. I have tried both the 'Quick' and 'Advanced' methods, and they both fail with this error:

```auto
"Fleet Server - Error - x509: certificate signed by unknown authority","ecs.version":"1.6.0"}
Error: fleet-server failed: context canceled

```

Here is my install command from the Advanced Interface

```auto
sudo ./elastic-agent install -v --url=https://<LOGSTASH_SERVER>:8220 \
 --fleet-server-es=https://<ELASTIC_SERVER_IP>:9200 \
 --fleet-server-service-token=AAEAAWVsYXN0aWMvZmxlZXQtc2VydmVyL3Rva2VuLTE2Njc3MjEzOTAyMDQ6bjZ5ckk4Ry1RWVNTdUtpX05NU3hQdw \
--fleet-server-policy=fleet-server-policy \
--fleet-server-es-ca-trusted-fingerprint=508D7EF87489AEBDCCB68E5692E6836F01A1FD004590A1FCD21BDC2D6A112831 \
--insecure

```

I have tried this with and without the --insecure flag. Same problem.  
I have tried with my own certs and letting the installer create it's own certs, but I get the same error.  
I have tried the -v switch to get more output to help solve this, but I do not get anything to help. There is nothing in the /var/log/messages.  
Help would be much appreciated.

---

<div class="post-metadata">

**Author:** ![Cristina\_Amico](https://avatars.discourse-cdn.com/v4/letter/c/9fc29f/32.png) [@Cristina\_Amico](https://discuss.elastic.co/u/Cristina_Amico)\
**Post date:** [November 8, 2022, 11:39am UTC](https://discuss.elastic.co/t/unable-to-install-fleet-server/318255/2 "2022-11-08T11:39:34Z")

</div>

Hi @themetman,

Can I ask you which version of the stack are you running?

Also, could you try adding the `--fleet-server-es-insecure` flag to your command and posting the logs if it doesn't work?

---

<div class="post-metadata">

**Author:** ![themetman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/themetman/32/112991_2.png) [@themetman](https://discuss.elastic.co/u/themetman)\
**Post date:** [November 8, 2022, 12:33pm UTC](https://discuss.elastic.co/t/unable-to-install-fleet-server/318255/3 "2022-11-08T12:33:59Z")

</div>

Thanks for taking the time to reply, @Cristina_Amico. I am using version 8.5.0.  
Since posting I reinstalled everything with fresh certs & keys etc, and I now have it up and running. I used the --insecure flag which worked.  
Regards

---

<div class="post-metadata">

**Author:** ![Cristina\_Amico](https://avatars.discourse-cdn.com/v4/letter/c/9fc29f/32.png) [@Cristina\_Amico](https://discuss.elastic.co/u/Cristina_Amico)\
**Post date:** [November 8, 2022, 1:31pm UTC](https://discuss.elastic.co/t/unable-to-install-fleet-server/318255/4 "2022-11-08T13:31:01Z")

</div>

No problem! I'm glad it worked.

---

<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:** [December 6, 2022, 1:31pm UTC](https://discuss.elastic.co/t/unable-to-install-fleet-server/318255/5 "2022-12-06T13:31:27Z")

</div>

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