[error connecting to Elasticsearch at https:certificate signed by unknown authority

Ana_11 · March 9, 2021, 11:13am

Hi
I have enabled secure communication in my elasticsearch deployment. https is enabled and elasticsearch and kibana is working as expected. Now when im trying to ingest the winlogbeat logs im getting the following error

Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at ht
tps://172.16.1.11:9200: Get "https://172.16.1.11:9200": x509: certificate signed by unknown authority]

below is my winlogbeat.yml file


# This file is an example configuration file highlighting only the most common

# options. The winlogbeat.reference.yml file from the same directory contains

# all the supported options with more comments. You can use it as a reference.

#

# You can find the full configuration reference here:

# https://www.elastic.co/guide/en/beats/winlogbeat/index.html

# ======================== Winlogbeat specific options =========================

# event_logs specifies a list of event logs to monitor as well as any

# accompanying options. The YAML data type of event_logs is a list of

# dictionaries.

#

# The supported keys are name (required), tags, fields, fields_under_root,

# forwarded, ignore_older, level, event_id, provider, and include_xml. Please

# visit the documentation for the complete details of each option.

# https://go.es.io/WinlogbeatConfig

winlogbeat.event_logs:

  - name: Application

    ignore_older: 72h

  - name: System

  - name: Security

    processors:

      - script:

          lang: javascript

          id: security

          file: ${path.home}/module/security/config/winlogbeat-security.js

  - name: Microsoft-Windows-Sysmon/Operational

    processors:

      - script:

          lang: javascript

          id: sysmon

          file: ${path.home}/module/sysmon/config/winlogbeat-sysmon.js

  - name: Windows PowerShell

    event_id: 400, 403, 600, 800

    processors:

      - script:

          lang: javascript

          id: powershell

          file: ${path.home}/module/powershell/config/winlogbeat-powershell.js

  - name: Microsoft-Windows-PowerShell/Operational

    event_id: 4103, 4104, 4105, 4106

    processors:

      - script:

          lang: javascript

          id: powershell

          file: ${path.home}/module/powershell/config/winlogbeat-powershell.js

  - name: ForwardedEvents

    tags: [forwarded]

    processors:

      - script:

          when.equals.winlog.channel: Security

          lang: javascript

          id: security

          file: ${path.home}/module/security/config/winlogbeat-security.js

      - script:

          when.equals.winlog.channel: Microsoft-Windows-Sysmon/Operational

          lang: javascript

          id: sysmon

          file: ${path.home}/module/sysmon/config/winlogbeat-sysmon.js

      - script:

          when.equals.winlog.channel: Windows PowerShell

          lang: javascript

          id: powershell

          file: ${path.home}/module/powershell/config/winlogbeat-powershell.js

      - script:

          when.equals.winlog.channel: Microsoft-Windows-PowerShell/Operational

          lang: javascript

          id: powershell

          file: ${path.home}/module/powershell/config/winlogbeat-powershell.js

# ====================== Elasticsearch template settings =======================

setup.template.settings:

  index.number_of_shards: 1

  #index.codec: best_compression

  #_source.enabled: false

# ================================== 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: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the

# output.

#fields:

#  env: staging

# ================================= Dashboards =================================

# These settings control loading the sample dashboards to the Kibana index. Loading

# the dashboards is disabled by default and can be enabled either by setting the

# options here or by using the `setup` command.

setup.dashboards.enabled: true

# The URL from where to download the dashboards archive. By default this URL

# has a value which is computed based on the Beat name and version. For released

# versions, this URL points to the dashboard archive on the artifacts.elastic.co

# website.

#setup.dashboards.url:

# =================================== Kibana ===================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.

# This requires a Kibana endpoint configuration.

setup.kibana:

  # Kibana Host

  # Scheme and port can be left out and will be set to the default (http and 5601)

  # In case you specify and additional path, the scheme is required: http://localhost:5601/path

  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

  host: "172.16.1.11:5601"

  # Kibana Space ID

  # ID of the Kibana Space into which the dashboards should be loaded. By default,

  # the Default Space will be used.

  #space.id:

# =============================== Elastic Cloud ================================

# These settings simplify using Winlogbeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and

# `setup.kibana.host` options.

# You can find the `cloud.id` in the Elastic Cloud web UI.

#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and

# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.

#cloud.auth:

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

# Configure what output to use when sending the data collected by the beat.

# ---------------------------- Elasticsearch Output ----------------------------

output.elasticsearch:

  # Array of hosts to connect to.

  hosts: ["172.16.1.11:9200"]

  # Protocol - either `http` (default) or `https`.

  protocol: "https"

  #ssl_verification_mode: "none"

  

  #Authentication credentials - either API key or username/password.

  #api_key: "id:api_key"

  username: "elastic"

  password: "cJwLd1eyes6DsD2fmgh0"

# ------------------------------ 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"

# ================================= Processors =================================

processors:

  - add_host_metadata:

      when.not.contains.tags: forwarded

  - add_cloud_metadata: ~

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

# Sets log level. The default log level is info.

# Available log levels are: 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",

# "publisher", "service".

#logging.selectors: ["*"]

# ============================= X-Pack Monitoring ==============================

# Winlogbeat can export internal metrics to a central Elasticsearch monitoring

# cluster.  This requires xpack monitoring to be enabled in Elasticsearch.  The

# reporting is disabled by default.

# Set to true to enable the monitoring reporter.

#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this

# Winlogbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch

# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.

#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the

# Elasticsearch output are accepted here as well.

# Note that the settings should point to your Elasticsearch *monitoring* cluster.

# Any setting that is not set is automatically inherited from the Elasticsearch

# output configuration, so if you have the Elasticsearch output configured such

# that it is pointing to your Elasticsearch monitoring cluster, you can simply

# uncomment the following line.

#monitoring.elasticsearch:

# ============================== Instrumentation ===============================

# Instrumentation support for the winlogbeat.

#instrumentation:

    # Set to true to enable instrumentation of winlogbeat.

    #enabled: false

    # Environment in which winlogbeat is running on (eg: staging, production, etc.)

    #environment: ""

    # APM Server hosts to report instrumentation results to.

    #hosts:

    #  - http://localhost:8200

    # API Key for the APM Server(s).

    # If api_key is set then secret_token will be ignored.

    #api_key:

    # Secret token for the APM Server(s).

    #secret_token:

# ================================= Migration ==================================

# This allows to enable 6.7 migration aliases

#migration.6_to_7.enabled: true

mazoutte · March 9, 2021, 12:53pm

Hello, 3 things to say :

Be carefull when you post Config files with a password ; try to modify/blank the password.
Even you have configured Elasticsearch with SSL, you need to configure some SSL stuff on the client.
Some parameters are missing in the config file like the Certificate of the Authority that signed the Elasticsearch certificate.
You have a commented example in the "Logstash Section".
Be carefull when you use IP to target a server. If the IP is not mentionned anywhere in the certificate, you will have trouble (it should be inserted in the SAN - like we do with real FQDN actualy)
I advise you to use the FQDN of the Elasticsearch's server - or an alias.

Regards
Luc

Ana_11 · March 9, 2021, 1:14pm

Hi the password is modified, So i should use

#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
#ssl.certificate: "/etc/pki/client/cert.pem"
#ssl.key: "/etc/pki/client/cert.key"

but i have added
ssl_verification_mode: "none"

mazoutte · March 9, 2021, 1:22pm

Yes, but in your config file, it's commented So I was assuming it was not used.
And we can see the Error related to the CA ....

You need only ssl.certificate_authorities for the purpose.
The others parameters are used when using Client Certificate Authentication.

system · April 6, 2021, 3:33pm

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