Looking for help with some errors we're receiving on our Windows TLS - [AbstractTcpTransport]

[gsmith]

hey @Tom_at_lorman

Dont be fooled by the full path of the certificates,

This can be adjusted for example:

output.logstash:
  # The Logstash hosts
  hosts: ["192.168.1.100:5044"]

  #sername: "admin"
  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  ssl.certificate_authorities: ["C:\winlogbeat\ca.pem"]

  # Certificate for SSL client authentication
  ssl.certificate: "C:\winlogbeat\cert.pem"

  # Client Certificate Key
  ssl.key: "C:\winlogbeat\cert.key"

Ensure Winlogbeat has access to certificates.

@Tom_at_lorman

So do the windows clients need certs located locally?

Where every you decide to purtyour certificate/s that Windows node/instance can access them.

@Tom_at_lorman

f that was the case I haven’t seen any example sidecare configurations like this (with paths that point to a windows path).

Winlogbeat → Graylog’s Input 5044 (SSL certificates can be used)

The Communication between Sidecar and Graylog will be secured if your API uses SSL .To secure the communication between the Collector and Graylog you just need to mark Enable TLS in your Beats Input.

This is found here.

https://go2docs.graylog.org/5-0/getting_in_log_data/graylog_sidecar.html

There are a lot of good references in the form.

Windows Sidecar TLS setup

So, i managed to make it work without TLS - Graylog Sidecar Windows beats. I receive the messages and all is good. Now, i try to make it work with TLS and i have some questions, as, i am getting this error on the windows side when i am running the sidecar.exe [image] so, the certificate i am using on GL server i installed it on the windows machine under this path [image] the setup i found for the GL part is for a linux machine though: # Needed for Graylog fields_under_root: true fields.c…