# Metricbeat module monitoring self-signed SSL endpoint

**URL:** <https://discuss.elastic.co/t/metricbeat-module-monitoring-self-signed-ssl-endpoint/147779>\
**Category:** Beats\
**Created:** [September 7, 2018, 9:41pm UTC](https://discuss.elastic.co/t/metricbeat-module-monitoring-self-signed-ssl-endpoint/147779 "2018-09-07T21:41:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomaszp](https://avatars.discourse-cdn.com/v4/letter/t/c89c15/32.png) [@tomaszp](https://discuss.elastic.co/u/tomaszp)\
**Post date:** [September 7, 2018, 9:41pm UTC](https://discuss.elastic.co/t/metricbeat-module-monitoring-self-signed-ssl-endpoint/147779/1 "2018-09-07T21:41:31Z")

</div>

Hi,

I'm trying to monitor an SSL endpoint signed with a self-signed certificate with either the dropwizard or jolokia module of Metricbeat.

For example, a snipped of jolokia module config:  
`- module: jolokia
metricsets: ["jmx"]
enabled: true
period: 1s
hosts: ["https://host007.***.com:8082/manager/jmxproxy"]`

How can this be accomplished?

In the debug message, both report something similar to this:

` "error": {
"message": "error making http request: Post https://host007.**.com:8082/manager/jmxproxy: x509: certificate signed by unknown authority"
}`

---

<div class="post-metadata">

**Author:** ![Joern\_Ott\_Schufa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joern_ott_schufa/32/33857_2.png) [@Joern\_Ott\_Schufa](https://discuss.elastic.co/u/Joern_Ott_Schufa)\
**Post date:** [September 25, 2018, 12:57pm UTC](https://discuss.elastic.co/t/metricbeat-module-monitoring-self-signed-ssl-endpoint/147779/2 "2018-09-25T12:57:56Z")

</div>

I am encountering the same issue running v6.4.0. The documentation specifies

> This module supports TLS connections when using `ssl` config field, as described in [_Specify SSL settings_](https://www.elastic.co/guide/en/beats/metricbeat/master/configuration-ssl.html). It also supports the options described in [Standard HTTP config options](https://www.elastic.co/guide/en/beats/metricbeat/master/configuration-metricbeat.html#module-http-config-options)[edit](https://github.com/elastic/beats/edit/master/metricbeat/docs/metricbeat-options.asciidoc).

Following those links, one can find that there is an option "ssl.verification\_mode" which can be set to "none". Sady, that does not change anything.

---

<div class="post-metadata">

**Author:** ![Joern\_Ott\_Schufa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joern_ott_schufa/32/33857_2.png) [@Joern\_Ott\_Schufa](https://discuss.elastic.co/u/Joern_Ott_Schufa)\
**Post date:** [September 25, 2018, 1:10pm UTC](https://discuss.elastic.co/t/metricbeat-module-monitoring-self-signed-ssl-endpoint/147779/3 "2018-09-25T13:10:18Z")

</div>

Correction: "ssl.verification\_mode: none" works. I had a typo in the config.

---

<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:** [October 23, 2018, 3:10pm UTC](https://discuss.elastic.co/t/metricbeat-module-monitoring-self-signed-ssl-endpoint/147779/4 "2018-10-23T15:10:20Z")

</div>

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