# Elasticsearch ca certificate problem
**URL:** https://discuss.elastic.co/t/elasticsearch-ca-certificate-problem/304108
**Category:** Beats
**Tags:** filebeat
**Created:** [May 6, 2022, 9:36am UTC](https://discuss.elastic.co/t/elasticsearch-ca-certificate-problem/304108 "2022-05-06T09:36:10Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@uaygun](https://discuss.elastic.co/u/uaygun)
#### Post date: [May 6, 2022, 9:36am UTC](https://discuss.elastic.co/t/elasticsearch-ca-certificate-problem/304108/1 "2022-05-06T09:36:11Z")
Hi guys;
I have a wazuh server with running filebeat and Elasticsearch. When i am trying to establish a connection from remote filebeat to my Elasticsearch i am getting "Exiting: error loading config file: yaml: line 139: did not find expected key" error. I tried to solve this problem with some answers from community but i couldnt get the ca\_trusted\_fingerprint and i do not now how to get it
Can anyone help me 🙂
P.S: I tried below solution but as i said i could not get ca fingerprint.
When you start Elasticsearch for the first time it will log the value for `ca_trusted_fingerprint` .
If the auto-configuration process has already completed, you can follow [those steps](https://www.elastic.co/guide/en/elasticsearch/reference/8.0/configuring-stack-security.html#_use_the_ca_fingerprint_5) to get the CA fingerprint
and i tried [this link](https://www.elastic.co/guide/en/elasticsearch/reference/8.0/configuring-stack-security.html#_use_the_ca_fingerprint_5) but still no luck
And this is my Elasticsearch.yml file
```auto
output.elasticsearch.hosts: ["10.72.81.11:9200"]
username: "wazuh"
password: "password"
# Protocol - either `http` (default) or `https`.
protocol: "https"
ssl:
enabled: true
ca_trusted_fingerprint: ????
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 3, 2022, 9:37am UTC](https://discuss.elastic.co/t/elasticsearch-ca-certificate-problem/304108/2 "2022-06-03T09:37:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.