509: certificate signed by unknown authority

hello dears,

I'm getting errors when running sudo filebeat setup --pipelines -and below the error return:

{"log.level":"error","@timestamp":"2022-10-21T00:32:06.624+0100","log.origin":{"file.name":"instance/beat.go","file.line":1056},"message":"Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://localhost:9200: Get "https://localhost:9200": x509: certificate signed by unknown authority]","service.name":"filebeat","ecs.version":"1.6.0"}
Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://localhost:9200: Get "https://localhost:9200": x509: certificate signed by unknown authority]

Well you did not share your configurations so we can only guess

Assuming you are on 8.x

..

Perhaps

And perhaps this..

For testing you could set this in the filebeat.yml under the elasticsearch output.

ssl.verification_mode: none

/etc/filebeat/filebeat.yml

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

-# ================================== 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: ["https://10.35.33.65:9200"]
  username: "elastic"
  password: "j-oQfgstGW*gVV_0lP9I"

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

  -# Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  #username: "elastic"
  #password: "changeme"

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

I added the line but the error remains... i.e. filebeat does not start

-# ================================== 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: ["https://10.35.33.65:9200"]
username: "elastic"
password: "j-oQfgstGW*gVV_0lP9I"
ssl.verification_mode: none

-# Protocol - either http (default) or https.
#protocol: "https"

-# Authentication credentials - either API key or username/password.
#api_key: "id:api_key"
#username: "elastic"
#password: "changeme"

ssl.verification_mode: none

I added the line but the error remains... i.e. filebeat does not start


-# ================================== 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: ["[https://10.35.33.65:9200](https://10.35.33.65:9200/)"]
username: "elastic"
password: "j-oQfgstGW*gVV_0lP9I"
**ssl.verification_mode: none**

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

-# Authentication credentials - either API key or username/password.
#api_key: "id:api_key"
#username: "elastic"
#password: "changeme"

The error continues, even adding the ssl.verification_mode: none

Can you show the logs please again? Also, can you please take a couple moments to format your code? It makes it nearly impossible to read... I did it for you.

But because I did it afterwards, It's hard to tell if you're indentation is correctly. If that SSL verification is not indented properly under the output, then it will not take effect. So it's hard for us to tell whether you have it properly formatted or not.

Select the code and highlight and press the </> button


###################### Filebeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common
# options. The filebeat.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/filebeat/index.html

# For more available modules and options, please see the filebeat.reference.yml sample
# configuration file.

# ============================== Filebeat inputs ===============================

filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so
# you can use different inputs for various configurations.
# Below are the input specific configurations.

# filestream is an input for collecting log messages from files.
- type: filestream

  # Unique ID among all inputs, an ID is required.
  id: my-filestream-id

  # Change to true to enable this input configuration.
  enabled: false

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/log/*.log
    #- c:\programdata\elasticsearch\logs\*

  # Exclude lines. A list of regular expressions to match. It drops the lines that are
  # matching any regular expression from the list.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #exclude_lines: ['^DBG']

  # Include lines. A list of regular expressions to match. It exports the lines that are
  # matching any regular expression from the list.
  # Line filtering happens after the parsers pipeline. If you would like to filter lines
  # before parsers, use include_message parser.
  #include_lines: ['^ERR', '^WARN']

  # Exclude files. A list of regular expressions to match. Filebeat drops the files that
  # are matching any regular expression from the list. By default, no files are dropped.
  #prospector.scanner.exclude_files: ['.gz$']

  # Optional additional fields. These fields can be freely picked
  # to add additional information to the crawled log files for filtering
  #fields:
  #  level: debug
  #  review: 1

# ============================== Filebeat modules ==============================

filebeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

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

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: false

# 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: "XXXXXXXX: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 Filebeat 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: ["https://x.x.x.x:9200"]
  username: "elastic"
  password: "j-oQfgstGW*gVV_0lP9I"
  ssl.verification_mode: none
 
  # Protocol - either `http` (default) or `https`.
  #protocol: "https"

  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  #username: "elastic"
  #password: "changeme"

# ------------------------------ 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: ~
  - add_docker_metadata: ~
  - add_kubernetes_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 ==============================
# Filebeat 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
# Filebeat 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 filebeat.
#instrumentation:
    # Set to true to enable instrumentation of filebeat.
    #enabled: false

    # Environment in which filebeat 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

Hi @Joao_Malebo

Can you please show the latest errors... and not just a single line ... lines before and after...

Also Can you curl to elasticsearch from the filebeat server what is the output / results of that.

curl -k -v https://youriporhost:9200

also you should really just run this command for setup so everything gets set up

sudo filebeat setup -e

[rcmag.kta@XXXXXXXX ~]$ curl -k -v https://X.X.X.X:9200
* About to connect() to X.X.X.X port 9200 (#0)
*   Trying X.X.X.X...
* Connected to X.X.X.X (X.X.X.X) port 9200 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate:
*       subject: CN=XXXXXXXX
*       start date: Oct 14 13:44:46 2022 GMT
*       expire date: Oct 13 13:44:46 2024 GMT
*       common name: XXXXXXXX
*       issuer: CN=Elasticsearch security auto-configuration HTTP CA
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: X.X.X.X:9200
> Accept: */*
>
< HTTP/1.1 401 Unauthorized
< WWW-Authenticate: Basic realm="security" charset="UTF-8"
< WWW-Authenticate: Bearer realm="security"
< WWW-Authenticate: ApiKey
< content-type: application/json;charset=utf-8
< content-length: 459
<
* Connection #0 to host X.X.X.X left intact
{"error":{"root_cause":[{"type":"security_exception","reason":"missing authentication credentials for REST request [/]","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}}],"type":"security_exception","reason":"missing authentication credentials for REST request [/]","header":{"WWW-Authenticate":["Basic realm=\"security\" charset=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}},"status":401}[rcmag.kta@XXXXXXXX ~]$
{"log.level":"info","@timestamp":"2022-10-28T00:04:14.171+0100","log.logger":"modules","log.origin":{"file.name":"fileset/pipelines.go","file.line":133},"message":"Elasticsearch pipeline loaded.","service.name":"filebeat","pipeline":"filebeat-8.4.3-azure-auditlogs-azure-shared-pipeline","ecs.version":"1.6.0"}
{"log.level":"error","@timestamp":"2022-10-28T00:04:14.172+0100","log.origin":{"file.name":"cfgfile/reload.go","file.line":258},"message":"Error loading configuration files: 1 error: Unable to hash given config: missing field accessing '0.firewall' (source:'/etc/filebeat/modules.d/gcp.yml.disabled')","service.name":"filebeat","ecs.version":"1.6.0"}
{"log.level":"info","@timestamp":"2022-10-28T00:04:14.172+0100","log.logger":"load","log.origin":{"file.name":"cfgfile/list.go","file.line":139},"message":"Stopping 68 runners ...","service.name":"filebeat","ecs.version":"1.6.0"}
Loaded Ingest pipelines

@Joao_Malebo

I apologize you're struggling but you need to really show us the command you run and the full output.

If you just give us a couple lines of logs and and not the command you ran It's very difficult. For us to help.

When I asked for the startup logs for filebeat I'm expecting 50 lines of logs including the command that you use to start that.

Also, there is an error message in what you did post saying that you have a module enabled but their syntax errors in it.

Do purposely have other modules enabled. I see references to azure modules and GCP modules.

If you only give us a portion of the view and not everything you're doing, we're not going to be able to help.

The good sign is the curl seem to show the correct data so the next step I would do is.

curl -k -v -u elastic https://youriporhost:9200

And enter the elastic password when it asked for it and see if it's successful.

It's unclear to me what state you're configuration is in. I would start with something very basic.