linkedin / linkedin/Burrow

Burrow can't connect to HTTPS in the notifier

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

Nobody has claimed this yet.

Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

Has anyone tried setting up 'Notifier HTTP' to a HTTPS URL? I receive an error that says `"Post https://....: x509: certificate signed by unknown authority"`

I am using Burrow on a golang:alpine image. Tried updating my endpoint's certificate on the ca-certificates level and using the "headers" option to pass on the key for connecting to the HTTPS URL.

My config is as below -
[notifier.newrelic]
class-name="http"
interval=10
threshold=1
send-close=true
url-open="https://xyz.com/events"
url-close="https://xyz.com/events"
template-post="/default-http-post.tmpl"
extras={ eventType="burrow" }
timeout=5
keepalive=30
headers={ X-Insert-Key="key"}

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing the HTTPS failure with the shown Notifier HTTP configuration on the golang:alpine image, checking how its certificate authorities are used. Compare the behavior with a trusted HTTPS endpoint and define done as the notifier successfully posting to HTTPS without the x509 unknown-authority error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.