Hi Adi, I'm not sure what you intended to do with these JVM settings, but they're for the Maven build system and not Graylog.
Please refer to http://docs.graylog.org/en/2.2/pages/configuration/https.html for information about using HTTPS in Graylog. Cheers, Jochen On Sunday, 19 February 2017 15:23:05 UTC+1, Adi Spivak wrote: > > i upgraded to graylog 2.2 and now i keep getting ssl related errors. > it worked on graylog 2.1 with this added flags: > -Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true > -Dmaven.wagon.http.ssl.ignore.validity.dates=true > now they do not help, ports are not comming up, and i keep getting ssl > related errors: > javax.net.ssl.SSLHandshakeException: > sun.security.validator.ValidatorException: PKIX path building failed: > sun.security.provider.certpath.SunCertPathBuilderException: unable to find > valid certification path to requested target > Caused by: sun.security.provider.certpath.SunCertPathBuilderException: > unable to find valid certification path to requested target > > can anyone help me please? > > -- 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/513de1e8-c899-482c-9dc2-64371671f454%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
