How to connect beats to elasticsearch, when elasticsearch using ssl/tls

what should i do to make all of my beat can send log to my elasticsearch since i setting ssl/tls to my elasticsearch. this my configuration and the log

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

- type: log

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

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/log/*.log
    #- /var/log/messages*
    #- /var/adm/syslog.log
     - /var/log/auth.log
     - /var/log/syslog

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

  ### Multiline options

  # Multiline can be used for log messages spanning multiple lines. This is common
  # for Java Stack Traces or C-Line Continuation

  # The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
  #multiline.pattern: ^\[

  # Defines if the pattern set under pattern should be negated or not. Default is false.
  #multiline.negate: false

  # Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
  # that was (not) matched before or after or as long as a pattern is not matched based on negate.
  # Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
  #multiline.match: after

# filestream is an experimental input. It is going to replace log input in the future.
- type: filestream

  # 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.
  #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.
  #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: "https://10.194.11.68: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: ["10.194.11.67:9200"]

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

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

  #public key certificates
  elasticsearch.ssl.certificateAuthorities: [ "/etc/filebeat/elasticsearch-ca.pem" ]
  elasticsearch.ssl.verificationMode: none

# ------------------------------ Logstash Output -------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["10.194.11.69:5443"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/filebeat/logstash-forwarder.crt"]

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

log

● filebeat.service - Filebeat sends log files to Logstash or directly to Elasticsearch.
   Loaded: loaded (/usr/lib/systemd/system/filebeat.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Tue 2021-04-27 09:44:00 WIB; 6min ago
     Docs: https://www.elastic.co/products/beats/filebeat
  Process: 6275 ExecStart=/usr/share/filebeat/bin/filebeat --environment systemd $BEAT_LOG_OPTS $BEAT_CONFIG_OPTS $BEAT_PATH_OPTS (code=exited, status=1/FAILURE)
 Main PID: 6275 (code=exited, status=1/FAILURE)

Apr 27 09:44:00 localhost.localdomain systemd[1]: Unit filebeat.service entered failed state.
Apr 27 09:44:00 localhost.localdomain systemd[1]: filebeat.service failed.
Apr 27 09:44:00 localhost.localdomain systemd[1]: filebeat.service holdoff time over, scheduling restart.
Apr 27 09:44:00 localhost.localdomain systemd[1]: start request repeated too quickly for filebeat.service
Apr 27 09:44:00 localhost.localdomain systemd[1]: Failed to start Filebeat sends log files to Logstash or directly to Elasticsearch..
Apr 27 09:44:00 localhost.localdomain systemd[1]: Unit filebeat.service entered failed state.
Apr 27 09:44:00 localhost.localdomain systemd[1]: filebeat.service failed.

please help me :frowning:

Can you please post the Filebeat logs or start Filebe in debug using -e and post the output?

how to start filebeat in debug using -e

see Debug | Filebeat Reference [7.12] | Elastic

t=\"UTF-8\"","Bearer realm=\"security\"","ApiKey"]}},"status":401}]
2021-05-04T19:47:03.839+0700    INFO    cfgfile/reload.go:224   Loading of config files completed.
2021-05-04T19:47:03.840+0700    INFO    log/harvester.go:302    Harvester started for file: /var/log/messages-20210425
2021-05-04T19:47:03.840+0700    INFO    log/harvester.go:302    Harvester started for file: /var/log/secure-20210502
2021-05-04T19:47:03.842+0700    INFO    log/harvester.go:302    Harvester started for file: /var/log/messages-20210502
2021-05-04T19:47:03.843+0700    INFO    log/harvester.go:302    Harvester started for file: /var/log/secure
2021-05-04T19:47:06.378+0700    INFO    [add_cloud_metadata]    add_cloud_metadata/add_cloud_metadata.go:89     add_cloud_metadata: hosting provider type not detected.
2021-05-04T19:47:06.378+0700    INFO    log/harvester.go:302    Harvester started for file: /var/log/messages
2021-05-04T19:47:06.500+0700    INFO    [publisher_pipeline_output]     pipeline/output.go:143  Connecting to backoff(elasticsearch(https://10.194.11.67:9200))
2021-05-04T19:47:06.500+0700    INFO    [publisher]     pipeline/retry.go:219   retryer: send unwait signal to consumer
2021-05-04T19:47:06.500+0700    INFO    [publisher]     pipeline/retry.go:223     done
2021-05-04T19:47:07.603+0700    ERROR   [publisher_pipeline_output]     pipeline/output.go:154  Failed to connect to backoff(elasticsearch(https://10.194.11.67:9200)): 401 Unauthorized: {"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}
2021-05-04T19:47:07.604+0700    INFO    [publisher_pipeline_output]     pipeline/output.go:145  Attempting to reconnect to backoff(elasticsearch(https://10.194.11.67:9200)) with 1 reconnect attempt(s)
2021-05-04T19:47:07.604+0700    INFO    [publisher]     pipeline/retry.go:219   retryer: send unwait signal to consumer
2021-05-04T19:47:07.604+0700    INFO    [publisher]     pipeline/retry.go:223     done
2021-05-04T19:47:09.780+0700    ERROR   [publisher_pipeline_output]     pipeline/output.go:154  Failed to connect to backoff(elasticsearch(https://10.194.11.67:9200)): 401 Unauthorized: {"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}
2021-05-04T19:47:09.780+0700    INFO    [publisher_pipeline_output]     pipeline/output.go:145  Attempting to reconnect to backoff(elasticsearch(https://10.194.11.67:9200)) with 2 reconnect attempt(s)
2021-05-04T19:47:09.780+0700    INFO    [publisher]     pipeline/retry.go:219   retryer: send unwait signal to consumer
2021-05-04T19:47:09.780+0700    INFO    [publisher]     pipeline/retry.go:223     done
2021-05-04T19:47:17.292+0700    ERROR   [publisher_pipeline_output]     pipeline/output.go:154  Failed to connect to backoff(elasticsearch(https://10.194.11.67:9200)): 401 Unauthorized: {"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}
2021-05-04T19:47:17.292+0700    INFO    [publisher_pipeline_output]     pipeline/output.go:145  Attempting to reconnect to backoff(elasticsearch(https://10.194.11.67:9200)) with 3 reconnect attempt(s)
2021-05-04T19:47:17.293+0700    INFO    [publisher]     pipeline/retry.go:219   retryer: send unwait signal to consumer
2021-05-04T19:47:17.293+0700    INFO    [publisher]     pipeline/retry.go:223     done
2021-05-04T19:47:27.920+0700    ERROR   [publisher_pipeline_output]     pipeline/output.go:154  Failed to connect to backoff(elasticsearch(https://10.194.11.67:9200)): 401 Unauthorized: {"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}
2021-05-04T19:47:27.920+0700    INFO    [publisher_pipeline_output]     pipeline/output.go:145  Attempting to reconnect to backoff(elasticsearch(https://10.194.11.67:9200)) with 4 reconnect attempt(s)
2021-05-04T19:47:27.920+0700    INFO    [publisher]     pipeline/retry.go:219   retryer: send unwait signal to consumer
2021-05-04T19:47:27.920+0700    INFO    [publisher]     pipeline/retry.go:223     done
2021-05-04T19:47:33.390+0700    INFO    [monitoring]    log/log.go:145  Non-zero metrics in the last 30s        {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":240,"time":{"ms":249}},"total":{"ticks":1200,"time":{"ms":1214},"value":1200},"user":{"ticks":960,"time":{"ms":965}}},"handles":{"limit":{"hard":4096,"soft":1024},"open":19},"info":{"ephemeral_id":"a190300e-3931-4e22-92ee-38a327e13fee","uptime":{"ms":30100}},"memstats":{"gc_next":48533840,"memory_alloc":42771176,"memory_total":125823904,"rss":75542528},"runtime":{"goroutines":85}},"filebeat":{"events":{"active":4124,"added":4146,"done":22},"harvester":{"open_files":7,"running":7,"started":7}},"libbeat":{"config":{"module":{"running":1,"starts":1},"reloads":1,"scans":1},"output":{"read":{"bytes":3415},"type":"elasticsearch","write":{"bytes":620}},"pipeline":{"clients":3,"events":{"active":4118,"filtered":25,"published":4116,"retry":200,"total":4143}}},"registrar":{"states":{"current":16,"update":22},"writes":{"success":22,"total":22}},"system":{"cpu":{"cores":4},"load":{"1":0,"15":0.05,"5":0.01,"norm":{"1":0,"15":0.0125,"5":0.0025}}}}}}
^C2021-05-04T19:47:43.350+0700  INFO    beater/filebeat.go:515  Stopping filebeat
2021-05-04T19:47:43.351+0700    INFO    beater/crawler.go:148   Stopping Crawler
2021-05-04T19:47:43.351+0700    INFO    beater/crawler.go:158   Stopping 1 inputs
2021-05-04T19:47:43.351+0700    INFO    cfgfile/reload.go:227   Dynamic config reloader stopped
2021-05-04T19:47:43.351+0700    INFO    [reload]        cfgfile/list.go:129     Stopping 1 runners ...
2021-05-04T19:47:43.351+0700    INFO    input/input.go:136      input ticker stopped
2021-05-04T19:47:43.351+0700    INFO    [crawler]       beater/crawler.go:163   Stopping input: 17165655958888633130
2021-05-04T19:47:43.351+0700    INFO    input/input.go:136      input ticker stopped
2021-05-04T19:47:43.351+0700    INFO    log/harvester.go:329    Reader was closed: /var/log/sdcss_install.log. Closing.
2021-05-04T19:47:43.351+0700    INFO    log/harvester.go:329    Reader was closed: /var/log/vmware-vmsvc.log. Closing.
2021-05-04T19:47:43.351+0700    INFO    input/input.go:136      input ticker stopped
2021-05-04T19:47:43.352+0700    INFO    beater/crawler.go:178   Crawler stopped
2021-05-04T19:47:43.352+0700    INFO    [registrar]     registrar/registrar.go:132      Stopping Registrar
2021-05-04T19:47:43.352+0700    INFO    [registrar]     registrar/registrar.go:166      Ending Registrar
2021-05-04T19:47:43.353+0700    INFO    [registrar]     registrar/registrar.go:137      Registrar stopped

It looks like you're either not sending credentials or incorrect credentials

You also shouldn't need the elasticsearch here since it's under the output.elasticsearch key. It's possible that duplication could be causing a conflict.

so what should i do?

btw i just try ssl.certificate but still doesn't work

You changed both lines to below and no difference in log messages or success?

ssl.certificateAuthorities: ["/etc/filebeat/elasticsearch-ca.pem" ]
ssl.verificationMode: none

Also what version of filebeat and elasticsearch are u using?

yes now it's running but i don't know is it send log or not

i use v7.10

btw how to load dashboard to kibana. i use https

Run filebeat setup. That will load the dashboards, ingest pipelines...

yeah i know but i got an error

[root@bdi-uat-splunkes ansible]# filebeat setup --dashboards
Loading dashboards (Kibana must be running and reachable)
Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to https://10.194.11.68:5601/api/status fails: fail to execute the HTTP GET request: Get "https://10.194.11.68:5601/api/status": x509: cannot validate certificate for 10.194.11.68 because it doesn't contain any IP SANs. Response: .
# =================================== 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: "https://10.194.11.68:5601"
  ssl.enabled: true
  ssl.certificate_authorities: ["/etc/filebeat/elasticsearch-ca.pem"]

this my config

[root@bdi-uat-splunkes ansible]# filebeat setup
Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://10.194.11.67:9200: 401 Unauthorized: {"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}]

this the error i got filebeat setup

set ssl.verification_mode: certificate, see Configure SSL | Filebeat Reference [7.12] | Elastic

it can't, still got same error :frowning: