# Filebeat ssl issue

**URL:** https://discuss.elastic.co/t/filebeat-ssl-issue/300984
**Category:** Beats
**Tags:** filebeat
**Created:** [March 29, 2022, 2:45pm UTC](https://discuss.elastic.co/t/filebeat-ssl-issue/300984 "2022-03-29T14:45:30Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![alaine](https://avatars.discourse-cdn.com/v4/letter/a/22d042/32.png) [@alaine](https://discuss.elastic.co/u/alaine)
#### Post date: [March 29, 2022, 2:45pm UTC](https://discuss.elastic.co/t/filebeat-ssl-issue/300984/1 "2022-03-29T14:45:30Z")

</div>

Hello,

I ran into a weird issue where I was getting the following error on one of my logstash servers as I was trying to set up filebeats:

```auto
ERROR [esclientleg] transport/logging.go:37 Error dialing x509: Certificate signed by unknown authority {"network": "tcp", "address": "<hostname:443>"

```

By adding the following syntax I was able to solve the problem, but now I have slightly different configs and I am not sure why:

```auto
output.elasticsearch.ssl.certificate_authorities: ["path to CA file"]

```

What has me confused is that I have metricbeat running on the same host without having to add that syntax. I also copied these configs directly from another host that is working without having to add that syntax as well.

Thanks for any thoughts,  
Alex

---

<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: [April 26, 2022, 4:46pm UTC](https://discuss.elastic.co/t/filebeat-ssl-issue/300984/2 "2022-04-26T16:46:18Z")

</div>

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