# Is there a way to ease installing fleet server to a elasticsearch server secured by self-signed certificate

**URL:** <https://discuss.elastic.co/t/is-there-a-way-to-ease-installing-fleet-server-to-a-elasticsearch-server-secured-by-self-signed-certificate/281583>\
**Category:** Elastic Observability\
**Tags:** fleet\
**Created:** [August 16, 2021, 6:08pm UTC](https://discuss.elastic.co/t/is-there-a-way-to-ease-installing-fleet-server-to-a-elasticsearch-server-secured-by-self-signed-certificate/281583 "2021-08-16T18:08:19Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![blaker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/blaker/32/65621_2.png) [@blaker](https://discuss.elastic.co/u/blaker)\
**Post date:** [August 18, 2021, 4:48pm UTC](https://discuss.elastic.co/t/is-there-a-way-to-ease-installing-fleet-server-to-a-elasticsearch-server-secured-by-self-signed-certificate/281583/5 "2021-08-18T16:48:25Z")

</div>

Read the discussion here, it describes how the output settings must be configured in the Fleet settings flyout in Kibana.

> [@7.14 - Windows agent deployed with Fleet, but not sending data](https://discuss.elastic.co/t/7-14-windows-agent-deployed-with-fleet-but-not-sending-data/281347/2):
>
> The issue is that using --insecure only allow Elastic Agent to communicate with Fleet Server insecurely. It still takes the settings from the policy to communicate with Elasticsearch. You need to modify the output settings inside the Fleet UI in Kibana. You will want to add the following in the Elasticsearch output configuration (YAML) block: ssl.verification\_mode: none

---

_[View the full topic](https://discuss.elastic.co/t/is-there-a-way-to-ease-installing-fleet-server-to-a-elasticsearch-server-secured-by-self-signed-certificate/281583)._