-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS with selfsigned certificate #44
Comments
Update: Using the selfsigned certificate as CA certificate (Parameter ca_file) works. Still, it is not clear to me how the verify_mode parameter is supposed to work. Can anyone clarify? |
Hi @mreiger I have cerated self signed CA certificate. Created Server certificate and signed that with the CA. Syslog server config ->
Fluentd COnfig
getting err --> error="verification error"
Could you please suggest what i'm missing? |
Hi I am trying to use this plugin (via the fluentd kubernetes daemonset Debian syslog docker image, which as far as I can tell uses this plugin for output.)
I need to use TLS encryption and the syslog receiver uses a selfsigned certificate. Therefore I tried to disable certificate verification with the verify_mode paramter; however I still get a verification error and no connection.
This is my output configuration:
Name matching is done via /etc/hosts (through Kubernetes hostAliases) entry.
The selfsigned certificate has "syslogserver" both as issuer and subject CN; but this should not matter since I try to disable certificate verification anyway.
The error message I get is:
I also tried other values for verify_mode after some searching:
but the result - and the error message - is the same.
Can you advise me what the correct use of the parameter is?
The text was updated successfully, but these errors were encountered: