Cert error for intial setup of fileBeat

i follow exactly the documentaion , but we stuck on :slight_smile:
filebeat setup.

filebeat setup
Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://127.0.0.1:9200: Get "https://127.0.0.1:9200": decode 'ca_trusted_fingerprint': encoding/hex: invalid byte: U+002F '/']

My conf;


output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["127.0.0.1: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: "changeme"

  username: "elastic"
  password: "xxxxxxxxxxxx"
  ssl.ca_trusted_fingerprint: "/etc/filebeat/certs/http_ca.crt"
  ssl.verificationMode: none

"/etc/filebeat/certs/http_ca.crt" i s a copy of "/etc/Elasticsearch/certs/http_ca.crt"

The ssl.ca_trusted_fingerprint value is the actual fingerprint, not a path to the file. If u want to use a file use ssl.certificate_authorities which is a list of trusted CA files

1 Like

hello legoguy1000,
ok after modify , filebeat setup , is progressing progress. (so your advice was good ;-))
now i've got :

Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to http://localhost:5601/s/HAproxy/api/status fails: fail to execute the HTTP GET request: Get "http://localhost:5601/s/HAproxy/api/status": EOF. Response: .

Modify some port in kabana , then ok.

thank you.

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