Jochen,

Thank you!  I had been looking in the HTTPS section of the graylog 2.1 
documentation, but the link you provided made the configuration 
ridiculously simple.  Dropped our certs into the nginix/ca directory, ran 
the graylog-ctl enforce-ssl and graylog-ctl restart nginix commands and 
graylog-ctl reconfigure-as-server and all is working perfectly.  

Thanks!!
Matt



On Saturday, October 22, 2016 at 2:58:32 AM UTC-7, Jochen Schalanda wrote:
>
> Hi Matthew,
>
> what did you do exactly and which error messages do you see?
>
> If you're using the OVA (virtual machine images), please follow the 
> instructions at 
> http://docs.graylog.org/en/2.1/pages/configuration/graylog_ctl.html#install-custom-ssl-certificates
>
> Cheers,
> Jochen
>
> On Friday, 21 October 2016 18:59:08 UTC+2, Matthew Johnson wrote:
>>
>> Hello, just upgraded to graylog 2.1.1 (virtual appliances upgraded from 
>> 2.0.3 -> 2.1 -> 2.1.1), and everything is working as expected over HTTP. 
>>  We are attempting to configure HTTPS using an existing certificate and 
>> private key signed by a public CA, but no luck when following the Graylog 
>> 2.1 HTTPS Configuration Documentation. Does anyone have step-by-step 
>> directions to properly configure HTTPS?  Our configuration is one graylog 
>> server node and two graylog data nodes.
>>
>> We also found some separate documentation about modifying the httpd.conf 
>> apache configuration file, but that file does not exist at the expected 
>> location in /etc/apache2 (the apache2 directory does not exist).
>>
>> Thanks in advance!
>>
>>

-- 
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/3e39f4cf-1a78-4f62-a937-a1fc484ca7c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to