# Heartbeat Query - Problem with Websites Security Certificate

**URL:** <https://discuss.elastic.co/t/heartbeat-query-problem-with-websites-security-certificate/97191>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [August 16, 2017, 6:45am UTC](https://discuss.elastic.co/t/heartbeat-query-problem-with-websites-security-certificate/97191 "2017-08-16T06:45:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![r4z0rw1r3666](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@r4z0rw1r3666](https://discuss.elastic.co/u/r4z0rw1r3666)\
**Post date:** [August 16, 2017, 6:45am UTC](https://discuss.elastic.co/t/heartbeat-query-problem-with-websites-security-certificate/97191/1 "2017-08-16T06:45:12Z")

</div>

Hello,

I've configured heartbeat to connect to a https wsdl endpoint, however there is a problem with the website security certificate, causing failures.

As a test, I have put ssl.verification\_mode: none into the monitor section in heartbeat.yml and still have the same error.

Normally, I'd pursue the path of fixing the certificate, however I won't get enough buy in to fix it.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [August 16, 2017, 1:03pm UTC](https://discuss.elastic.co/t/heartbeat-query-problem-with-websites-security-certificate/97191/2 "2017-08-16T13:03:34Z")

</div>

Please share the configuration you are using (use three backticks before and after to get proper formatting).

---

<div class="post-metadata">

**Author:** ![r4z0rw1r3666](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@r4z0rw1r3666](https://discuss.elastic.co/u/r4z0rw1r3666)\
**Post date:** [August 17, 2017, 3:40am UTC](https://discuss.elastic.co/t/heartbeat-query-problem-with-websites-security-certificate/97191/3 "2017-08-17T03:40:29Z")

</div>

Hi Andrew, thanks for your reply:

Please see below my heartbeat.yml.

The 8002/Cardholder/?wsdl is the one in question that fails.

````auto
################### Heartbeat Configuration Example #########################

# This file is an example configuration file highlighting only some common options.
# The heartbeat.full.yml file in the same directory contains all the supported options
# with detailed comments. You can use it for reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/heartbeat/index.html

############################# Heartbeat ######################################

# Configure monitors
heartbeat.monitors:
- type: http

  # List or urls to query
  urls:
       - "http:// **** :6005"
       - "http://test-apex-workspace.***"
       - "http:// ****:29080/cad-soap/21616/***.wsdl"
       - "https://***:8082/Cardholder/?wsdl"
       - "https:// ***/pack/*** /soap?wsdl"

  # Configure task schedule
  schedule: '@every 60s'

  ssl.verification_mode: none
  # Total test connection and data exchange timeout
#================================ General =====================================

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
tags: ["web-apps"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging

#================================ Outputs =====================================

# Configure what outputs to use when sending the data collected by the beat.
# Multiple outputs may be used.

#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["***:9200"]
  index: "heartbeat-%{+yyyy.MM.dd}"
  # Optional protocol and basic auth credentials.

#----------------------------- Logstash output --------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

#================================ Logging =====================================

# Sets log level. The default log level is info.
# Available log levels are: critical, error, warning, info, debug
#logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publish", "service".
#logging.selectors: ["*"]```
````

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [August 17, 2017, 9:41pm UTC](https://discuss.elastic.co/t/heartbeat-query-problem-with-websites-security-certificate/97191/4 "2017-08-17T21:41:24Z")

</div>

Might be a bug in beats TLS verification not being correctly disabled. Can you report this [on github](https://github.com/elastic/beats/issues) please?

As workaround, you can configure the certificate authorities to be used by the TLS client.

---

<div class="post-metadata">

**Author:** ![r4z0rw1r3666](https://avatars.discourse-cdn.com/v4/letter/r/e79b87/32.png) [@r4z0rw1r3666](https://discuss.elastic.co/u/r4z0rw1r3666)\
**Post date:** [August 21, 2017, 12:42am UTC](https://discuss.elastic.co/t/heartbeat-query-problem-with-websites-security-certificate/97191/5 "2017-08-21T00:42:52Z")

</div>

Hi Steffen,

Think it was something on my end. Working ok now.

Cheers!

---

<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:** [September 18, 2017, 12:42am UTC](https://discuss.elastic.co/t/heartbeat-query-problem-with-websites-security-certificate/97191/6 "2017-09-18T00:42:59Z")

</div>

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