Hi, On Monday, 13 June 2016 02:54:55 UTC+2, 123Dev wrote: > > *graylog-ctl enforce-ssl *is not setting the REST transport on HTTPS > > In our case API browser is on: http://10.20.1.229:12900/api-browser and > is accessible > If I try to check if it is also accessible on SSL, > https://10.20.1.229:12900/api-browser *it fails* > > Would be nice if *enforse-ssl *would set this correctly? >
That's completely correct as it is. The official virtual machine and Docker images are using nginx for TLS (HTTPS) termination and not Graylog itself. Cheers, Jochen -- 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/ae1c1159-d835-465d-8f03-a0542f27bbc4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
