Oh yeah, I should have mentioned that sorry !
- Graylog 2.0.3 (installed from current AWS AMI just a few days ago) - nxlog-ce-2.9.1716 On Friday, 12 August 2016 00:55:59 UTC+10, Michael Anthon wrote: > > Hi All, > Is there a way to use the new collector setup to use SSL? Maybe I'm just > missing something but there doesn't seem to be a way to enable it. > > I have set up an input that uses SSL and configured nxlog manually to send > to this input successfully. The output definition in nxlog looks like > this... > > <Output out_gelf_graylog2> > Module om_ssl > Host x.x.x.x > Port 12203 > AllowUntrusted true > OutputType GELF_TCP > </Output> > > This works and I can send in log messages. > > If I try and use the same input via the collector configuration and > sidecar the output definition generated is still set to om_tcp instead of > om_ssl. I would have thought that if the input is defined to use SSL/TLS > then the generated block should switch to om_ssl. > > Is this an issue with graylog2 or have I just done something wrong? > > Thanks > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/9add45c3-b0c2-438a-852c-6f428d4ccbd3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
