# Ssl.verification\_mode is broken in 6.7.2

**URL:** https://discuss.elastic.co/t/ssl-verification-mode-is-broken-in-6-7-2/180385
**Category:** Beats
**Tags:** elastic-stack-security, filebeat
**Created:** [May 9, 2019, 2:26pm UTC](https://discuss.elastic.co/t/ssl-verification-mode-is-broken-in-6-7-2/180385 "2019-05-09T14:26:32Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jwlogemann](https://avatars.discourse-cdn.com/v4/letter/j/5fc32e/32.png) [@jwlogemann](https://discuss.elastic.co/u/jwlogemann)
#### Post date: [May 9, 2019, 2:26pm UTC](https://discuss.elastic.co/t/ssl-verification-mode-is-broken-in-6-7-2/180385/1 "2019-05-09T14:26:32Z")

</div>

Hi,  
I'm trying to connect Filebeat 6.7.2 on Windows server 2019 to ES 6.6 which has a company issued certificate.  
I've set verification\_mode to none in the yml, but I get the following error when I try to start the service:  
_2019-05-09T16:20:36.744+0200 ERROR instance/beat.go:906 Exiting: Error importing Kibana dashboards: fail to create the Elasticsearch loader: Error creating Elasticsearch client: Couldn't connect to any of the configured Elasticsearch hosts. Errors: [Error connection to Elasticsearch [https://elasticsearch.svc-win.sbx.company.com:443](https://elasticsearch.svc-win.sbx.company.com:443): Get [https://elasticsearch.svc-win.sbx.company.com:443](https://elasticsearch.svc-win.sbx.company.com:443): x509: certificate signed by unknown authority]_

filebeat.yml:

> ```
> output.elasticsearch:
> ssl.verification_mode: none
> hosts: ['https://elasticsearch.svc-win.sbx.company.com:443']
> 
> ```

Any thoughts?

---

<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: [June 6, 2019, 2:26pm UTC](https://discuss.elastic.co/t/ssl-verification-mode-is-broken-in-6-7-2/180385/2 "2019-06-06T14:26:37Z")

</div>

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