Winlogbeat getting x509: certificate signed by unknown authority while setting up Kibana

Elastic Stack Beats
1

I am getting x509: certificate signed by unknown authority error while trying to setup Kibana

PS C:\winlogbeat> .\winlogbeat.exe setup --dashboards

Logstash Beats configuration file

input {
	stdin {}
    beats {
        port => 5044
    }
}

#filter {
#
#}

output {
    elasticsearch{
        hosts => ["https://192.16.202.154:9200,https://192.16.202.153:9200"]
        user => "elastic"
        password => "changeme"
        index => "-%{[@metadata][beat]}-%{+YYYY.MM.dd}"
        ssl_certificate_verification => false
    }
	stdout { codec => rubydebug }
}

winlogbeat.yml

winlogbeat.event_logs:
  - name: Application
    ignore_older: 72h

setup.kibana:
  host: "192.16.202.154:5601"
  protocol: https
  username: "elastic"
  password: "5ekequ4ataDa"
  ssl.enabled: false

output.logstash:
  # The Logstash hosts
  hosts: ["192.16.200.250:5044"]
  ssl.enabled: false

I have tried using ssl.enabled: false in every place but still no luck, I am aware that we can configure SSL for this link https://www.elastic.co/guide/en/beats/winlogbeat/6.2/configuration-ssl.html#_configuration_options_9, but can i disable that and go ahead if i have to use https?

i have mentioned the ssl verification to be false in the logstash config file pasted above

appreciate if anyone can help on this

2

To match your logstash configuration, you can set the verification_mode flag to none:

setup.kibana:
   verification_mode: none

This will make winlogbeat ignore the certificate validation error

3

Thank you Adrian, the service is running without any issues now, but how do i access these dahsboards from Kibana should i search with the index that i have created or will it create with a different indexname.

I learned that there are few default visualizations created, how can i access those is my question

also when i run the winlogbeat.exe i see below error

Exiting: Error importing Kibana dashboards: fail to create the Kibana loader: Er
ror creating Kibana client: fail to get the Kibana version:HTTP GET request to /
api/status fails: fail to execute the HTTP GET request: Get https://192.16.202.1
54:5601/api/status: x509: certificate signed by unknown authority. Response: .
4

What version of beats are you using? 6.2?

Because I see an issue with the logstash configuration you shared. The index name is wrong:

It should be:

index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"

In your config, version is missing and also you have a leading slash, I think that is a mistake.

About the error with winlogbeat.exe, I don't understand as you said it was working now. Maybe when you run it by hand its using a different config that doesn't have the verification_mode: none change ?

5

Yes Adrian i am using 6.2.

I changed the index name as per your suggestion and regarding verification_mode: none, i added this entry as per your suggestion and i thought it is working but later i noticed that the issue is not fixed.

Please let me know if you need any more details

6

The conf I provided was wrong. The correct one is:

setup.kibana:
   ssl.verification_mode: none
2 Likes
7

Sorry Adrian, still no luck for me

8

What is the situation now? Are you still getting the "certificate signed by unknown authority" error?

9

Yes Adrian

10

Please paste your current winlogbeat.yml

11

Here is the complete file Adrian

###################### Winlogbeat Configuration Example ##########################

# 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
    provider:
      - CustomAppSource

#==================== Elasticsearch template setting ==========================

#setup.template.settings:
  #index.number_of_shards: 3
  #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` CLI flag or the `setup` command.

setup.dashboards.enabled: true

#setup.dashboards.index: "winlogbeat-*"

# 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: "https://192.16.202.154:5601/api/status"

#============================== 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
  verification_mode: none
  host: "192.16.202.104:5601"
  protocol: "https"
  username: "elastic"
  password: "changme"

#============================= 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: 

  # Optional protocol and basic auth credentials.

#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["192.16.200.250:5044"]
  ssl.enabled: false

  # 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: 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: [eventlog]

#============================== Xpack 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.
#xpack.monitoring.enabled: false

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well. Any setting that is not set is
# automatically inherited from the Elasticsearch output configuration, so if you
# have the Elasticsearch output configured, you can simply uncomment the
# following line.
#xpack.monitoring.elasticsearch:
12

You didn't apply the last change I suggested.

Instead of:

setup.kibana:
  # [...]
  verification_mode: none

use:

setup.kibana:
  # [...]
  ssl.verification_mode: none
1 Like
13

I am sorry i guess one of my other changes messed up with this.

now i could see the dashboard in Kibana but it is loooking winlogbeat-* index and my indexname is different "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"

how do i map it to the index name that i created

14

This is the index template. %{[@metadata][beat]} will be replaced by winlogbeat, %{[@metadata][version]} will be replaced by the version number and %{+YYYY.MM.dd} by the current date.

It matches the winlogbeat-* pattern. Look at the time picker to make sure you're looking at the appropriate time.

1 Like
15

Oh understood but what if i prefix it with my project name something like "projectname-%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}" does it still going to replace it

16

Then you will be using an index called projectname-winlogbeat-6.2.3-2018.03.22

It is not mandatory to add the beatname, version and date. You can remove it from the template.

17

Thanks a lot @adrisr for being so patient in answering all my queries

So here you are talking about the template file that is winlogbeat\winlogbeat.template.json right

{
  "index_patterns": [
    "winlogbeat-6.2.2-*"
  ],

can i completely remove this entry or i can only rename it to something like

{
  "index_patterns": [
    "*-winlogbeat-6.2.2-*"
  ],
18

No, I was referring to the index => setting in your Logstash configuration. This is how you control the index where the events are indexed.

This file you are referring now is the index pattern that is installed in Kibana, which controls the events that you will see.

If you change one, then change the other accordingly or manually set the index pattern in Kibana

19

Ok thank you

20

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