# Fleet Server - Certificate Issues

**URL:** <https://discuss.elastic.co/t/fleet-server-certificate-issues/297749>\
**Category:** Beats\
**Tags:** elastic-agent\
**Created:** [February 21, 2022, 11:43am UTC](https://discuss.elastic.co/t/fleet-server-certificate-issues/297749 "2022-02-21T11:43:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![praveen\_raju](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/praveen_raju/32/81804_2.png) [@praveen\_raju](https://discuss.elastic.co/u/praveen_raju)\
**Post date:** [February 21, 2022, 11:43am UTC](https://discuss.elastic.co/t/fleet-server-certificate-issues/297749/1 "2022-02-21T11:43:13Z")

</div>

Hello

When i try to register Fleet Server using a certificate, it is getting successfully registered. But the problem is, it is throwing "Generating self-signed certificate for Fleet Server" after executing the command as shown below. This might be the reason when i try to register an VM to this Fleet Server using the certifictae i' am getting an exception "x509 certificate signed by unknown authority".

So trying to see if the root cause of the issue is "my fleet server" is not configured properly using CA certificate. Please help.

```auto
sudo ./elastic-agent install -f --url=https://XX1prdelkfleet01:8220 \
> --fleet-server-es=https://mo1prdelkmstr01:9200 \
> --fleet-server-service-token=AAEAAWVsYXN0aWMvZmxlZXQtc2VydmVyL3Rva2VuLTE2NDU0MzU3NTMwMjY6RmduZUU1RGNTeHlEb2lKVHdEVjRRZw \
> --fleet-server-policy=9de5f020-8e76-11ec-9794-bf083a8b07e7 \
> --certificate-authorities= /etc/ssl/certs/elkprd.crt \
> --fleet-server-es-ca= /tmp/elkprd.crt \
> --fleet-server-cert= /tmp/elkprd.crt \
> --fleet-server-cert-key= /tmp/elkprd.key
2022-02-21T06:34:43.470-0500	INFO	cmd/enroll_cmd.go:354	Generating self-signed certificate for Fleet Server
2022-02-21T06:34:45.887-0500	INFO	cmd/enroll_cmd.go:701	Fleet Server - Starting
2022-02-21T06:34:46.888-0500	INFO	cmd/enroll_cmd.go:682	Fleet Server - Running on policy with Fleet Server integration: 9de5f020-8e76-11ec-9794-bf083a8b07e7; missing config fleet.agent.id (expected during bootstrap process)
2022-02-21T06:34:47.692-0500	INFO	cmd/enroll_cmd.go:414	Starting enrollment to URL: https://mo1prdelkfleet01:8220/
2022-02-21T06:34:48.482-0500	INFO	cmd/enroll_cmd.go:252	Successfully triggered restart on running Elastic Agent.

```

---

<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 21, 2022, 1:43pm UTC](https://discuss.elastic.co/t/fleet-server-certificate-issues/297749/2 "2022-03-21T13:43:29Z")

</div>

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