Filebeat Error

Elastic Stack Beats
1

I set filebeat to use the ingest node of okta, but an error occurs and filebit does not run.

ERROR [esclientleg] transport/logging.go:37 Error dialing x509: certificate signed by unknown authority {"network": "tcp", "address": "10.10.10.10:9200"}
2022-12-02T03:11:39.817Z ERROR [esclientleg] eslegclient/connection.go:232 error connecting to Elasticsearch at https://10.10.10.10:9200: Get "https://10.10.10.10:9200": x509: certificate signed by unknown authority
2022-12-02T03:11:39.817Z ERROR instance/beat.go:1014 Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://10.10.10.10:9200: Get "https://10.10.10.10:9200": x509: certificate signed by unknown authority]
Exiting: couldn't connect to any of the configured Elasticsearch hosts. Errors: [error connecting to Elasticsearch at https://10.10.10.10:9200: Get "https://10.10.10.10:9200": x509: certificate signed by unknown authority]

2

Welcome to our community! :smiley:

That would be why, there's a tonne of web search hits on approaches to fix this. How did you create your certificates?

3

I struggled a lot to solve this problem.
Resolved with "ssl.verification_mode: "none".

4

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