--fleet-server-policy=id:5fa328c0-f635-11eb-b62c-2d3279f943d3 --fleet-server-es-ca=/etc/elastic-agent/certs/elasticsearch-ca.pem
Here the elastic-agent logs:
```auto
[...]
{"log.level":"info","@timestamp":"2021-08-24T15:40:05.115Z","log.origin":{"file.name":"stateresolver/stateresolver.go","file.line":48},"message":"New State ID is rEMABmG_","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:40:05.115Z","log.origin":{"file.name":"stateresolver/stateresolver.go","file.line":49},"message":"Converging state requires execution of 1 step(s)","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:40:05.158Z","log.origin":{"file.name":"operation/operator.go","file.line":259},"message":"operation 'operation-install' skipped for fleet-server.7.14.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:40:05.493Z","log.origin":{"file.name":"log/reporter.go","file.line":40},"message":"2021-08-24T17:40:05+02:00 - message: Application: fleet-server--7.14.0[]: State changed to STARTING: Starting - type: 'STATE' - sub_type: 'STARTING'","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:40:05.494Z","log.origin":{"file.name":"stateresolver/stateresolver.go","file.line":66},"message":"Updating internal state","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:42:04.574Z","log.origin":{"file.name":"cmd/run.go","file.line":189},"message":"Shutting down Elastic Agent and sending last events...","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:42:04.574Z","log.origin":{"file.name":"operation/operator.go","file.line":191},"message":"waiting for installer of pipeline 'default' to finish","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:42:04.574Z","log.origin":{"file.name":"process/app.go","file.line":181},"message":"Signaling application to stop because of shutdown: fleet-server--7.14.0","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:42:05.075Z","log.origin":{"file.name":"cmd/run.go","file.line":197},"message":"Shutting down completed.","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:42:05.075Z","log.origin":{"file.name":"log/reporter.go","file.line":40},"message":"2021-08-24T17:42:05+02:00 - message: Application: fleet-server--7.14.0[]: State changed to STOPPED: Stopped - type: 'STATE' - sub_type: 'STOPPED'","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2021-08-24T15:42:05.075Z","log.logger":"api","log.origin":{"file.name":"api/server.go","file.line":66},"message":"Stats endpoint (/var/lib/elastic-agent/data/tmp/elastic-agent.sock) finished: accept unix /var/lib/elastic-agent/data/tmp/elastic-agent.sock: use of closed network connection","ecs.version":"1.6.0"}
```
Could anyone give me some light?
Thanks in advance,
V
---
### Author:  [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [August 25, 2021, 7:38am UTC](https://discuss.elastic.co/t/fleet-server-does-not-start-properly/282380/2 "2021-08-25T07:38:14Z")
I'm stumbling over the following log line:
```auto
{"log.level":"info","service.name":"fleet-server","index":".fleet-policies","ctx":"index monitor","error.message":"elastic fail 500:exception:[service account role descriptor resolving] requires TLS for the HTTP interface","@timestamp":"2021-08-24T15:40:06.082Z","message":"exited"}
```
But I also see you are connecting through https to Elasticsearch is this correct? What is your TLS config in Elasticsearch?
---
### Author:  [@blaker](https://discuss.elastic.co/u/blaker)
#### Post date: [August 25, 2021, 1:39pm UTC](https://discuss.elastic.co/t/fleet-server-does-not-start-properly/282380/3 "2021-08-25T13:39:17Z")
@ruflin Could be possible that the HTTPS is managed by a HTTP reverse proxy and not by Elasticsearch and that is why that error is showing. Just a thought.
---
### Author:  [@Servando\_Dominguez](https://discuss.elastic.co/u/Servando_Dominguez)
#### Post date: [August 26, 2021, 12:59pm UTC](https://discuss.elastic.co/t/fleet-server-does-not-start-properly/282380/4 "2021-08-26T12:59:25Z")
Hi all,
@blaker There is no reverse proxy in that installation.
@ruflin I use the autogenerated certificates way. Here the configuration with the autogenerated certs of the master node:
```auto
xpack.security.enabled: true
xpack.security.transport.ssl.enabled: true
xpack.security.transport.ssl.verification_mode: full
xpack.security.transport.ssl.keystore.path: /etc/elasticsearch/certs/AVVLS-ELAST-001.p12
xpack.security.transport.ssl.truststore.path: /etc/elasticsearch/certs/elastic-stack-ca.p12
xpack.security.http.ssl.enabled: true
xpack.security.http.ssl.keystore.path: "/etc/elasticsearch/certs/http.p12"
```
The installation is in a rocky linux. I tried a clean installation with the same installation procedure and works properly. Maybe is an update issue.
---
### Author:  [@Servando\_Dominguez](https://discuss.elastic.co/u/Servando_Dominguez)
#### Post date: [August 29, 2021, 9:07pm UTC](https://discuss.elastic.co/t/fleet-server-does-not-start-properly/282380/5 "2021-08-29T21:07:58Z")
I did a new installation and migrate the data. We can close this case. The workaround was hard.
---
### Author:  [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [August 30, 2021, 7:17am UTC](https://discuss.elastic.co/t/fleet-server-does-not-start-properly/282380/6 "2021-08-30T07:17:11Z")
Sorry for the bumpy road @Servando_Dominguez The reinstall with all the same settings just worked?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 27, 2021, 7:17am UTC](https://discuss.elastic.co/t/fleet-server-does-not-start-properly/282380/7 "2021-09-27T07:17:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.