Failed to connect to backoff(elasticsearch(https://x.x.x.x:9200)): Get "https://x.x.x.x:9200": x509: certificate signed by unknown authority

Open
#60 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
elasticsearch, go
Domain
backend, security

Research direction

No files or tests are named. Start by tracing Machinebeat's Elasticsearch connection configuration and how TLS options are passed to the client; confirm whether a verification-mode setting can be exposed safely. Done means self-signed certificates can be handled as specified and the behavior is covered by appropriate tests or documentation.

Written by the indexing model from the issue text.

Description

I'm using self-signed certificates. Is it possible to pass Machinebeat a parameter like ssl.verification_mode: none?

ERROR   [esclientleg]   transport/logging.go:37 Error dialing x509: certificate signed by unknown authority     {"network": "tcp", "address": "x.x.x.x:9200"}
ERROR   [publisher_pipeline_output]     pipeline/output.go:154  Failed to connect to backoff(elasticsearch(https://x.x.x.x:9200)): Get "https://x.x.x.x:9200": x509: certificate signed by unknown authority
Dominant language
Go
Stars
79
Forks
28
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/Machinebeat

All issues in elastic/Machinebeat

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.