# Strigo account SSL issue for mysql

**URL:** <https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 18, 2021, 3:26am UTC](https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371 "2021-12-18T03:26:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![kapilsapra](https://avatars.discourse-cdn.com/v4/letter/k/85e7bf/32.png) [@kapilsapra](https://discuss.elastic.co/u/kapilsapra)\
**Post date:** [December 18, 2021, 3:26am UTC](https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371/1 "2021-12-18T03:26:00Z")

</div>

I am trying to configure and run filebeat on the `mysql` server in strigo environment. when i run filebeat i am getting SSL error that certificate signed by some different authority.

```auto

2021-12-18T05:35:20.274Z INFO eslegclient/connection.go:99 elasticsearch url: https://elasticsearch:9200
2021-12-18T05:35:20.345Z ERROR [esclientleg] eslegclient/connection.go:261 error connecting to Elasticsearch at https://elasticsearch:9200: Get "https://elasticsearch:9200": x509: certificate signed by unknown authority
2021-12-18T05:35:20.345Z ERROR instance/beat.go:951 Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://elasticsearch:9200: Get "https://elasticsearch:9200": x509: certificate signed by unknown authority]
Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://elasticsearch:9200: Get "https://elasticsearch:9200": x509: certificate signed by unknown authority]

```

Can some one from tech support troubleshoot and help me.

---

<div class="post-metadata">

**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\
**Post date:** [December 20, 2021, 12:11am UTC](https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371/2 "2021-12-20T00:11:04Z")

</div>

Can you provide your ssl configuration for elk and filebeat?

---

<div class="post-metadata">

**Author:** ![kapilsapra](https://avatars.discourse-cdn.com/v4/letter/k/85e7bf/32.png) [@kapilsapra](https://discuss.elastic.co/u/kapilsapra)\
**Post date:** [December 20, 2021, 10:59am UTC](https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371/3 "2021-12-20T10:59:17Z")

</div>

in strigo i ssh to mysql server

> ssh mysql  
> vi ./filebeat/filebeat.yml \<------- configure filebeat on mysql server  
> output.elasticsearch:  
> hosts: ["elasticsearch:9200"]  
> protocol: "https"  
> username: "elastic"  
> password: "password"  
> ssh.certificate\_authorities: ["/home/elastic/ca.crt"]

* * *

elastic@ip-172-31-47-163:~$ ssh elasticsearch

[elastic@elasticsearch ~]$ ls  
ca.crt datasets elasticsearch filebeat heartbeat logstash metricbeat  
[elastic@elasticsearch ~]$ cd elasticsearch/  
[elastic@elasticsearch elasticsearch]$ ls  
bin config data jdk lib LICENSE.txt logs modules NOTICE.txt plugins README.asciidoc  
[elastic@elasticsearch elasticsearch]$ cd config/  
[elastic@elasticsearch config]$ ls  
ca.crt elasticsearch.keystore elasticsearch.yml elasticsearch.yml.bak jvm.options log4j2.properties node1.crt node1.key

vi elasticsearch.yml

xpack.security.enabled: true  
xpack.security.transport.ssl.enabled: true  
xpack.security.http.ssl.enabled: true  
xpack.security.http.ssl.key: node1.key  
xpack.security.http.ssl.certificate: node1.crt  
xpack.security.http.ssl.certificate\_authorities: ca.crt  
xpack.security.transport.ssl.key: node1.key  
xpack.security.transport.ssl.certificate: node1.crt  
xpack.security.transport.ssl.certificate\_authorities: ca.crt

---

<div class="post-metadata">

**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\
**Post date:** [December 20, 2021, 11:09am UTC](https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371/4 "2021-12-20T11:09:30Z")

</div>

Please use this option to format the code you paste.  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/c/0c86d86cb83dd79cc5b03598221e749e167c5783.png)

From the documentation, you can read.

```auto
`xpack.security.http.ssl.verification_mode`

([Static](https://www.elastic.co/guide/en/elasticsearch/reference/current/settings.html#static-cluster-setting)) Controls the verification of certificates. Controls the verification of certificates.

Valid values are:

* `full` , which verifies that the provided certificate is signed by a trusted authority (CA) and also verifies that the server’s hostname (or IP address) matches the names identified within the certificate.
* `certificate` , which verifies that the provided certificate is signed by a trusted authority (CA), but does not perform any hostname verification.
* `none` , which performs *no verification* of the server’s certificate. This mode disables many of the security benefits of SSL/TLS and should only be used after very careful consideration. It is primarily intended as a temporary diagnostic mechanism when attempting to resolve TLS errors; its use on production clusters is strongly discouraged.The default value is `full` .

```

Currently your setting for option  
`xpack.security.http.ssl.verification_mode`  
if default so it work as "full"

That means if you did not specify the hostname for a certificate for filebeat and it is different than in certificate. The connection will be refused.

Also you did not provide setting in filebeat config for

```auto
ssl.certificate: "/path/beats.crt"
ssl.key: "/path/beats.key"

```

Is it set up?

---

<div class="post-metadata">

**Author:** ![kapilsapra](https://avatars.discourse-cdn.com/v4/letter/k/85e7bf/32.png) [@kapilsapra](https://discuss.elastic.co/u/kapilsapra)\
**Post date:** [December 20, 2021, 11:47am UTC](https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371/5 "2021-12-20T11:47:31Z")

</div>

Thanks Adriann,

I'll try as mentioned above. ssl settings in filebeat in mysql is not configured. so do i need to set that up as well ??

---

<div class="post-metadata">

**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\
**Post date:** [December 20, 2021, 12:02pm UTC](https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371/6 "2021-12-20T12:02:33Z")

</div>

Yes you do.

> **[Configure SSL | Filebeat Reference \[7.16\] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/configuration-ssl.html)**

---

<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:** [January 17, 2022, 2:03pm UTC](https://discuss.elastic.co/t/strigo-account-ssl-issue-for-mysql/292371/7 "2022-01-17T14:03:27Z")

</div>

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