# Elastic Endpoint Security missing host

**URL:** <https://discuss.elastic.co/t/elastic-endpoint-security-missing-host/250420>\
**Category:** Endpoint Security\
**Created:** [September 29, 2020, 9:57pm UTC](https://discuss.elastic.co/t/elastic-endpoint-security-missing-host/250420 "2020-09-29T21:57:54Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![Kevin\_Logan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kevin_logan/32/74427_2.png) [@Kevin\_Logan](https://discuss.elastic.co/u/Kevin_Logan)\
**Post date:** [October 7, 2020, 4:09pm UTC](https://discuss.elastic.co/t/elastic-endpoint-security-missing-host/250420/18 "2020-10-07T16:09:59Z")

</div>

Hi @ManuelF

In order to restart the `elastic-endpoint`, you should be able to run: `sudo systemctl restart ElasticEndpoint` on Linux.

EDIT: in addition, you should run: `update-ca-certificates` to ensure that the Endpoint will recognize the new certs.

If this is still not working, try following the commands from this comment:

> [@Missing Elastic Security and endpoint integration data](https://discuss.elastic.co/t/missing-elastic-security-and-endpoint-integration-data/246601/16):
>
> FWIW, on an Ubuntu Linux VM, I was able to connect up an endpoint to elasticsearch using pki certificates. An issue I noticed was that I needed to restart endpoint in order for it to pick up changes in the system's trusted certificates. I ran the following two commands in a root shell to add the certificate: $ openssl pkcs12 -in certs/http.p12 -nokeys -out /usr/local/share/ca-certificates/elasticsearch-http.crt $ update-ca-certificates After restarting the endpoint, it was able to connect up …

As @ferullo has said, this could be a bug in the Endpoint restarting upon restart of the `elastic-agent`, so the steps you took will be helpful.

---

_[View the full topic](https://discuss.elastic.co/t/elastic-endpoint-security-missing-host/250420)._