# Filebeat: Error on Windows\* with SSL Certificates

**URL:** <https://discuss.elastic.co/t/filebeat-error-on-windows-with-ssl-certificates/134559>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 5, 2018, 8:20am UTC](https://discuss.elastic.co/t/filebeat-error-on-windows-with-ssl-certificates/134559 "2018-06-05T08:20:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![SimonSays4223](https://avatars.discourse-cdn.com/v4/letter/s/ac8455/32.png) [@SimonSays4223](https://discuss.elastic.co/u/SimonSays4223)\
**Post date:** [June 5, 2018, 8:20am UTC](https://discuss.elastic.co/t/filebeat-error-on-windows-with-ssl-certificates/134559/1 "2018-06-05T08:20:44Z")

</div>

Hello @all,

I'm trying to configure filebeat on a Win7 and Win10 machine with SSL-Certificates. After configuring it as described:

```
   output.logstash
     hosts: ["mylogstaship:myport"]
     ssl.certificate_authorities: ["C:\filebeat-6.2.4-windows-x86_64\myrootca.crt"]
     ssl.certificate: "C:\filebeat-6.2.4-windows-x86_64\myclientcert.crt"
     ssl.key: "C:\filebeat-6.2.4-windows-x86_64\myclientkey.key"

```

I'm getting the following error:

> The service filebeat cannot be startetd. Error 1053 ...

It always appears if I have a config mistake. When commenting the ssl-lines out, it works.

Seems to be the same issue as:  
[https://discuss.elastic.co/t/filebeat-on-windows-ssl-certificates/125333/2](https://discuss.elastic.co/t/filebeat-on-windows-ssl-certificates/125333/2)

Since it has not been solved yet, I think the bug still exists. Unfortunately there is no logentry in the filebeat logging mechanism (event on debug) that could indicate why the config cannot be parsed.

PS: The same config on a CentOS6 and CentOS7 host just works fine.

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [June 5, 2018, 8:56am UTC](https://discuss.elastic.co/t/filebeat-error-on-windows-with-ssl-certificates/134559/2 "2018-06-05T08:56:23Z")

</div>

Hi @SimonSays4223,

Welcome to the discuss forum 🙂

~~The configuration looks good~~. Could you check the filebeat logs to see if it is reporting any error there?

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [June 5, 2018, 9:03am UTC](https://discuss.elastic.co/t/filebeat-error-on-windows-with-ssl-certificates/134559/3 "2018-06-05T09:03:50Z")

</div>

Could you try to scape the path separators? Like this:

```auto
   output.logstash
     hosts: ["mylogstaship:myport"]
     ssl.certificate_authorities: ["C:\\filebeat-6.2.4-windows-x86_64\\myrootca.crt"]
     ssl.certificate: "C:\\filebeat-6.2.4-windows-x86_64\\myclientcert.crt"
     ssl.key: "C:\\filebeat-6.2.4-windows-x86_64\\myclientkey.key"

```

You can also use single quoutes instead:

```auto
   output.logstash
     hosts: ['mylogstaship:myport']
     ssl.certificate_authorities: ['C:\filebeat-6.2.4-windows-x86_64\myrootca.crt']
     ssl.certificate: 'C:\filebeat-6.2.4-windows-x86_64\myclientcert.crt'
     ssl.key: 'C:\filebeat-6.2.4-windows-x86_64\myclientkey.key'

```

---

<div class="post-metadata">

**Author:** ![SimonSays4223](https://avatars.discourse-cdn.com/v4/letter/s/ac8455/32.png) [@SimonSays4223](https://discuss.elastic.co/u/SimonSays4223)\
**Post date:** [June 5, 2018, 9:24am UTC](https://discuss.elastic.co/t/filebeat-error-on-windows-with-ssl-certificates/134559/4 "2018-06-05T09:24:05Z")

</div>

Nice. that worked... now filebeat is starting.

Thanks a lot!

---

<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:** [July 3, 2018, 9:24am UTC](https://discuss.elastic.co/t/filebeat-error-on-windows-with-ssl-certificates/134559/5 "2018-07-03T09:24:14Z")

</div>

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