[graylog2] Re: Upgrade 1.1.6 to 1.2 RC broke REST API using TLS?
Thanks for looking into this Jochen, I'll try to enable TLS again after the next release. As an off-topic side note, good job on the LDAP group support, that was my main reason to upgrade so fast and it's working nicely, even if TLS on the API isn't. :P Tim C -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/e369ff08-31b0-4616-b13d-ad7ffe173a24%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Upgrade 1.1.6 to 1.2 RC broke REST API using TLS?
Configuration is exactly as it was previously and I have had to revert back and forth between HTTP and HTTPS a few times while I've tested and reverted to get thigns working again. Following variables are set when using HTTPS: *Server* rest_listen_uri = https://server2.example.com:12900/ rest_enable_tls = true rest_tls_cert_file = /etc/graylog/server/key.cer rest_tls_key_file = /etc/graylog/server/key.key *Web* graylog2-server.uris= "https://server1.example.com:12900,https://server2.example.com:12900"; and like this for HTTP: *Server* rest_listen_uri = http://server2.example.com:12900/ rest_enable_tls = false rest_tls_cert_file = /etc/graylog/server/cert.cer rest_tls_key_file = /etc/graylog/server/key.key *Web* graylog2-server.uris= "http://server1.example.com:12900,http://server2.example.com:12900"; Happy to send the full configs off-list if that helps? These are self-signed certificates, is there any trust of the CA that should be setup? There was nothing done for CA trust previously but maybe that's wrong and the CA needs to be trusted somehow? Thanks, Tim C -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/4b7a0915-285d-43a8-b35a-344deba17068%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Upgrade 1.1.6 to 1.2 RC broke REST API using TLS?
Nothing else of note in either /var/log/graylog-server/server.log or /var/log/graylog-web/application.log. Server end doesn't seem to report any errors at all, last lines are that the inputs are running and everything looks well? Is there somewhere else I should be looking? -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/8283f9c6-7225-418e-b3c9-21a2fee119f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Upgrade 1.1.6 to 1.2 RC broke REST API using TLS?
I've just upgraded my Graylog installation to 1.2 RC and since the upgrade my graylog-web node can no longer connect to the REST API of either of my graylog-server nodes using TLS and I have had to revert back to HTTP. I get these application logs (real domain removed) on the graylog-web node, any idea how I can further troubleshoot this? None of my configurations were changed or updated during the upgrade (which used the Ubuntu 14.04 repository to do the upgrade) and it was working fine previously using TLS? 2015-09-02T09:12:05.913+01:00 - [ERROR] - from org.graylog2.restclient.lib. ApiClient in pool-8-thread-1 https://server.example.com:12900 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/cacc7402-3177-4e7d-a1c1-cc2e40b4f95f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: graylog-server 1.1.5 - Enabling HTTPS REST api binds graylog-server service to loopback instead of eth0 address
When I removed that line I then had to then also manually specify the bind addresses for the Elasticsearch client, but otherwise that got it working. 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/6c38a873-0ae2-4f31-b181-4f1a82df22a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] graylog-server 1.1.5 - Enabling HTTPS REST api binds graylog-server service to loopback instead of eth0 address
I am currently in the process of switching to HTTPS for REST communication between my graylog-web frontend and graylog-server nodes but I am having an issue that when I configure the graylog-server to use https the service only binds to the loopback 127.0.1.1 instead of the eth0 address: netstat -an | grep 12900 tcp6 0 0 127.0.1.1:12900 :::*LISTEN My rest_listen_uri is set to match the certificate I'm using and as https (real domain removed) and the certificate and key are configured (real paths removed) and the graylog-server service startsup fine, connects to elasticsearch and the inputs start as normal: rest_listen_uri = https://hostname.example.com:12900/ rest_enable_tls = true rest_tls_cert_file = cert.cer rest_tls_key_file = key.key This is an Ubuntu 14.04.2 box and my /etc/hosts looks like this (real domains removed) 127.0.0.1 localhost 127.0.1.1 hostname.example.com hostname 10.106.249.71 hostname.example.com hostname Is this something I am doing wrong, or should the graylog-server process know from this config it's not supposed to start on the loopback IP? -- 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 graylog2+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/cb97df20-1074-4c9d-99ca-89b15c392ad1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
